On Wed, Mar 13, 2013 at 8:52 PM, Greg Stein <[email protected]> wrote:
> On Mar 12, 2013 1:33 PM, "Ryan Ollos" <[email protected]> wrote: > > Please let me know if you see any problems with the following plan: > > 1. Leave the 0.5 tag > > 2. Update the release notes, bump the version numbers to 0.5.1 and > remove > > the `contrib` directory on the 0.5 branch > > 3. Delete the 0.5 release artifacts in the bloodhound-dist (1) > > 4. Create a new release named 0.5.1 > > > > I'll wait about 24 hours for feedback before taking any action to start > the > > next release. > > I concur with Gary: just do this on trunk. > > Further, I recommend calling 0.5 defunct and move to 0.6. Version numbers > are cheap. Just note 0.5 was not released (in the release notes). You'll > find similar in the svn and serf notes, where versions were pulled. I > screwed up serf so badly once, we jumped from 0.3 to 0.6.1 in a few hours. > Horrible day :-/ > If we go this route and wish to keep milestone "Release X" aligned with version "X", which I hope we do for the sake of sanity, then I'll need Gary (or anyone else BATCH_MODIFY privileges) to move the tickets currently assigned to "Release 6" to "Release 7" (or I suppose you can accomplish this in other ways that you might see fit, such as renaming milestones [which is another action that I don't have permissions to perform]). Batch modify will avoid having to change 35 tickets one-at-a-time, which also would result in 35 messages being sent to bloodhound-commits, and I'm sure no one wants that. I have felt that it would be less confusing to just call this release 0.5.1 and have it correspond to the "Release 5" milestone so that we don't have to move tickets, but that's as much opinion as I have on the matter.
