[cle-release-team] Fwd: CLE Release Team Call, Thursday, October 27, 10am EDT

Anthony Whyte arwhyte at umich.edu
Wed Oct 26 12:14:52 PDT 2011


I should also note that non-indies with dependencies on indies bind to specific indie versions as via version <properties> defined in the master pom.  This eliminates another vector for snapshot drift.

Anth  

Begin forwarded message:

> From: Anthony Whyte <arwhyte at umich.edu>
> Date: October 26, 2011 2:49:33 PM EDT
> To: "Maurer, Christopher Wayne" <chmaurer at iupui.edu>
> Cc: "cle-release-team at collab.sakaiproject.org" <cle-release-team at collab.sakaiproject.org>
> Subject: Re: [cle-release-team] CLE Release Team Call, Thursday, October 27, 10am EDT
> 
> But of course.  There are many projects that are not yet indies (e.g., rwiki, podcasts etc.) so they remain SNAPSHOT.  They would also remain 2.9-SNAPSHOT even if we branched to 2.9.x given the current versioning practice for maintenance branches (see 2.6.x, 2.7.x, 2.8.x).
> 
> Except in the case of lessonbuilder, which as I noted earlier, I did not release due to its (former) contrib dependencies, none of the other non-indies pose a risk of introducing drift because none of them have binaries that have been deployed to the snapshot repo.  So there is nothing to worry about as regards them.
> 
> 
> Anth
> 
> 
> On Oct 26, 2011, at 2:37 PM, Maurer, Christopher Wayne wrote:
> 
>> I will probably not be able to make the call tomorrow, but if I can, I'll join.
>> 
>> A couple of comments.
>> I'm not sure if it's again an artifact of the way we've been tagging from trunk, but as I was (finally) rebuilding for the revised a01 tag today, I sure noticed a lot of SNAPSHOT artifacts go flying by in maven.
>> Here's a link to the build log if anyone would like to inspect it:
>> http://nightly2.sakaiproject.org/logs/build-qa3/build-2011-10-26-12:00:26.log.txt
>> 
>> Not sure if that's anything we should be worried about or not, but it seems like it has a great potential to be introducing newer artifacts into this build.  If so, then what I just deployed might not be the a01 tag "proper".
>> 
>> Chris
>> 
>> From: Sam Ottenhoff <ottenhoff at longsight.com>
>> Date: Wed, 26 Oct 2011 12:03:06 -0400
>> To: <cle-release-team at collab.sakaiproject.org>, Sakai QA <sakai-qa at collab.sakaiproject.org>
>> Subject: [cle-release-team] CLE Release Team Call, Thursday, October 27, 10am EDT
>> 
>> Hi all,
>> 
>> We're expecting a few additional people on the call tomorrow as we gear up for 2.9 QA and new build processes.  The floor will be open for topics in addition to QA, major 2.9 feature review, and current blockers.
>> 
>> --Sam
>> 
>> CONNECTION INFO
>> 
>> Telephone: +1 812 856 7060
>> Polycom or Lifesize: 156.56.240.100##22X
>> Tandberg or XMeeting: 22X at 156.56.240.100
>> GDS E.164: 0011439X
>> 
>> Conference Code: 22348#
>> PIN: 72524
>> 
>> CLE open blockers:
>>   
>>    https://jira.sakaiproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=12708
>> _______________________________________________ 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/20111026/e5434317/attachment-0006.html 


More information about the cle-release-team mailing list