[cle-release-team] [infrastructure] Mail Sender to core

Anthony Whyte arwhyte at umich.edu
Tue Sep 20 09:39:21 PDT 2011


Bind to these assemblies:

LB trunk assembly
http://source.sakaiproject.org/maven2-snapshots/org/sakaiproject/lessonbuilder/sakai-lessonbuildertool-assembly/1.4-SNAPSHOT/

Mailsender trunk assembly
http://source.sakaiproject.org/maven2-snapshots/org/sakaiproject/mailsender/mailsender-assembly/1.7.0-SNAPSHOT/


On Sep 20, 2011, at 12:31 PM, Anthony Whyte wrote:

> I have another proposal that I plan to send out that recommends we reintroduce full source checkout and that means moth-balling core-deploy.
> 
> I think both lessonbuilder and mailsender and the rest of the indies should be included in the check out like all monolithic projects.  If you think that is jumping the gun as regards current practice then forget about updating the .externals and the base pom and do the following:
> 
> master pom  add
> 
> <properties>
> 	<sakai.lessonbuilder.version>X.X-SNAPSHOT</sakai.lessonbuilder.version>
> 	<sakai.mailsender.version>X.X-SNAPSHOT</sakai.mailsender.version>
> 
> 
> core-deploy pom
> 
> Add a dependency to lessonbuilder and mailsender's assemblies (a cut and paste job based on the other indies referenced).  Add to both the full and experimental profiles.
> 
> Build and test.
> 
> Anth
> 
> 
> 
> On Sep 20, 2011, at 11:44 AM, Maurer, Christopher Wayne wrote:
> 
>> Well, looking again, maybe this should be an indie and go in core-deploy?
>> 
>> Chris
>> 
>> From: Anthony Whyte <arwhyte at umich.edu>
>> Date: Tue, 20 Sep 2011 11:41:16 -0400
>> To: Chris Maurer <chmaurer at iupui.edu>
>> Cc: "cle-release-team at collab.sakaiproject.org" <cle-release-team at collab.sakaiproject.org>, Carl Hall <carl at hallwaytech.com>, "infrastructure at collab.sakaiproject.org" <infrastructure at collab.sakaiproject.org>
>> Subject: Re: [infrastructure] Mail Sender to core
>> 
>> Put it in both.  The experimental profile is core + additional stuff.
>> 
>> On Sep 20, 2011, at 11:34 AM, Maurer, Christopher Wayne wrote:
>> 
>>> And is it safe to assume that it should go under the full profile rather than the experimental one?
>>> 
>>> Chris
>>> 
>>> From: Anthony Whyte <arwhyte at umich.edu>
>>> Date: Tue, 20 Sep 2011 11:31:59 -0400
>>> To: Chris Maurer <chmaurer at iupui.edu>
>>> Cc: "cle-release-team at collab.sakaiproject.org" <cle-release-team at collab.sakaiproject.org>, Carl Hall <carl at hallwaytech.com>, "infrastructure at collab.sakaiproject.org" <infrastructure at collab.sakaiproject.org>
>>> Subject: Re: [infrastructure] Mail Sender to core
>>> 
>>> Indeed, I did leave that out of the instructions I sketched out below.
>>> 
>>> Anth
>>> 
>>> 
>>> On Sep 20, 2011, at 10:38 AM, Maurer, Christopher Wayne wrote:
>>> 
>>>> I believe you forgot to mention adding it to the main pom.xml (unless we're not ready to do that yet).
>>>> 
>>>> Carl, are there any properties we need to get added to the default sakai.properties file?
>>>> 
>>>> Chris
>>>> 
>>>> 
>>>> From: Anthony Whyte <arwhyte at umich.edu>
>>>> Date: Mon, 19 Sep 2011 16:43:56 -0400
>>>> To: Chris Maurer <chmaurer at iupui.edu>, <cle-release-team at collab.sakaiproject.org>, Carl Hall <carl at hallwaytech.com>
>>>> Cc: <infrastructure at collab.sakaiproject.org>
>>>> Subject: Re: [infrastructure] Mail Sender to core
>>>> 
>>>> Once Chris has moved mailsender a member of the release team should update trunk .externals.  I was going to do it but on reflection I am supposed to be letting go of these tasks.  :)
>>>> 
>>>> Also check with Carl to see if any properties are needed to be added to /config default.sakai.properties and demo.sakai.properties.
>>>> 
>>>> Cheers,
>>>> 
>>>> Anth
>>>> 
>>>> 1. First create a ticket task (e.g., add mailsender to trunk .externals).  
>>>> 2. Then perform a -N checkout of trunk.
>>>> 
>>>> cd /tmp
>>>> svn co -N https://source.sakaiproject.org/svn/sakai/trunk/ trunk
>>>> cd trunk
>>>> 
>>>> 3. Modify .externals
>>>> 
>>>> vi .externals (add alpha order)
>>>> 
>>>> mailsender https://source.sakaiproject.org/svn/mailsender/trunk
>>>> 
>>>> I'd also move lessonbuilder up and position it's checkout line between help and linktool.  Good to be consistent.
>>>> # Experimental Sakai capabilities
>>>> lessonbuilder https://source.sakaiproject.org/svn/lessonbuilder/trunk
>>>> 4.  Then do a propset on .externals and commit.
>>>> 
>>>> 
>>>> svn propset -F .externals svn:externals .
>>>> svn propget svn:externals
>>>> svn commit -m "SAK-XXXXX add mailsender to .externals"
>>>> 
>>>> 
>>>> You can (should) test locally and make sure that mailsender is included in a trunk checkout. Be sure to also check the next nightly2 build.
>>>> 
>>>> 
>>>> Cheers,
>>>> 
>>>> 
>>>> Anth
>>>> CLE release lead, emeritus
>>>> 
>>>> 
>>>> On Sep 19, 2011, at 3:04 PM, Maurer, Christopher Wayne wrote:
>>>> 
>>>>> Ok, I've got it into the test repo:
>>>>> https://source.sakaiproject.org/testrepo3/mailsender/
>>>>> 
>>>>> It's a straight up copy, so the dir structures will need a bit of attention.  
>>>>> Please verify that you have it all there (including history).
>>>>> Once you give the go ahead I'll do the import to svn.
>>>>> When the import is done, you'll need to move the trunk, tags, and branches directories back up to the top level of mailsender and should then be able to delete the intermediate stuff (gatech and then the embedded mailsender dir)
>>>>> 
>>>>> Chris
>>>>> 
>>>>> From: Chris Maurer <chmaurer at iupui.edu>
>>>>> Date: Mon, 19 Sep 2011 18:17:01 +0000
>>>>> To: Carl Hall <carl at hallwaytech.com>, "infrastructure at collab.sakaiproject.org" <infrastructure at collab.sakaiproject.org>
>>>>> Subject: Re: [infrastructure] Mail Sender to core
>>>>> 
>>>>> Carl,
>>>>> I'm been pretty swamped the last several weeks.  I'll try to get going on it this afternoon.
>>>>> 
>>>>> Chris
>>>>> 
>>>>> From: Carl Hall <carl at hallwaytech.com>
>>>>> Date: Mon, 19 Sep 2011 13:57:40 -0400
>>>>> To: <infrastructure at collab.sakaiproject.org>
>>>>> Subject: [infrastructure] Mail Sender to core
>>>>> 
>>>>> Hi infrastructure team,
>>>>> 
>>>>> I was wondering what the status of INFRSTR-35[1] is. With the 2.9 code freeze coming up, I'm trying to ready a mail sender release to happen about the same time.
>>>>> 
>>>>> Thanks,
>>>>> Carl
>>>>> 
>>>>> 1 https://jira.sakaiproject.org/browse/INFRSTR-35
>>>>> _______________________________________________ infrastructure mailing list infrastructure at collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/infrastructure
>>>>> _______________________________________________ infrastructure mailing list infrastructure at collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/infrastructure
>>>>> _______________________________________________
>>>>> infrastructure mailing list
>>>>> infrastructure at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/infrastructure
>>>> 
>>> 
>> 
> 
> _______________________________________________
> 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/20110920/2ab2a108/attachment-0006.html 


More information about the cle-release-team mailing list