[Building Sakai] status of 2.7-x branch

[Beth Kirschner]

Anthony,

   Is there any specific timeline for the Sakai 2.7.2 release (or is this up to the TCC)?

Thanks,
- Beth

On Sep 29, 2010, at 7:35 PM, Anthony Whyte wrote:

> The "2.7.x branch" (read 2.7.x .externals) no longer includes projects such as basiclti, msgcntr, profile2 and sitestats, projects that each possess the capability to be released independently of general sakai releases, leveraging Maven to generate tags and binary artifacts.  When you checked out 2.7.x, these projects are not downloaded via the svn .externals mechanism.  Instead, they are downloaded, installed in your local .m2 repo and deployed to Tomcat in the guise of *.zip overlays when you perform a build (i.e., mvn clean install sakai:deploy).
> 
> The "indies" as we call them are also versioned independently; sakai-2.7.1 for instance, deploys basiclti-1.1.4.  All of these projects have stable maintenance branches from which releases are generated.  But they are not named "sakai-2.7.x" any more.
> 
> Some "2.7"-related examples:
> 
> https://source.sakaiproject.org/svn/msgcntr/branches/msgcntr-2.7.x/
> https://source.sakaiproject.org/svn/profile2/branches/profile2-1.3.x/
> https://source.sakaiproject.org/svn/sitestats/branches/sitestats-2.1.x/
> 
> A list of all "indies" deployed by each Sakai release can be found in the release management space in Confluence:
> 
> http://confluence.sakaiproject.org/display/REL/sakai-2.8.0-a01
> http://confluence.sakaiproject.org/display/REL/sakai-2.7.1
> http://confluence.sakaiproject.org/display/REL/sakai-2.7.0
> 
> One goal among several of this approach was to encourage "off-cycle" releases in order to push fixes and new features out to the Sakai Community in a more timely fashion.  Another was to automate the snapshot build and release process, leveraging both Maven and our Hudson continuous integration server.  
> 
> In the next couple of days, for instance, we expect to release msgcntr-2.7.2 in order to address reported performance issues.  This is an off-cycle release that will occur well in advance of a general sakai-2.7.2 maintenance release, providing a tag and stable binaries.
> 
> 
> Cheers,
> 
> Anth
> 
> 
> 
> 
> On Sep 29, 2010, at 6:59 PM, Fischbein, Scott A. wrote:
> 
>> Hi all,
>> We’ve been running the 2.7.0 tag in production for a few months now, and are considering an update to 2.7-x. However, in preparing for that update, I’ve noticed that the 2.7-x branch doesn’t seem as solid and complete as the “-x” branches have in the past. For instance, there are some tools/modules that don’t have a 2.7-x branch at all (some have skipped straight to 2.8 or 3.0) and the build itself seems a bit more unstable  (my initial build attempts were unsuccessful, but I was able to work past most of the errors…)
>> 
>> So I’m wondering what the status and reliability of the 2.7-x branch is and whether anyone is running it in production currently.
>> 
>> Thanks,
>> Scott
>> _______________________________________________
>> 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"