Carsten Ziegeler skrev:
Our last official release has happened a long time ago...
I think it's time to release something again :) Imho we should release
2.2-M2 asap and 2.1.10 as well. I think 2.1.10-dev is currently working
pretty fine and there shouldn't be any outstanding issues. Or did I
oversee something?
The release of 2.1.10 should be the last planned release for 2.1.x - we
should drop the block sharing between trunk and the branch of the blocks
right after the release and continue development of things only in trunk
from that point on.
Only bug fixes should go to 2.1.x from that point on. This will ensure
that we have to work on trunk to get a new feature release out and will
stop people from adding everything to 2.1.x (hopefully).
So my idea is to release 2.1.10 in the midth of November and do at the
same time (or even before) a release of 2.2-m2. We can then target the
final release of 2.2 for December.
WE SHOULD REALLY GET 2.2 OUT *THIS YEAR*.
If some parts of the new blocks stuff are not working at that time it is
not that important. We can easily fix this with a 2.2.1 release or
(2.3).
The blocks can and should have own release cycles, so there is no need
to wait for the blocks fw to become stable. It can be in alpha state
until it is mature enough.
For a 2.2 release to make sense we need to simultaneously release enough
with important blocks to make it usable. But as we have discussed
plenty of times earlier everything after 2.1.x should be released in
terms of blocks (or Maven modules) instead as the whole of Cocoon trunk.
Although I totally agree that documentation for 2.2 is really
really important, let's not see this as a blocker. Either people will
document stuff or not, but we will not enforce this by blocking the
release. I'll work on the docs for the new core stuff next week and add
the missing pieces.
So, WDYAT?
Sounds like a good plan.
+1
/Daniel
