[cle-release-team] Revision # question

Neal Caidin neal.caidin at apereo.org
Mon Oct 14 08:01:11 PDT 2013


Ah, okay. 

For these close ones, I probably will ask ticket owners. Most likely more efficient than me sleuthing, as fun as it sounds to look through specific commits! ;-)

Cheers,
Neal



Neal Caidin
Sakai CLE Community Coordinator
neal.caidin at apereo.org
Skype: nealkdin
Twitter: ncaidin









On Oct 14, 2013, at 10:32 AM, Matthew Jones <matthew at longsight.com> wrote:

> You can always go to
> https://source.sakaiproject.org/viewsvn/
> 
> Then click basiclti -> tags and the tag you're interested in. It's still confusing in 2.9 because it uses the 2.1 tags, so 2.1.1 would have went with 2.9.3.
> (Thats in the master 2.9.3 pom.xml : https://source.sakaiproject.org/svn/master/tags/master-2.9.3/pom.xml and in the all externals https://source.sakaiproject.org/svn/sakai/tags/sakai-2.9.3-all/.externals )
> 
> Anyway, on that 2.1.1 tag, the revision next to that tag is when that indie was cut. This is 128788 which is slightly less than 128968. The indies are cut a day or so before the final release so some indie if they're *close* might not be included, you'd have to really dig in to double check. If you still weren't sure, on this page you can click on that revision number and it shows you all of the SAK's that are included in that tag.
> 
> You could probably write a script that would be like
> Download the -all externals https://source.sakaiproject.org/svn/sakai/tags/sakai-2.9.3-all/.externals
> 
> For each revision in the externals (
> svn info on that revision
> } 
> 
> So for example svn info https://source.sakaiproject.org/svn/basiclti/tags/basiclti-2.1.1
> 
> The value there of "Last Changed Rev: 128788" is the one you want. Maybe that's the fastest way.
>  
> 
> 
> 
> On Mon, Oct 14, 2013 at 8:03 AM, Neal Caidin <neal.caidin at apereo.org> wrote:
> [sakai cle release team]
> 
> Hey all,
> 
> This is an administrative question. I am going through some tickets w/o fix versions to see if I can identify issues which will be fix version of 2.10 when we branch.
> 
> This is an interesting case.
> 
> https://jira.sakaiproject.org/browse/SAK-24145
> 
> I thought this issue would have a fix version of 2.9.3 because the  revision number is 128968, which is in between 2.9.3 (129049) and 2.9.2 (125350).  But Dr. Chuck says no, it is 2.9.4 ?  
> 
> Can you tell me where my logic is off?
> 
> Thanks,
> Neal
> 
> 
> 
> Neal Caidin
> Sakai CLE Community Coordinator
> neal.caidin at apereo.org
> Skype: nealkdin
> Twitter: ncaidin
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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/20131014/3179c081/attachment.html 


More information about the cle-release-team mailing list