Skip to main content
Jump to: navigation, search

Papyrus/Papyrus Developer Guide/Release Standard Operating Procedure: Doc

< Papyrus‎ | Papyrus Developer Guide
Revision as of 07:03, 3 June 2015 by (Talk | contribs) (email template proposal)


  1. @improvement create a bugzilla first
  2. @improvment create a query to find all repositories to be updated manually
  3. @bug the automatic repository version updater seems to introduce non unix break lines


  1. one week before setup a team: at least one commiter with one other personn
  2. one day before send an email to the mailing
  3. release day send an email to the papyrus developer mailing list before the release
  4. make the release
  5. release day send an email to the papyrus developer mailing list after the release
  6. release day send an email to the cross project mailing list after the release

Email template proposal

  1. one week end before: XXXX
  2. 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


  1. fresh eclipse <version> nightly Eclipse for RCP and RAP Developers
  2. papyrus git new branch on master synchro wuth the master branch

Release Plan Action

  1. SimRel
    1. Clone simrel git repository: by egit or directly with command line: git clone git://
    2. Import the project inside your eclipse workspace
  2. Import Eclipse Papyrus Developer Tools
    1. Help>Install> Update site:
  3. Papyrus Releng
    1. Import releng project in workspace
    2. Update dependencies from Agregation Build Models
      1. right click on the *.pom.xml and oomph papyrus.setup
        1. /releng/org.eclipse.papyrus.oomph/setups/papyrus.setup
        2. /releng/top-pom-dev.xml
        3. /releng/top-pom-extra-tests.xml
        4. /releng/top-pom-extras.xml
        5. /releng/top-pom-main-tests.xml
        6. /releng/top-pom-main.xml
        7. /releng/top-pom-rcp.xml
      2. 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
    3. Update dependencies manually
      1. for all unannotated repositories,
      2. @missing cmd: find . -name "top-pom*" | xargs -t -i grep "manualUpdate" -b1 {}
      3. for detection of manual repository example repository orbit find the lastest url
    4. Push on Papyrus gerrit
      1. [Releng] Update dependencies for <Eclipse Version> <Milestone>

Back to the top