> > To that I would add a release plan: > > RC2 - in a week, this time with an anouncement (given that we have a > willing release manager) > RC3 - a month after RC2 > 2.2 - a month after RC3
Definitely +1 I (even when I'm not a new user of cocoon, but I haven't fully followed the migration to C22) managed with the existing docs to migrate applications from C21 to C22. Many parts of the C21 documentations are still usable for C22 or can give at least good starting point for help. > > We can skip RC3 and go directly to 2.2 if we are in a hurry. The idea is > that we release unconditionally as is on these dates. If we decide for a > certain feature or piece of documentation we will continue to just wait > for ever. > > OK, we could go for 2.2 directly without any RCs, I will not vote > against it. But one or two RCs will give us some valuable user feedback > and it will also increase the interest during a longer period. I wonder if it wouldn't make sense to publish the existing documentation to the productive area with the next RC to get more valuable user feedback. How many user feedback we got after releasing RC1 and having the documentation only on daisy's site and on cocoon.zones.apache.org? I haven't seen much feedback about documentation on these sites. I'm pretty sure this will not change when keeping the documentation on these 'developer' sites. Felix
