Hi,
thank everyone for your responses. I will continue to work on the
retirement tasks to archive the repository.
Matthias
Am 15.07.2025 um 19:17 schrieb Matthias Bünger:
Hi everyone,
during migration from JIRA to GitHub we noticed that the mentioned
component is no longer used, but was not fully archived. While (in
difference to plugins) there is no strict plan how to retire
components, but the current state of the component says the differnt,
meaning that
* the componenent is listd as active on site
* the JIRA component is listed as "active"
* the GitHub repository is not archived
* the readme of the GitHub repository gives no information about the
deprecation [1]
* the retirement task/issue is not finished [2]
To have a clear migration and be able to set the affected JIRA project
to read-only we need to decide how to move on with this component.
My suggestion is to take minimal efforts to archive it. This means
* set the componend to inactive on site and in the JIRA project,
* ask INFRA to proper archive the repository, and
* of course finish retirement issue
What do you think?
Matthias
[1] https://github.com/apache/maven-default-skin
[2] https://issues.apache.org/jira/browse/MSKINS-196
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
