I haven't got it: How are we able to release e.g. 2.1.2 without a branch/new repository without using e.g. Fortress as container (nothing against Fortress, I'm no specialist in these container things and maybe this is the reason for my concerns)? I would like to give us some time until we do a "production ready" release with all those new things. In the meantime we should always be able to do a stable 2.1.x release?
Did I miss something?
Nope, you've got my 'hint'. ;-)
IMHO, it's simply unworkable to have major stuff going on in one module, over two branches, at the same time. We've been there before with the docs and Cocoon2. Now however, some people were quite vocal in explaining they still wanted to stick to one module & branch. If they do the actual work, they get to decide how things are done (tm). But vice-versa as well, of course, which seems to be what Carsten is pointing at.
See Sylvain's reply as well.
I'm +1 on a 2.2 module, and +1 on 2.1.1 on Friday. Fortress might be something for 2.2 rather than 2.1.1, but I'll leave that to the people doing the actual work to decide.
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source Java & XML An Orixo Member Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
