[cle-release-team] Starting to release stuff today
Steve Swinsburg
steve.swinsburg at gmail.com
Mon Oct 3 14:56:04 PDT 2011
So long as all of the upstream projects have stable releases, eg kernel, purepoms, EB etc then you can resolve snapshots at release time.
Cheers
S
Sent from my iPhone
On 04/10/2011, at 5:35, Matthew Jones <jonespm at umich.edu> wrote:
> It seems like you'd still have the same problem, releasing from a release branch as releasing from trunk. You'd need to temporarily commit the changes then switch them back. However in the current 2.7.x and 2.8.x branches for pure-poms, they versions for trunk aren't SNAPSHOT, they're fixed kernel versions. . .
>
> I dunno, maybe we'll have to branch kernel and pure-poms if this was the practice in the past, since only trunk is still mostly open & 2.9, not kernel.
>
> On Mon, Oct 3, 2011 at 2:28 PM, Maurer, Christopher Wayne <chmaurer at iupui.edu> wrote:
> Well, I assume the way he's done it in the past is to release from a release branch!
>
> Chris
>
> From: Matthew Jones <jonespm at umich.edu>
> Date: Mon, 3 Oct 2011 14:25:45 -0400
> To: Chris Maurer <chmaurer at iupui.edu>
> Cc: Anthony Whyte <arwhyte at umich.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
>
> Having to set that property is pretty annoying! However it should only be altered temporarily while a new tag is being created and then immediately changed back to -SNAPSHOT waiting for the next tag in trunk. (Similar to how the maven-release-plugin does a temporary in-place change)
>
> You'll just have to do the release *really* fast! ;) Maybe it would be better if we put it in a profile incase we're not really fast? We'd have to remember to swap the activeByDefault and the RELEASE property when doing a release though. :( How has Anthony been doing this? I've grumbled a few times in the past few days about this trying to release a local kernel using this new process.
>
> <profiles>
> <profile>
> <id>KERNEL-SNAPSHOT</id>
> <activation>
> <property>
> <name>KERNEL-SNAPSHOT</name>
> <activeByDefault>true</activeByDefault>
> </property>
> </activation>
> <properties>
> <sakai.kernel.version>1.3.0-SNAPSHOT</sakai.kernel.version>
> </properties>
> </profile>
> <profile>
> <id>KERNEL-RELEASE</id>
> <activation>
> <property>
> <name>KERNEL-RELEASE</name>
> <activeByDefault>false</activeByDefault>
> </property>
> </activation>
> <properties>
> <sakai.kernel.version>1.3.0-a01</sakai.kernel.version>
> </properties>
> </profile>
> </profiles>
>
> -Matthew
>
> On Mon, Oct 3, 2011 at 1:20 PM, Maurer, Christopher Wayne <chmaurer at iupui.edu> wrote:
> Perhaps I didn't clearly state my issue. In order to release sakai-basic-tool out of pure-poms, I need to modify the sakai.kernel.version property (currently is 1.3.0-SNAPSHOT). Setting that property to 1.3.0-a01 in trunk probably isn't appropriate. And I don't really want to get in to modifying things by hand and forgetting to change them back.
> Is there a better way to do this without making a release branch for it?
>
> Chris
>
> From: Anthony Whyte <arwhyte at umich.edu>
> Date: Mon, 3 Oct 2011 12:10:26 -0400
> To: Chris Maurer <chmaurer at iupui.edu>
> Cc: Matthew Jones <jonespm at umich.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
>
> 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
>
>
>
> _______________________________________________
> 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/20111004/36c02e36/attachment-0006.html
More information about the cle-release-team
mailing list