[WG: Sakai QA] Potential 2.9.0 blocker

[Matthew Jones]

I think this would be more of a question for tomorrow. I don't consider
this a blocker because it doesn't prevent core functionality of Lessons.
There are however options that we'd probably want to discuss at tomorrow
meeting. (The 2.9.0 wouldn't start until later tomorrow anyway)

- Since 2.9.0 isn't going to be an *exact copy *of rc03 (everything has to
be re-released) we could just include this fix and continue with 2.9.0 as
planned.
  - I don't even know how I'd technically do an 'exact copy'. What we were
going to do as procedure is not merge anything for this week to keep it
exact. However it looks like this fix is already merged into the
appropriate Lessons branch so it would be picked up no matter what we did.
(Unless we actively reverted it)
- We could re-release *everything* again as rc04 and delay the release
until the next release window (which was defined as 11/20)
- We could do a new release of only Lessons with this fix and include that
in the 2.9.0. This might be a more proper procedure, but it wouldn't
*really* make any difference as 2.9.0 is different than 2.9.0-rc03
(1.4.0-rc03 in Lessons case). This would be a good idea for a 2.9.1 release
though.

We really just need to get over this 2.9.0 release hurdle, then indies can
release on their own whatever versions they want, and only the core is
bound to the release version tag. I think everything would just work out
better.

I'd lean toward testing this on the 2.9.x nightly server, if it works there
just release 2.9.0 as planned including this fix.


On Wed, Nov 7, 2012 at 10:18 AM, Neal Caidin <nealcaidin at sakaifoundation.org
> wrote:

> Not sure I understand the question. I think we would test the latest fix
> on LSNBLDR-144 in trunk and then merge it in. If there are no other
> blockers then that would be the scope for RC04.
>
> Cheers,
> Neal
>
>
> On Wed, Nov 7, 2012 at 8:56 AM, Berg, Alan <A.M.Berg at uva.nl> wrote:
>
>>  Collecting information to form an opinion. Rc's are used to converge on
>> stability with very little change. If there was a RC04 then what would be
>> the scope of the patching?
>>
>>
>> Regards,
>>            Alan
>>
>>
>> Alan Berg
>>
>> Innovation working group
>> On the use of ICT in Education & Research
>> University of Amsterdam
>>      ------------------------------
>> *From:* sakai-qa-bounces at collab.sakaiproject.org [
>> sakai-qa-bounces at collab.sakaiproject.org] on behalf of Neal Caidin [
>> nealcaidin at sakaifoundation.org]
>> *Sent:* 07 November 2012 14:45
>> *To:* cle-release-team at collab.sakaiproject.org; Sakai QA
>> *Subject:* [WG: Sakai QA] Potential 2.9.0 blocker
>>
>>  Hi All,
>>
>> https://jira.sakaiproject.org/browse/LSNBLDR-144
>>
>> The QA team met this morning and reviewed the RC03 testing. We found one
>> potential blocker in the Lessons tool, but since Lessons is new to core
>> Sakai, we recommend not treating this as a blocker, but including in the
>> release notes, and planning to include in 2.9.1 (actually Chuck Hedrick has
>> already fixed the issue in trunk). The Lessons' comment tool is not usable
>> by students in 2.9.0-rc03. It is usable in previous versions of Lessons,
>> and worked in one of the earlier beta releases of 2.9.0.
>>
>> We wanted to check with the team to be sure that this should not be a
>> blocker for 2.9.0 . Do you agree with the QA team recommendation?
>>
>> P.S. We plan to continue testing today, but we have covered all the areas
>> we were hoping to check for RC03.
>>
>> Thanks,
>>
>> --
>> Neal Caidin
>> Sakai CLE Community Coordinator
>> nealcaidin at sakaifoundation.org
>> skype: nealkdin
>>
>>
>>
>>
>
>
> --
> Neal Caidin
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> skype: nealkdin
>
>
>
>
> _______________________________________________
> sakai-qa mailing list
> sakai-qa at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>
> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.orgwith a subject of "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20121107/c55f991c/attachment.html