[Building Sakai] How we tag releases

[Noah Botimer]

It should be practical to do a test tag or two. Also, since these are  
copies that SVN knows about, it won't send the binary data back for  
the commit (or double it up in the repository). You do end up  
checking out the entire working copy, but I think this is already  
happening in the release process for verification.

I'll be glad to help test these suggestions.

Thanks,
-Noah

On Apr 13, 2009, at 8:57 AM, Anthony Whyte wrote:

> We should test out this idea after 2.6.0 is released.  I wonder  
> though, how long it will take to commit an entire working copy of  
> Sakai core projects (step 5).  It may well require a good deal of  
> patience and/or a pillow to see it through.  :)  We will probably  
> need more storage space allocated for svn as well.
>
> Anth
>
>
> On Apr 12, 2009, at 11:40 AM, Noah Botimer wrote:
>
>> I've been thinking about these hollow parts of the repository for  
>> some time. I think the right way to do this is to materialize our  
>> tags, but not branches. It's actually not that hard. Here's an  
>> abstract.
>>
>>  1. Figure out which externals and revisions are to be used.
>>  2. Check out the top tags dir with svn co -N /sakai/tags.
>>  3. Create an svn dir for the new tag locally.
>>  4. Run through the externals and svn cp from the branches to the  
>> working copy.
>>  5. Check the whole working copy in.
>>
>> The biggest benefit, in my mind, is that the tags become cohesive  
>> snapshots of everything that would make the release artifacts.  
>> Another benefit is that this would give a single commit tag,  
>> rather than assembling from a number of revs. We could also  
>> individually tag the projects and copy those in, rather than from  
>> branches, if folks really use individually project tags. This  
>> wouldn't change the net effect.
>>
>> Thanks,
>> -Noah
>>
>> On Apr 12, 2009, at 10:37 AM, csev wrote:
>>
>>> Hi,
>>>
>>> Here is Sakai's WSRP Producer:
>>>
>>> https://source.sakaiproject.org/svn/sakai/tags/sakai_2-1-2/wsrp/
>>>
>>> The last time this was tested was Sakai 2.1 - I remember testing  
>>> this with Sakai 2.2 but somehow in 2.2 and later it was dropped  
>>> from the release and dropped from the main SVN.
>>>
>>> I am sure it would take some effort to make it work with a modern  
>>> version of Sakai (2.5, trunk, etc).
>>>
>>> As a side note, this shows a flaw in making branches and tags  
>>> nothing but .externals (which we have done since Sakai 2.2) - it  
>>> means that when we drop top-level directories from the repo -  
>>> effectively all of their branches and tags are dropped as well.
>>>
>>> This is leaving us in a position to be unable to generate earlier  
>>> releases.  This is not such a good position to be in as a project  
>>> - perhaps we should go back to at least making branches real  
>>> rather than just a list of externals.  We should be willing to  
>>> make a full snapshot of our repo at least once per release cycle.
>>>
>>> /Chuck
>>>
>>
>> _______________________________________________
>> 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"
>