On Nov 17, 2007 9:49 AM, Ralph Goers [EMAIL PROTECTED] wrote:
...If someone finds a bug and wants to fix it and do a release of 2.1.x
they should be free to do so
Grzegorz Kossakowski wrote:
...After 2.1.11 I would like to close 2.1.x branch completely
Agree with Ralph, there's no
Carsten Ziegeler wrote:
If I get enough positive feedback about the current state I'm happy to
prepare a release of 2.1.11 in December.
the lenya community would appreciate that a lot! i'm collecting some
cocoon-specific user feedback on our lists atm. there have been no
problem reports
Hi Cocoon devs
Am 15.11.2007 um 15:41 schrieb Carsten Ziegeler:
We have no real plans or another 2.1.x release, although we talked
briefly about it over the last year several times. I think it makes
sense to do a 2.1.11 release as a maintenance release, especially if
Lenya wants to use this
On Fri, 2007-11-09 at 05:41 -0800, Thorsten Scherler (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COCOON-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thorsten Scherler updated COCOON-2145:
--
Attachment:
Bertrand Delacretaz escribió:
Agree with Ralph, there's no need to close anything, if people want
to fix bugs on older versions that's one of the beauties of open
source: no one forces you to upgrade, as long as you're ready to fix
what you're using if needed.
+1
Best Regards,
Antonio
Antonio Gallardo wrote:
Bertrand Delacretaz escribió:
Agree with Ralph, there's no need to close anything, if people want
to fix bugs on older versions that's one of the beauties of open
source: no one forces you to upgrade, as long as you're ready to fix
what you're using if needed.
+1
Bertrand Delacretaz pisze:
On Nov 17, 2007 9:49 AM, Ralph Goers [EMAIL PROTECTED] wrote:
...If someone finds a bug and wants to fix it and do a release of 2.1.x
they should be free to do so
Grzegorz Kossakowski wrote:
Agree with Ralph, there's no need to close anything, if people want
If you fix a bug in 2.1 it should obviously go to trunk. 2.1.11 has not
been released so if you know of a bug that applies to 2.1.x that is
fixed in trunk, IMO it should also be applied to 2.1.x. I would
recommend that this policy be followed until 2.2.0 is released. Past
that I would suggest
