| Summary: | www-apps/moodle needs to more closely follow the weekly releases | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Derriks <j.derriks> |
| Component: | Current packages | Assignee: | Anthony Basile <blueness> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Derriks
2011-09-29 13:02:52 UTC
moodle-2.1.2 has not hit their repos yet. Thanks for alerting me to the issue, but I can't act on this. I'm usually very good about getting the latest ebuilds up within a day of the release, so don't worry about me lagging. I'm closing this invalid because I can't bump. Please open again to remind me if I don't get an ebuild out within a day of the release of 2.1.2. http://download.moodle.org/ I should have said 2.1.1+ or 21Stable. That has been released and has all the patches we need. Quote from the url above: "It contains a number of fixes made since the 2.1.1 release and is usually a better choice for production than the actual 2.1.1 package". (In reply to comment #2) > http://download.moodle.org/ > > I should have said 2.1.1+ or 21Stable. That has been released and has all the > patches we need. > Quote from the url above: "It contains a number of fixes made since the 2.1.1 > release and is usually a better choice for production than the actual 2.1.1 > package". Ah okay. I know the + version but I didn't know that's what you wanted. For QA reasons, we discourage the use of "live" ebuilds, ie following CVS/SVN/GIT heads. They are moving targets and hard to support because you never know what you're open up a bug against. Can this wait until the next release? If its as serious as suggested, then that'll be coming around the corner. Dear Anthony, Moodle2.0 has changed their release strategy to time-based releases on a 6-moth basis. Version 2.2 will come december 1st. See http://docs.moodle.org/dev/Roadmap That could make your job very easy, a bump two times a year :-) However, these new versions will probably have more bugs than a version some weeks later in the weekly-stable-branch. I'm not used to this kind of frequent patching either but I think it will mean that a 2.1.1+ of september will have more bugfixes than a 2.2 in december because new features will introduce new bugs. So I agree that we shouldn't follow the unstable head of the GIT repo but that is exactly what you will do if you only take the 2.1 2.2 2.3 semester-releases without patches. Better pick one of the weekly releases from the stable list some time after the major release, marked as "weekly release 2.1.1+". I guess that's why 2.1.1+ is called "stable" and 2.1 is not. Look at the git log for the weekly releases: http://git.moodle.org/gw?p=moodle.git;a=log;h=refs/heads/MOODLE_21_STABLE (In reply to comment #4) > Dear Anthony, > > Moodle2.0 has changed their release strategy to time-based releases on a 6-moth > basis. Version 2.2 will come december 1st. > See http://docs.moodle.org/dev/Roadmap > That could make your job very easy, a bump two times a year :-) This does not make my job easier. > > However, these new versions will probably have more bugs than a version some > weeks later in the weekly-stable-branch. I'm not used to this kind of frequent > patching either but I think it will mean that a 2.1.1+ of september will have > more bugfixes than a 2.2 in december because new features will introduce new > bugs. > > So I agree that we shouldn't follow the unstable head of the GIT repo but that > is exactly what you will do if you only take the 2.1 2.2 2.3 semester-releases > without patches. Better pick one of the weekly releases from the stable list > some time after the major release, marked as "weekly release 2.1.1+". I guess > that's why 2.1.1+ is called "stable" and 2.1 is not. > > Look at the git log for the weekly releases: > http://git.moodle.org/gw?p=moodle.git;a=log;h=refs/heads/MOODLE_21_STABLE What do you recommend for gentoo's ebuild schedule then? I'm not even sure what my strategy should be now. I'm reopening this and changing the summary. (In reply to comment #0) > Current moodle 2.1.1 has a serious bug in quiz system. Please update to 2.1.2. > 2.1.2 is now in the tree. I think there is some confusion above, the release cycle is 6 months for bumps to the minor release number not the patch level. ie 2.1 -> 2.2 is a 6 month cycle. But bumps like 2.1.1 -> 2.1.2 happen as needed. The upstream team does what most do, wait until enough critical fixes are in and then bumps the third number. I think I'm going to continue following upstream here. If, however, individual users isolate a patch which address some issue they want, I'll apply it and rev bump, ie moodle-2.1.1.ebuild -> moodle-2.1.1-r1.ebuild where the latter has the patch. If there are good arguments against this, please reopen and comment. Thanks. |
