[cle-release-team] Starting to release stuff today

[Anthony Whyte]

No indie as any Sakai-specific dependencies that are themselves not indies.

>  But I need to make updates to poms for various other versions not controlled by the release plugin.  Versions of the parent and related/required modules.  

Anth


On Oct 3, 2011, at 12:03 PM, Maurer, Christopher Wayne wrote:

> So, looking down the list of modules, I'm not sure what the best way to do the releases of the indie projects really is.  Since we're not making release branches yet, I'm releasing from the trunks.  But I need to make updates to poms for various other versions not controlled by the release plugin.  Versions of the parent and related/required modules.  Seems a bit disruptive to trunk for me to do that.  Perhaps we should create release branches for all the indie modules, but not the core modules?
> 
> Or, if there's a better way to utilize jenkins right now, I'm all for that too!
> 
> Chris
> 
> From: Matthew Jones <jonespm at umich.edu>
> Date: Mon, 3 Oct 2011 11:05:57 -0400
> To: Chris Maurer <chmaurer at iupui.edu>
> Cc: Megan M May <mmmay at indiana.edu>, "cle-release-team at collab.sakaiproject.org" <cle-release-team at collab.sakaiproject.org>
> Subject: Re: [cle-release-team] Starting to release stuff today
> 
> That indie release plan looks really unpleasant. 
> 
> Letting Jenkins do the releases might make this more pleasant. [1] Entitybroker should really be in kernel at this point too, and we also locally build both kernel and pure-poms together since you essentially can't seem to release one without the other.
> 
> The biggest problem we found locally is that API changes still get into the kernel in minor releases. We just wanted to get in new kernel fixes, but SAK-18838 has an api change to "conditions/api/ConditionProvider.java" which requires a local patch/rebuild of edu-services (if customized) and possibly other tools. Since we aren't even using conditional release, it seemed easier just to revert it. 
> 
> Bummer!
> 
> [1] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin
> 
> On Mon, Oct 3, 2011 at 10:49 AM, Maurer, Christopher Wayne <chmaurer at iupui.edu> wrote:
>> I don't really know.  Anything that is an Indie release, as well as the main sakai project I suppose.
>> Here's the list of indie projects that Anthony put together:
>> https://confluence.sakaiproject.org/display/REL/Indie+release+order
>> 
>> Chris
>> 
>> From: Megan M May <mmmay at indiana.edu>
>> Date: Mon, 3 Oct 2011 10:45:35 -0400
>> To: Chris Maurer <chmaurer at iupui.edu>, "cle-release-team at collab.sakaiproject.org" <cle-release-team at collab.sakaiproject.org>
>> Subject: RE: Starting to release stuff today
>> 
>> What JIRA projects do you need admin privileges for besides kernel? 
>>  
>> Megan
>>  
>> From:cle-release-team-bounces at collab.sakaiproject.org [mailto:cle-release-team-bounces at collab.sakaiproject.org] On Behalf Of Maurer, Christopher Wayne
>> Sent: Monday, October 03, 2011 10:29 AM
>> To: cle-release-team at collab.sakaiproject.org
>> Subject: [cle-release-team] Starting to release stuff today
>>  
>> I'm starting to release various things today.  So far, I've just released the kernel.
>> Could I get cool jira super powers?  Or if not, could someone with those powers work along side me in jira so that I can add new versions for stuff as I go?  (for example, I just released kernel 1.3.0-a01, so I need that version created and then all the resolved stuff should point to that).
>>  
>> Chris
>> 
>> _______________________________________________
>> cle-release-team mailing list
>> cle-release-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>> 
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20111003/b231c4a0/attachment-0006.html