Deprecate the unleash plugin #6
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
https://github.com/shillner/unleash-maven-plugin/ has been archived. That is the unleash plugin for Apache Maven. The Jenkins unleash maven plugin depends on the unleash plugin for Apache Maven. https://github.com/jenkinsci/unleash-plugin has been archived. That is the Jenkins unleash Maven plugin. The last release of the Jenkins unleash maven plugin was 3 years ago. Since the Jenkins plugin repository has been archived, we can expect no new releases of the plugin. [JENKINS-70326](https://issues.jenkins.io/browse/JENKINS-70326) notes that the Jenkins unleash maven plugin does not work with Java 17. Let's deprecate the Jenkins plugin so that it is clear to users that the Jenkins plugin is not being maintained and that the Apache Maven plugin is not being maintained. https://www.jenkins.io/doc/developer/plugin-governance/deprecating-or-removing-plugin/ says that the preferred way to deprecate a plugin is to add the "deprecated" topic to the repository and to explain in the plugin documentation why it is being deprecated. That would mean allowing writes to the repository again, just long enough to set the topic. I assume that is more complicated than the alternate method, a pull request to the update center repository to mark the repository as deprecated. jenkins-infra/repository-permissions-updater#3042 is the request to remove all developers from the archived plugin repository.
MarkEWaite
added a commit
to MarkEWaite/update-center2
that referenced
this pull request
Dec 21, 2022
https://github.com/shillner/unleash-maven-plugin/ has been archived. That is the unleash plugin for Apache Maven. The Jenkins unleash maven plugin depends on the unleash plugin for Apache Maven. https://github.com/jenkinsci/unleash-plugin has been archived. That is the Jenkins unleash Maven plugin. The last release of the Jenkins unleash maven plugin was 3 years ago. Since the Jenkins plugin repository has been archived, we can expect no new releases of the plugin. https://issues.jenkins.io/browse/JENKINS-70326 notes that the Jenkins unleash maven plugin does not work with Java 17. Let's deprecate the Jenkins plugin so that it is clear to users that the Jenkins plugin is not being maintained and that the Apache Maven plugin is not being maintained. The [deprecation document](https://www.jenkins.io/doc/developer/plugin-governance/deprecating-or-removing-plugin/) says that the preferred way to deprecate a plugin is to add the "deprecated" topic to the repository and to explain in the plugin documentation why it is being deprecated. That would mean allowing writes to the repository again, just long enough to set the topic. I assume that is more complicated than the alternate method, a pull request to the update center repository to mark the repository as deprecated. I've taken the alternate approach with this pull request. jenkins-infra/plugins-wiki-docs#6 is the documetnation pull request to mark the plugin as deprecated.
timja
approved these changes
Dec 21, 2022
|
I believe that @halkeye has permissions here |
|
i do have merge permission. I have no who else does as I'm not an admin. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deprecate the unleash plugin
https://github.com/shillner/unleash-maven-plugin/ has been archived. That is the unleash plugin for Apache Maven. The Jenkins unleash maven plugin depends on the unleash plugin for Apache Maven.
https://github.com/jenkinsci/unleash-plugin has been archived. That is the Jenkins unleash Maven plugin. The last release of the Jenkins unleash maven plugin was 3 years ago. Since the Jenkins plugin repository has been archived, we can expect no new releases of the plugin.
JENKINS-70326 notes that the Jenkins unleash maven plugin does not work with Java 17.
Let's deprecate the Jenkins plugin so that it is clear to users that the Jenkins plugin is not being maintained and that the Apache Maven plugin is not being maintained.
https://www.jenkins.io/doc/developer/plugin-governance/deprecating-or-removing-plugin/ says that the preferred way to deprecate a plugin is to add the "deprecated" topic to the repository and to explain in the plugin documentation why it is being deprecated. That would mean allowing writes to the repository again, just long enough to set the topic.
I assume that is more complicated than the alternate method, a pull request to the update center repository to mark the repository as deprecated.
jenkins-infra/repository-permissions-updater#3042 is the request to remove all developers from the archived plugin repository.