Personally I would suggest (as I have done before) just moving all of trunk to the branch and getting another beta 0.30.1 out.
That way we can start to commit to trunk once more without our normal no-touch during alpha/beta phase. I've been holding off doing any more work to make this process less difficult for you. Once everything's copied to the branch I'd like to continue work in trunk as soon as possible. Certainly from the users perspective this is just a defect release. Regards Bob. On 17 April 2010 18:02, Linus Tolke Tigris <[email protected]> wrote: > Hello all! > All issues marked with the target-milestone 0.30.1 have now been merged into > the 0.30.x branch. > Bob mentioned including the 6008 and 6015 issues into the 0.30.1 release but > I am not sure if issue 6008 is ready and the issue 6015 doesn't have the > target milestone set for 0.30.1 so I am not sure if we all agree about this. > I intended for the 0.30.1 release to be a patch release with a limited set > of patches in 0.30. Now it looks more and more like we are working on a new > stable release from trunk. > Are the other changes in trunk more or less ready for a new stable release > so that we should plan for a quick 0.32 instead of 0.30.1? If so we could > make a development release (0.31.1 or 0.32.alpha1) tomorrow or Monday, a > beta release by the end of the week. > /Linus > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2587022 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
