[cle-release-team] sakai-10-qa01 branch vs tag?

[Kirschner, Beth]

Thanks Matt -- I've changed the "10.0" JIRA version to "10.0-qa01" and have added "10.0-qa02". If any bugs are fixed in trunk, they should probably set the fix version to "10.0-qa02".

- Betbh

On Dec 19, 2013, at 12:11 PM, Matthew Jones <matthew at longsight.com> wrote:

> Also to Beth's observation (I did this on Monday but looks like I forgot to send out a wide announcement)
> 
> I have built a Sakai 10-QA01 binary (~500MB)
> https://qa10.longsight.com/sakai-bin-10.0-SNAPSHOT-132648.tar.gz
> 
> And create a source tag (It points to externals as of around 9:30PM EST 2013-12-16) There were a few late breaking fixes that got in there including multithreading issue in assignments and a styling issue with formatted text processing.
> https://source.sakaiproject.org/svn/sakai/tag/sakai-10-qa01/
> 
> I'm running with all the properties enabled in local.properties mentioned on the MOTD and is started on.
> https://qa10.longsight.com/ logs at https://qa10.longsight.com/logs/
> 
> Alan and Chuck Hedrick said they would also start up servers. TBD. I also planned to start up a Spanish language version but not until January.
> https://confluence.sakaiproject.org/display/QA/QA+Servers+-+Sakai+10
> 
> Unless there is a serious blocker, there is no new tag expected until at *least* 2014-01-06, or more likely the week after. I will be only lightly monitoring email for the next few weeks.
> 
> One known issue is with portfolio sites not being able to be added. I'd consider this a blocker for a later QA release, but not for this one.
> https://jira.sakaiproject.org/browse/SAK-23775
> 
> Additional new issues discovered are being related on this ticket
> https://jira.sakaiproject.org/browse/SAK-25466
> 
> 
> On Thu, Dec 19, 2013 at 12:04 PM, Matthew Jones <matthew at longsight.com> wrote:
> I think I meant to put this in tags rather than branch, just mistyped, I think it was late. It really is a *tag*, but nothing was released. It just has version numbers in .externals that point to the versions used on the QA servers. I'll move it to the tags directory.
> 
> Individual tools were not tagged and nothing is branched. You need to check this "tag" directory out. I don't have time at the moment to release or really know the process for how we will do the release for this monolithic Sakai. I was hoping to maybe have something for Apereo Camp in that regard, though releases as they were done in 2.9 are less relevant.
> 
> Sounds like it should be created in jira though as you describe.
> 
> 
> On Thu, Dec 19, 2013 at 11:45 AM, Kirschner, Beth <bkirschn at umich.edu> wrote:
> It looks like we have a sakai-10-qa01 branch, but no tag. Is anyone planning on creating a tag? Is the intent to update this branch or to treat it like a tag?
> 
> Is anyone planning on creating a sakai-10-qa01 release version in JIRA? I can update JIRA, but feel like i've been out-of-the-loop on the actual branching / tagging discussion (probably my own fault). I'm assuming we'll be using JIRA in the same way as the past, where we create qa01, qa02, … rc01, rc02, … release 'versions', and once Sakai 10.0 is released, we'll consolidate them all into one 10.0 release?
> 
> Thanks,
> - Beth
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> 
>