[ome-devel] OME 2.6.0 Release Branch

[Ilya Goldberg]

Hi All
Things are rapidly drawing to a close, and I would like to tag the  
2.6.0 release.
The plan is to do it this Friday afternoon 2006-07-21.  If anybody  
has last-minute adds, this would be the dead-line.
If someone needs to extend the date, please speak up.

For those new here, here's how releasing works:
A branch is created in CVS called OME_2_6_0
The code in the branch is tagged as OME_2_6_0_RC1 as the first  
release candidate.
The release candidate is packaged up in a tar-ball for people to  
download and test.
Commits to the OME_2_6_0 branch in CVS should be for fixing bugs only.
All other work on OME continues in HEAD, which becomes version 2.7.0  
after the branch.

The candidate is tested by everyone (please help with this!) for one  
week, with bug fixes committed to the OME_2_6_0 branch (and ported to  
HEAD).
A new release candidate is tagged and packaged for testing at the end  
of the week if there are new commits to the OME_2_6_0 branch.
If there are no commits or outstanding bugs at the end of the week,  
the last candidate is released as 2.6.0

The OME_2_6_0 branch is then effectively dead, except for fixing  
critical bugs.  These will be released as 2.6.1, etc.

Please speak up if you have suggestions/modifications for this process.

Thanks,
Ilya