Rick Hillegas <[EMAIL PROTECTED]> writes: > Mike Matrigali wrote: >> Rick Hillegas wrote: >>> Mike Matrigali wrote: >>>> Could someone with the right permissions add the new >>>> 10.3.3.0 release to JIRA as a "released" version? >>> Hi Mike, >>> >>> I have marked 10.3.3.0 as released on May 12. I double-checked that >>> it now appears as a released version when I try to create a new >>> JIRA. Let me know if there's still some tweaking to be done here. >>> >>> Cheers, >>> -Rick >>> >> Thanks, I just updated an issue using this new field, so worked for me. >> Is there any automated process where we could change all those bugs >> marked fixed in the unreleased version of 10.2.2 as fixed in >> released >> version 10.3.3.0? > I don't know this magic but I'm happy to learn it if someone will teach me.
Hi Rick, I think this is step 11b of "After a successful vote" in the release process (http://wiki.apache.org/db-derby/DerbySnapshotOrRelease): > The older development versions used for tracking changes between > releases are no longer needed, and old versions should be merged into > the release version. E.g. for the 10.3.1.4 release, 10.3.0.0, > 10.3.1.0, 10.3.1.1, 10.3.1.2, and 10.3.1.3 need to be merged into the > released 10.3.1.4. > > * Click the Merge button next to the oldest release. > > * Select all the versions in the list on the right to merge and then > the released version to merge to on the left (in the example > above, this would be 10.3.1.4 > > * Click the Merge button and confirm the merge. -- Knut Anders
