DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Status: Completed
The last phase is about to clean up and "archiving" the Jira projects. This includes
- Properly retire inactive or partly archived repositories according to the Retirement plan
- Decide what to do with inactive components and of shared projects
- Reconsider migration MNGSITE issues to Github (to not have site the only Jira project left) or put common effort to get Jira issues done
- "Archive" Jira projcets by adding information of migration and making them fully read only
Proper retirement of inactive projects/ decide what to do inactive components
The following projects / components where skipped, because they are inactive or already partly archived
| JIRA | Retirement | ||||||
|---|---|---|---|---|---|---|---|
| project | component | issues | GitHub repository | task issue | Done | Status | Notes |
| MSHARED | maven-ant | Getting issues... |  | The whole Jira project will get read only in the near future. No extra work. | |||
| MSHARED | maven-app-configuration | Getting issues... | | The whole Jira project will get read only in the near future. No extra work. | |||
| MSHARED | maven-artifact-transfer | Getting issues... | maven-artifact-transfer |
INFRA-27068
-
Getting issue details...
STATUS
| Deprecated though MSHARED-1270 - Getting issue details... STATUS Discussion on ML about retirement got 3 +1 from PMC | ||
| MSHARED | maven-doxia-tools | Getting issues... |
| not retired | Jira note: maven-doxia-tools is now a part of DOXIATOOLS Nothing to do | ||
| MSHARED | maven-mapping | Getting issues... | maven-mapping | needed, no retirement | |||
| MSHARED | maven-project-utils | Getting issues... | maven-project-utils |
INFRA-27068
-
Getting issue details...
STATUS
| GitHub page says: "Not active projects - to be archived" Discussion on ML about retirement got 3 +1 from PMC | ||
| MSHARED | maven-script | Getting issues... | | | The whole Jira project will get read only in the near future. No extra work. | ||
| MSHARED | maven-shared-monitor | Getting issues... | | The whole Jira project will get read only in the near future. No extra work. | |||
| MNG | Integration Tests | maven-integration-testing | needed for 3.x | GitHub page says: "Has been integrated into Maven core" | Is needed, Maven 3.x line (latest 3.9.x inclusive) are still using this repo to run ITs | ||
| DOXIATOOLS | Doxia Eclipse Editor | Getting issues... | maven-doxia-ide |  | | The whole Jira project will get read only in the near future. No extra work. | |
| DOXIATOOLS | Doxia Integration Tools | Getting issues... | | Jira says: Moved to DOXIASITETOOLS | The whole Jira project will get read only in the near future. No extra work. | ||
| DOXIATOOLS | Doxia Netbeans Editor | Getting issues... | maven-doxia-ide | | | The whole Jira project will get read only in the near future. No extra work. | |
| MSKINS | Default Skin | Getting issues... | maven-default-skin |
INFRA-27057
-
Getting issue details...
STATUS
| Discussion on ML about retirement got 3 +1 from PMC | ||
Reconsider migration MNGSITE issues to Github
When tasks of above table were done (and nothing was overseen) MNGSITE is the last Jira projects with issues that were not migrated, but are also not completed. We should reconsider, if we want to keep this and making it the only Jira project / GitHub repository in that state or also migrate the issues ( Getting issues... ).
Update: Issues got migrated
"Archive" Jira projects
At the end of phase 1 Jira projects are in the state that no new issues can be created, but existing can be modified (commented, worked on, etc.). When issues of a Jira projects were migrated the Jira needs to be set into "read only mode".
In Slack the idea came up to set the description (can NOT be done by PMC, we were wrong about this) to a text like "This project has been retired after migration to GitHub. Please refer to <<<GITHUB PAGE>>> for further details.". It also needs to be considered that some Jira projects (e.g. MSHARED, DOXIATOOLS, MRESOLVER, and more) have multiple components with different Github pages.
INFRA issue: INFRA-27075 - Getting issue details... STATUS