[cle-release-team] Need guidance to release content-review

[Matthew Jones]

I stand massively corrected, these were 29 pages that I didn't even know
existed. Without an Anthony style effort, I'm not sure this will be able to
be kept up. Some web script or something should be written to semi-automate
the generation of this information like on these pages:
https://confluence.sakaiproject.org/display/REL/sakai-2.8.1

Seems to be pretty useful, but quite (IMHO) hidden information, as I've
never clicked on it until today. :(

-Matthew

On Fri, Dec 23, 2011 at 9:10 PM, Anthony Whyte <arwhyte at umich.edu> wrote:

>
> It can be quite confusing when the versions don't match up (for indies
> they shouldn't be expected to match anything), and AFIAK we haven't been
> too good at keeping track of what is the latest version anywhere
> (confluence?) except maybe in the master?
>
>
> From 2.7.0 thru 2.9.0-a01, including all alpha, beta and release
> candidates, I produced a Confluence page for each tag that listed all
> associated indie releases.  These pages were created as I produced each
> tag.  I generated 29 pages.
>
> https://confluence.sakaiproject.org/display/REL/Releases
>
> Anth
>
>
>
> On Dec 23, 2011, at 7:27 PM, Steve Swinsburg wrote:
>
> That branch name method is from the maven release plugin which I presume
> Chris was using? I am pretty sure profile2 has the same thing as that is
> how the branches have been made for a while.
>
> Cheers and merry Christmas to all!
>
> Sent from my iPhone
>
> On 24/12/2011, at 5:52, Matthew Jones <jonespm at umich.edu> wrote:
>
> Unless a branch was messed up before anyone had a chance of possibly using
> it, it really shouldn't be deleted. It makes it harder to check it out if
> anyone else was using it for some reason in their local builds or to find
> it again.
>
> The general policy should be:
>
> Copy from trunk to a branch:
>   - Only merge bugs from trunk to the branch
>     - Features when they are small and approved
>   - Branch should only be deleted/replaced if it was a made in mistake and
> no tags or nothing is referencing it yet.
>
> Tag a branch "when needed". This is different for core and indies, as well
> as different for those that are have project maintainers or those on the MT.
>
> It can be quite confusing when the versions don't match up (for indies
> they shouldn't be expected to match anything), and AFIAK we haven't been
> too good at keeping track of what is the latest version anywhere
> (confluence?) except maybe in the master?
>
> In the case of content review, it was already 2.9-SNAPSHOT in trunk, so
> creating the 2.9.x branch and pushing trunk to 2.10-SNAPSHOT seems like a
> good enough idea and easier than merging any changes, though if there
> wasn't any major changes this is all we should have really had to do.
>
> Also, it looks like for all of the new tool branches you named them
> <toolname>-<branch version. like *assignment/branches/assignment-2.9.x*
> where for all of the old branches we were just using the pattern of
> *assignment/branches/2.8.x*
>
> I really don't particularly like all of the redundancy in path names, but
> I guess this is more nitpicking on something that should be added to a
> cleanup task when we get time.
> It's not as bad as config where to even GET to the config properties you
> have to look at: (3 times bundle and 3 times config is in a directory name!)
> *
> config/branches/sakai-2.9.x/configuration/bundles/src/bundle/org/sakaiproject/config/bundle/
> *
>
> Thanks though, haven't paid too much attention but looks good.
>
> -Matthew
>
> On Fri, Dec 23, 2011 at 11:15 AM, Maurer, Christopher Wayne <
> chmaurer at iupui.edu> wrote:
>
>>  Since I have heard nothing on this, I'm going to make an executive
>> decision to just make a new branch off of the trunk (preserving the old
>> branch, just in case).  I'll then set trunk as 2.10-SNAPSHOT.
>>
>>  Chris
>>
>>   From: Chris Maurer <chmaurer at iupui.edu>
>> Date: Fri, 23 Dec 2011 00:13:07 +0000
>> To: David Horwitz <david.horwitz at uct.ac.za>, Steven Githens <
>> sgithens at iupui.edu>
>> Cc: "cle-release-team at collab.sakaiproject.org" <
>> cle-release-team at collab.sakaiproject.org>
>> Subject: [cle-release-team] Need guidance to release content-review
>>
>>   And more importantly, where should it be released from?  I see that
>> there is a contentreview-2.9.x branch, but it seems to be a bit out of date
>> compared to trunk.  I guess I'd like some guidance here as to where to
>> release from and what version to release it as.  When we did 2.9.0-a01, it
>> was made from trunk.  I could delete (or rename) the existing branch and
>> create a new one from trunk.  Then, perhaps release it as 2.9.2-b01?
>>  Thoughts?
>> I can't release anything else until we decide on this, so if folks
>> familiar with this module could chime in, that'd be great!
>>
>>  Chris
>>
>>   From: Chris Maurer <chmaurer at iupui.edu>
>> Date: Thu, 22 Dec 2011 15:33:39 +0000
>> To: David Horwitz <david.horwitz at uct.ac.za>
>> Cc: "cle-release-team at collab.sakaiproject.org" <
>> cle-release-team at collab.sakaiproject.org>
>> Subject: Re: [cle-release-team] Most indies are released now
>>
>>   So, word on the street is that David Horwitz is in charge of
>> content-review…so, David…what version would you like it to be released as?
>>
>>  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
>
> _______________________________________________
> 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/20111223/bd4dd078/attachment-0006.html