[cle-release-team] [Building Sakai] Release thoughts

[Kirschner, Beth]

I agree -- I think also critical to the success of Sakai 10 (aka 2.10) is a QA effort that starts _before_ we branch, and raises visibility of critical/blocker bugs.

- Beth

On Nov 3, 2013, at 10:16 AM, "May, Megan Marie" <mmmay at iu.edu> wrote:

> In the past we cut release branches because people didn’t understand that trunk wasn’t the wild wild west.     If you go with this approach, I’d be sure that you over  communicate this kind of change.
>  
> From: cle-release-team-bounces at collab.sakaiproject.org [mailto:cle-release-team-bounces at collab.sakaiproject.org] On Behalf Of Steve Swinsburg
> Sent: Thursday, October 31, 2013 6:30 PM
> To: Zach A. Thomas
> Cc: Charles Hedrick; sakai-dev; cle-release-team at collab.sakaiproject.org
> Subject: Re: [cle-release-team] [Building Sakai] Release thoughts
>  
> I actually think that Lessons, and any other tool that wants to undergo major changes that won't be ready for trunk in 1st quarter of next year should pick a point to branch their own code and leave trunk ready for the CLE branch time, so everything is consistent.
> 
> Svn 1.8 allows for better branch reintegration so merging back from the branch into trunk is a breeze.
> 
> Standard svn feature branch practice.
> 
> Cheers
> Steve
> 
> sent from mobile device
> 
> On 01/11/2013 2:10 AM, "Zach A. Thomas" <zach.thomas at gmail.com> wrote:
> Chuck,
>  
> Lessons might benefit from some of the techniques collectively known as trunk based development. These are gaining a lot of traction anywhere an organization wants to reduce the friction of doing releases[1].
>  
> The short version is, you don't make a branch; you do all your development in trunk, and you maintain stability with Branch by Abstraction[2] and Feature Toggles[3]. It's a way of having work-in-progress in trunk that wouldn't prevent you from releasing at any given time.
>  
> I wouldn't be so bold as to recommend this for all CLE development, because the necessary rigor might break down, but since, as Sam pointed out, Lessons is the really fast moving target over the next couple of releases, it could help there.
>  
> regards,
> Zach
>  
>  
> [1] http://paulhammant.com/2013/04/05/what-is-trunk-based-development/
> [2] http://continuousdelivery.com/2011/05/make-large-scale-changes-incrementally-with-branch-by-abstraction/
> [3] http://martinfowler.com/bliki/FeatureToggle.html
> On Oct 31, 2013, at 9:00 AM, Charles Hedrick <hedrick at rutgers.edu> wrote:
> 
> 
> It would be nice to QA them sooner, but I’m at the edge of going too fast now. I can’t afford to compromise stability for Sakai 10 by adding anything more than what’s on the list for 10 now. That should be ready within a couple of weeks. I’d rather hold a feature for 2015 than risk the quality of Sakai 10.
>  
> I’m actually not sure exactly how much will be added. I’ve already got enough features. I don’t want to add more (and it’s not clear that the code would survive it). But the Teaching and Learning group has some suggestions for UI, which I’d like to do as I have time. The only one of them that I plan to put into 10 is renaming “add multimedia” / “add resource” to “embed” and “add link”, and reorganizing the pulldowns.
>  
> But if I get time to do other things I’d like to be able to start on them before the RC.
>  
>  
> On Oct 31, 2013, at 9:42 AM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
> 
> 
> I think feature branches makes sense for Lessons, although I would ask: are these features you really don't want to be QA'ed until 2015 and released in mid-2015?  Are they not features that can be refined and QA'ed over the next six months?
>  
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>  
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team