fine for me, although there are more than 70 issues scheduled in jira for 3.0-rc3 at this moment :/
maybe we should take some time to *really* schedule bugfixes and enhancements across releases and start using jira to understand when a release is ready. A good topic for the next weekend :) ... what about an on site "jira hackatlon" with a definitive scheduling and cleanup? fabrizio On 9/15/06, Philipp Bracher <[EMAIL PROTECTED]> wrote:
Hi List We would like to make a code freeze (excluding bugfixes) on Wednesday 20th. Followed by a week of bugfixing only. This means I would branch a 3.0 version on Wednesday evening. To this branch we commit only bugfixes to. This guarantees that any changes on the trunk will not touch the to releasing version. I will merge then this branch on a regular base to the trunk. After the fixing week we release RC3. For releasing we will use a yet to finish building system which creates the packages we deliver (tomcat bundle, ...). In my point of view there is one open major change to discuss here, which is the persisting of the workitems and a possible improvement of the inbox. If possible I would like to use the new persistence Nicolas and John made in 3.0 RC3. Everything else (excluding bugfixes) will get postponed to the next version. Is this reasonable for you both Nicolas & John? Can you change the persistence and commit until Wednesday evening? Hope this is reasonable for everyone here. Philipp
---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
