Re: lenya 2.0 release preparation - cocoon version dependency (2.1.11?)
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 that fixes be targeted to 2.2. If something critical were to come up that could affect 2.1 it would be nice to have it mentioned here so that someone who cares could apply it if they want to. Ralph Grzegorz Kossakowski wrote: 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 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. Ok, lesson taken. :-) Just to clarify, we don't have policy to keep 2.1 and trunk in sync, anymore. Right?
Re: lenya 2.0 release preparation - cocoon version dependency (2.1.11?)
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 > 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. Ok, lesson taken. :-) Just to clarify, we don't have policy to keep 2.1 and trunk in sync, anymore. Right? -- Grzegorz Kossakowski Committer and PMC Member of Apache Cocoon http://reflectingonthevicissitudes.wordpress.com/
Re: lenya 2.0 release preparation - cocoon version dependency (2.1.11?)
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 +1 Cheers Michael Best Regards, Antonio Gallardo. -- Michael Wechner Wyona - Open Source Content Management - Yanel, Yulup http://www.wyona.com [EMAIL PROTECTED], [EMAIL PROTECTED] +41 44 272 91 61
Re: lenya 2.0 release preparation - cocoon version dependency (2.1.11?)
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 Gallardo.
Re: [jira] Updated: (COCOON-2145) Input module to return absolute file location of a block
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: COCOON-2145.patch > > If you think it is useful, please review the patch. > > If you want I commit it. Did anybody look into this patch? Can I commit it? TIA for any feedback salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
Re: lenya 2.0 release preparation - cocoon version dependency (2.1.11?)
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 version. However, the only problem I see right now is the question of the qualitify. Which means, how many people are using latest svn and/or have tested it? If I get enough positive feedback about the current state I'm happy to prepare a release of 2.1.11 in December. Thanks a lot for the feedback! A december release would be a great perspective for our project and would help us a lot to roll out lenya in a smooth way. As you might have noticed we opened a thread in our user mailing list asking for feedback if our users know of any cocoon related issues - we'll let you know if there are any reports. For quite a while now, the cocoon 2.1.x trunk is fetched as a svn external during lenya svn checkout and lenya seems to be running fine with it. Jürgen null-oder-eins GmbH Zürich web & graphic design www.null-oder-eins.ch [EMAIL PROTECTED] Skype: callto://ragaller
Re: lenya 2.0 release preparation - cocoon version dependency (2.1.11?)
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 whatsoever, and a few people have reported "works for me". the majority of users have not replied yet, which could be interpreted as "works *perfectly* for me" :-D of course, lenya uses only a subset of cocoon 2.1.11-dev, but this subset at least should have gotten a fair bit of testing lately. the last cocoon breakages i can recall were those induced by shared code with 2.2, which has been remedied a while ago. regards, and thanks for your great work! jörn -- Jörn Nettingsmeier "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson.
Re: lenya 2.0 release preparation - cocoon version dependency (2.1.11?)
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 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. -Bertrand
