I added a third point, see below: > Carsten Ziegeler wrote: > > Hmm, "release early" what does it mean? > I think we should release a new version before lunch. Is that > early enough? > > Ok, odd joke, let's get serious now: > > The problem with Cocoon and release early is the wast amount of > changes that occur between versions. But I really would like > to make a 2.0.2 asap. > As I couldn't follow all the changes and discussions in the > last two weeks, can someone summarize this please? Are the changes.xml > up-to-date? > > I have at least two topics I would like to address: > > a) Sitemap components in the cocoon.xconf. > Now, personally I don't like this - but that's my own opinion about this. > If you want to edit the sitemap, you not only have to look at the sitemap > but also at the cocoon.xconf. This makes handling the sitemap even more > complicated. > I know a lot of people complaining about the complexity of Cocoon and > the many places of configuration. By this splitting of component > definition > it gets even harder for beginners. > So I would like to have all these definitions back in the sitemap. > What is the benefit of having them in the cocoon.xconf? > > b) the sunRise and sunSpot components > What is the feeling of the community to move them out of the scratchpad > into the main trunk? I'm - of course :) - +1 on moving them. >
c) Rename the CVS repository as by Stefano's suggestion: Rename xml-cocoon to xml-cocoon1 and xml-cocoon2 to xml-cocoon to keep the history. > Cheers, > Carsten > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
