On Fri, Aug 16, 2013 at 3:15 PM, Gornstein, Daniel S. <[email protected]>wrote:
> Matt, > > What is the upside of merging the branch into trunk before it is done or > more complete? > > IMO, working off of trunk makes it more "real" for everyone. I think it should only be done if we are within 1-2 months of it being releasable. > This causes people to not be able to use snapshot, and not release any bug > fixes into trunk if you find something which needs attention right away. > Good point, but if we absolutely have to, we can release bugs out of a branch that we create from 0.23 tag. > > Thanks, > Daniel Gornstein > > -----Original Message----- > From: Matt Franklin [mailto:[email protected]] > Sent: Friday, August 16, 2013 3:09 PM > To: [email protected] > Subject: 0.23 Release & Angular Merge > > We are coming up on the end of the month and IMO, it would be a good idea > to do a Rave release for 0.23 that includes the requirejs and Shindig 2.5 > final changes. > > To support this, I have been committing minor bug fixes as I find them, but > it would be good to get everyone who is able checking the current state and > logging anything that needs to be fixed. > > I also see that Erin has been very active on the angular branch. Given > that it is now the major thrust of the project, what would everyone think > about merging that branch back to trunk after the 0.23 release? We would > then wait to do a 0.24 release until after the Angular code is ready. >
