[sakai2-tcc] Emerging consensus to focus on 2.10

[Matthew Jones]

As far as your questions go?

On Fri, Sep 6, 2013 at 4:33 AM, Jean-Francois Leveque <
jean-francois.leveque at upmc.fr> wrote:
>
> In order for 2.9.4 to be released, we need merges, QA and release work.
> Did I forget something?
>
>      Do we still have QA volunteers for 2.9.4?
>

We have limited volunteers to do QA. In order to get trunk out, we'll need
to get many issues that are resolved/unverified in trunk resolved. We'll
also want regression testing. Some of this testing is applicable to the 2.9
release as if bugs are verified they can get merged back, but we may want
more verification on features and fixes not getting back. So QA isn't
specifically assigned, it's wherever the release team directs our attention.


>      Do we still have 2.9.x maintenance merge volunteers?
>

2.9.x merges don't require much work and Longsight will continue to merge
bugs into 2.9.x as we have been at least until 2.10 is released. I'm sure
Michigan will be the same. The more things that get merged into the
branches, the less work we have to do locally on maintaining a fork.

     Do we have a release building volunteer and if we don't, how much
> work is it (learning and doing)?
>

I most likely still will have time, the release takes 4-6 hours depending
on what goes wrong and it has to run overnight. It's well documented, but
someone moderately technical will need to take over the current process as
sometimes the ruby scripts break down, or sometimes Jenkins doesn't start
up and you have to manually go in and fix it. The time to train someone
this late in 2.9 isn't worth it when we plan to change the process for
2.10. I've went through the process before with Sam and it's not too far
different from the old process that Steve and Anthony were working on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130906/f857b896/attachment-0001.html