[sakai2-tcc] Sakai 2.5 status

[Matthew Jones]

I agree on 2.5.x. Getting an actual tagged release would mean putting it up
on a QA server, and running tests against it. I'd also like to repurpose QA5
for something related to 2.7 or 2.8 in the near future rather than leaving
it as a 2.5 QA, since we aren't running on 2.5 any longer at Michigan and we
haven't been for over a year.

As you'd said in (2), if someone really wants to volunteer to maintain 2.5
that would be up to them,  but time is better spent on the future on the 2
stable releases (2.6, 2.7) as many fixes are very difficult/time consuming
to back-port to older releases.

-Matthew

On Tue, Jul 20, 2010 at 10:51 AM, Anthony Whyte <arwhyte at umich.edu> wrote:

> I just sent a draft email to the Security WG partly in regards this topic.
>
> My recommendations:
>
> 1.  Continue to merge security-related fixes to 2.5.x until 2.6.3/2.7.1 are
> released.  I've recommended that the latter be released jointly no later
> than the second week of August.  We should debate this general date as
> necessary.
> 2.  Consider all non-security merges to 2.5.x as purely voluntary work and
> not a requirement for any branch manager to undertake.
> 3.  Given our resource constraints as well as community traditions, no
> community-sponsored 2.5.7 release will occur.
>
> In other words, notwithstanding any security fixes we choose to merge to
> 2.5.x, we are done with the 2.5 series.  In my opinion we have met our
> Denver goal, thanks largely to Steve Swinsburg.
>
> If there are people/institutions in the Sakai Community who wish to
> maintain 2.5.x bully for them but our focus lies elsewhere.  It's to the
> horizon we should be looking, not to our wake.
>
> Cheers,
>
> Anth
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100720/bdaff235/attachment.html