Hi, I will actually work soon on 2.1 issues (at least those I've opened). I also want to have a look to all existing 2.1 issues, to measure the distance to an eventual 2.1.12 release in a near future. So please don't close all 2.1 entries right now. It is IMHO a good thing to merge the two JIRA projects, but we should take care to the various components spread accross different versions. Cocoon 2.1 blocks are for instance a non sense for Cocoon 3, as well as Cocoon 3 components does not mean anything for Cocoon 2.x We could maybe rename such components with a prefix indicating their version ? Cédric Le 03/01/2012 11:59, Jasha Joachimsthal a écrit : Merging those projects is good, but only if we clean up COCOON. There is a long list of issues with patches (there used to be a weekly mail with them) and an even longer list of unresolved issues. If we keep these issues open, it will be harder to see what we're working on and what we're dragging with us for years. IMO we can close the 2.1 and 2.2 issues that were created in 2010 or earlier with resolution "won't fix". They can always be reopened (or re-created) when someone is actually going to work on them. --
Toute modification, édition, utilisation ou diffusion non autorisée est interdite. Anyware Services décline toute responsabilité au titre de ce Message s'il a été altéré, déformé, falsifié ou édité, diffusé sans autorisation. |
- JIRA "unification" proposal Francesco Chicchiriccò
- Re: JIRA "unification" proposal Jasha Joachimsthal
- Re: JIRA "unification" proposal Cédric Damioli
- Re: JIRA "unification" prop... Francesco Chicchiriccò
- Re: JIRA "unification" prop... Kaj Kandler
- Re: JIRA "unification" ... Cédric Damioli
- Re: JIRA "unification&q... Kaj Kandler
- Re: JIRA "unification" proposal Thorsten Scherler
- Re: JIRA "unification" prop... Simone Tripodi
- Re: JIRA "unification" ... Francesco Chicchiriccò
- Re: JIRA "unification&q... Jasha Joachimsthal