On 03/11/2013 05:22 PM, Jonathan Wiltshire wrote:
On 2013-03-11 10:18, Tomasz Muras wrote:
On 03/11/2013 10:49 AM, Didier 'OdyX' Raboud wrote:
So as much as I find that unfortunate, I think that the best solution
for all
of Moodle, Moodle-in-Debian and Debian, is to not ship Moodle 2.2 in
Wheezy.
I have exactly the same concerns. Security fixes has been released
for Moodle 2.2 today. I could cherry pick the patches and we could
close this bug - not a big deal. They will probably be another
security update for Moodle this year but that's it.
Realistically speaking there is no way I can maintain security fixes
for non-supported (by upstream) software this size.
I have put Moodle 2.2 into Wheezy as that's the only possible upgrade
path for Moodle (1.9 -> 2.2 -> 2.3+).
By not shipping 2.2 in wheezy, we will break the upgrades for any
current users. I don't see any other option though. There are talks in
Moodle about making LTS version (e.g. 2.6LTS) - and that's probably
the only reasonable way to maintain a high quality package like this
in Debian.
We have found this elsewhere too (e.g. mediawiki, where they are moving
to a six-month cycle but adding LTS releases for distributions).
+1 for not shipping 2.2, breaking the upgrade path for this package,
start from 2.5 (or higher) in unstable and provide Moodle LTS editions
in Debian stable only.
Just to clarify before I do it: stable stays as it is; remove moodle
from Wheezy and you will work on the basis of getting 2.5 into Jessie?
Intermediate versions can always go into backports of course.
Correct. 1.9 is still supported (it won't be for long) and can stay in
stable.
I am thinking that I would would package 2.5 and then 2.6 in unstable
and do not let it migrate into testing - unless LTS upstream version is
released. Does it make sense?
One thing I'm not sure about is what will happen to current users of
moodle package. They have 1.9 in squeeze, there will be nothing in
wheezy but then the package will appear back in jessie - but with no
upgrade path. The only way to get moodle back will be to drop the
package completely (and drop DB) and re-install it. Of course we could
provide some manual instructions to install 2.2 package and then upgrade
to 2.4.
Tomek
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
