Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintain revision history of package metadata updates #1142

Closed
pranavkm opened this issue May 15, 2013 · 2 comments
Closed

Maintain revision history of package metadata updates #1142

pranavkm opened this issue May 15, 2013 · 2 comments

Comments

@pranavkm
Copy link
Contributor

From https://nuget.codeplex.com/workitem/3348

Whenever a package's metadata is changed or the package is unlisted, a revision history should be kept. And this revision history should be queryable from NuGet.org.

The process of unlisting or altering package metadata should require whoever is doing it to supply an explanation that becomes part of the revision history. Ideally, when a package is unlisted, this explanation will become the Description field saying something like "This package has been deprecated. Please use package X.Y instead".

Users should be able to see this revision history and explanations at least from the Data Services, and maybe eventually in Package Explorer or Package Manager.

@TimLovellSmith
Copy link
Member

Great idea to have better support for deprecation of packages/package versions.
Do you have an intended purpose/use for the entire history of past list/unlist events, or only for the explanation 'why is this package I'm interested in unlisted'?

@analogrelay
Copy link
Contributor

As we look at more editable metadata in #565, we also agree that having a history of changes is good. So we'll do that when we work on editable metadata.

joelverhagen pushed a commit that referenced this issue Jul 30, 2024
* Package source mapping.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants