Pre-Release Branch

Owned by Former user (Deleted)
Last updated: Feb 12, 2008 by Former user (Deleted)Version comment
2 min read

Objectives to this process:

  • Foster better communication between those fixing the bugs and those carrying out the testing
  • Have discussion on the lists so those that can't attend the release meetings can participate

Assumptions

Upon completing the fix for an issue you are checking your changes in to trunk, Resolving the issue in Jira and marking "Nightly/SVN-Trunk" as a Fix Version. Please note: The fix version should only be set to 2.5.x if the code has actually been merged into this branch.

Process

To get your fixes in the release there are two steps:

  1. Add your fix to the fixes for next tag list at http://confluence.sakaiproject.org/confluence/x/fAAv
  2. Please send an email to the QA list (sakai-qa@collab.sakaiproject.org) for any Jira that you think is a good candidate for merging from trunk to the 2.5.x branch. You should include a brief summary of your change in the email and recommendations for how to test the change, if you haven't already placed that information in the Jira.

Managing your own branch? Follow this process

  1. Please send an email to the QA list (sakai-qa@collab.sakaiproject.org) for any Jira that you think is a good candidate for merging from trunk to the 2.5.x branch. You should include a brief summary of your change in the email and recommendations for how to test the change, if you haven't already placed that information in the Jira
  2. Update the FIX VERSION to 2.5.x. Your issue will auto-magically display on the list of items for the next tag.

Followup

After the release meeting, the Release manager will typically create the tag, and one of the Foundation staff (project coordinator, qa director) will make sure the Fix Versions are updated appropriately. I know there is probably an easier way to handle some of this given the introduction of the targeted version and I am definitely open to finding a better way to do this. So if you have suggestions, please feel free to pipe up with them. That said, I'd like to continue with this process throughout the 2.5 cycle since we've used it for the past couple releases and pain as it might be, it's generally served us well