Really great work, thanks Vadim!!! I think the next steps should be: a) merge things back from 2.2 to the 2.1.x branch
We should backport all bug fixes, especially the fix for the sitemap reloading problem. What do you think about tracing the status of the merge (which block has already, which needs to etc.) on the wiki? b) clean up the directory for the new kernel proposal I think the new kernel should only contain the kernel but not the whole cocoon stuff; it's outdated anyway. Most of the stuff we have added to our cocoon-2.2 CVS repo is now in the cocoon/trunk (apart from the Fortress migration). Carsten > -----Original Message----- > From: Vadim Gritsenko [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 29, 2004 5:27 PM > To: [EMAIL PROTECTED] > Subject: Status of SVN Conversion!!! > > Carsten Ziegeler wrote: > > > Ok, it seems that it works (=compiles), but I think it's > not ready to go. > > Sorry, guys - forgot to post status :-) > > Cocoon 2.2-dev is here: > http://svn.apache.org/repos/asf/cocoon/trunk/ > > Cocoon 2.1.6-dev is here: > http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/ > > Cocoon Site is here: > http://svn.apache.org/repos/asf/cocoon/site/ > > Cocoon released versions are all listed here: > http://svn.apache.org/repos/asf/cocoon/tags/ > > Butterfly is here: > http://svn.apache.org/repos/asf/cocoon/branches/butterfly/ > > > Committers have to use https:// protocol, users can use > http:// protocol. Committers have to create a password for > using Subversion by logging in to minotaur and running > "svnpasswd" command. > > > For users of Cygwin, use cygwin's setup.exe to get cygwin > version of the subversion :-) > > Vadim >
