On Fri, Aug 16, 2013 at 3:33 PM, Erin Noe-Payne <[email protected]>wrote:
> On Fri, Aug 16, 2013 at 3:18 PM, Matt Franklin <[email protected]> > wrote: > > 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. > > > > That feels like an ambitious schedule to me. I see 1 month as no > chance, and 2 months as very tight at best. > - There is a lot of outstanding api work to fill in missing or > incomplete endpoints > - We need to make changes to some models so that transitions (f.e. > moving widgets between regions and pages) become state-based > Can you what you mean by this a little more? > - We need to harden the service layer to protect against data corruption > Yes, but we currently have this in trunk... > - We need to re-implement all of the front end as angular apps What is the state of this re-implementation? > - We need to solve some pretty major architecture questions like... > - The entire authentication / authorization model > Authentication I agree, while the current authorization model is not optimal, it should still work, right? > - How we will now handle internationalization The client messages js endpoint should still work, right? > - How are we going to handle client-side view composition to keep > it from being to chatty > +1 Fair enough. I haven't seen much discussion of state of the branch except for Jira tickets, so this helps. IMO, some of these things feel a lot like they need to be solved by V1, but not necessarily before branch merge. > > > > > > >> 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. > >> >
