Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Recommenders/Release/Checklist"

m
Line 16: Line 16:
 
# Announcements ready?
 
# Announcements ready?
 
# Created a post in the forum?
 
# Created a post in the forum?
 +
 +
 +
=== update versions with tycho ===
 +
 +
Use: '''mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<version>''' as described [[http://community.jboss.org/en/tools/blog/2011/09/17/coping-with-versions-in-large-multi-module-osgi-projects here]].
 +
  
 
[[Category:Recommenders|When Creating Drops Checklist]]
 
[[Category:Recommenders|When Creating Drops Checklist]]

Revision as of 01:23, 19 September 2011

This is a action list that should be checked before a new drop is promoted.

  1. Walk trough all UI test cases and check applicability (especially for postponed scenarios)? Do that a few days before drop date.
  2. Are all UI test suites running?
  3. Do all manual test scenarios still work?
  4. Are all versions in pom.xm, manifest.mf, and feature.xml files updated?
    • Create dummy feature containing all plug-ins. Press Versions button on plug-ins tab and select force feature version into plug-in and fragment manifests
    • Update all feature versions
    • Update maven version of parent module. Run mvn versions:update-child-modules
  5. Added News and Noteworthy/0.x to org.eclipse.recommenders.doc.user plug-in generation task?
  6. Added all new plug-in dependencies to feature?
  7. Are plug-ins available from dev update channel?
  8. Did test install in a clean Eclipse installation work? (note, no update site except default and code recommenders dev allowed)
  9. Website updated?
  10. Marketplace updated?
  11. Announcements ready?
  12. Created a post in the forum?


update versions with tycho

Use: mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<version> as described [here].

Back to the top