-
Suggestion
-
Resolution: Fixed
-
None
The site studio.plugins.atlassian.com is deprecated. All new projects shall be migrated to bitbucket.org or eventually to ecosystem.atlassian.net.
Deadline:
- final deadline 5.03.2013
- it's recommended to finish it before 5.02.2013
Scope:
1) Migrate SVN repositories
to Mercurial on Bitbucket
2) Migrate Bamboo builds (if necessary) from
Note: CLMVNONE has no builds configured
to new Bamboo location.
3) There is no need to migrate Wiki pages and Code reviews (practically empty).
4) Migrate JIRA issues from
- https://studio.plugins.atlassian.com/browse/CLMVNONE
- https://studio.plugins.atlassian.com/browse/CLMVN
to
if this is feasible and set component "Maven 1 Plugin" and "Maven Plugin", respectively.
Alternatively, create new issue trackers on Bitbucket or Ecosystem, copy all issues "as is" and set projects read-only with a message that issue tracking shall be done in JAC CLOV project.
5) Update build scripts (Maven / Ant) and handle:
new repository type (tagging)new way of deployment of binaries (optional)
Update also BEAC builds.
[CLOV-1197] Perform migration of CLMVN and CLMVNONE from studio.plugins.atlassian.com
ad 4) CLMVN jira project was copied to jira.atlassian.com, references on confluence.atlassian.com/display/CLOVER were updated; only the latest version of documentation was updated; older spaces CLOVER030, CLOVER026 etc ... are set read-only
ad 1) CLMVN SVN repository was migrated to https://bitbucket.org/atlassian/maven-clover2-plugin
Updated release procedure and tested (3.1.10.1), updated Clover+for+Maven+2+and+3+Developer+Guide.
ad 4) Around 15 issues from CLMVN were copied to CLOV project and scheduled for 'someday' or '3.2.3' release. The whole CLMVN project will be migrated to JAC for the archival reasons and set read-only.
TODO: as soon as it's copied, update all "Changelog" pages on CAC/CLOVER to query issues from new location.
ad 3) Wiki pages won't be migrated. POMs and Bitbucket's README will point to the Clover Documentation Home.
ad 4) Three open issues from CLMVNONE were copied to CLOV.
ad 5) Clover-for-Maven1: maven build cannot handle HG repository, so tagging is made manually. Rest of build works, according to the procedure. There will be no new way of deployment of binaries - just scp to maven.atlassian.com/maven1, nowhere else.
ad 1) CLMVNONE
- was migrated with history to https://bitbucket.org/atlassian/maven-clover-plugin (Mercurial)
- jjaroczynski invited as admin; mstudman and npellow notified
- public access
- new developer guide for customers prepared: https://confluence.atlassian.com/display/CLOVER/Clover-for-Maven1+Developer+Guide
todo:
- update internal procedure, test by releasing 2.6.3 and 3.1.10
ad 2) CLMVN-TRUNK was disabled; reasons:
- latest migration to OSS Sonatype hosting requires Maven 3.x for build which is not available on StPAC
- there is a similar build running on BEAC already
= DONE
Both projects are migrated (sources, documentation, issue tracker, development procedures etc).