Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/Papyrus Developer Guide/Release Standard Operating Procedure: Doc"
Line 1: | Line 1: | ||
− | + | ==Comment== | |
− | + | # level 3 | |
− | + | # @improvement create a bugzilla first | |
− | + | ==Overview== | |
− | + | ||
− | + | ||
− | + | ||
− | # | + | #1 week before setup a team: at least one commiter with one other personn |
− | # | + | #1 day before send an email to the mailing |
− | # | + | #release day send an email to the papyrus developer mailing list before the release |
− | ## | + | #make the release |
− | # | + | #release day send an email to the papyrus developer mailing list after the release |
+ | #release day send an email to the cross project mailing list after the release | ||
+ | |||
+ | ==email template proposal== | ||
+ | |||
+ | # one week end before: XXXX | ||
+ | # release day initial email: Hi everyone !Today is build day so if you can refrain yourselves from pushing troublesome features we would greatly appreciate it.Papyrus Core Team | ||
+ | |||
+ | ==Prerequisite== | ||
+ | |||
+ | # fresh eclipse <version> nightly Eclipse for RCP and RAP Developers | ||
+ | # papyrus git new branch on master synchro wuth the master branch | ||
+ | |||
+ | ==Release Plan Action== | ||
# SimRel | # SimRel |
Revision as of 06:51, 3 June 2015
Comment
- level 3
- @improvement create a bugzilla first
Overview
- 1 week before setup a team: at least one commiter with one other personn
- 1 day before send an email to the mailing
- release day send an email to the papyrus developer mailing list before the release
- make the release
- release day send an email to the papyrus developer mailing list after the release
- release day send an email to the cross project mailing list after the release
email template proposal
- one week end before: XXXX
- release day initial email: Hi everyone !Today is build day so if you can refrain yourselves from pushing troublesome features we would greatly appreciate it.Papyrus Core Team
Prerequisite
- fresh eclipse <version> nightly Eclipse for RCP and RAP Developers
- papyrus git new branch on master synchro wuth the master branch
Release Plan Action
- SimRel
- Clone simrel git repository: by egit or directly with command line: git clone git://git.eclipse.org/gitroot/simrel/org.eclipse.simrel.build.gi
- Import the project inside your eclipse workspace
- Import Eclipse Papyrus Developer Tools
- Papyrus Releng
- Import releng project in workspace
- Update dependencies from Agregation Build Models
- right click on the *.pom.xml and oomph papyrus.setup
- /releng/org.eclipse.papyrus.oomph/setups/papyrus.setup
- /releng/top-pom-dev.xml
- /releng/top-pom-extra-tests.xml
- /releng/top-pom-extras.xml
- /releng/top-pom-main-tests.xml
- /releng/top-pom-main.xml
- /releng/top-pom-rcp.xml
- Selection the right version and check the Confirmation Location Update, each version should be the lastest official version except if you depend on a specific build version, unreleased officially
- right click on the *.pom.xml and oomph papyrus.setup
- Update dependencies manually
- for all unannotated repositories,
- @missing cmd: find . -name "top-pom*" | xargs -t -i grep "manualUpdate" -b1 {}
- for detection of manual repository example repository orbit find the lastest url http://download.eclipse.org/tools/orbit/downloads/
- Push on Papyrus gerrit
- [Releng] Update dependencies for <Eclipse Version> <Milestone>