You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2004/07/29 08:41:41 UTC
Status of SVN Conversion?
Just curious: what's the status of the SVN conversion?
Carsten
Carsten Ziegeler
Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.net/weblogs/rael/
Re: Status of SVN Conversion!!!
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 2 Aug 2004, at 15:26, Vadim Gritsenko wrote:
>> 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).
>
> If it's only new kernel, then it's not a branch anymore - but
> subdirectory in whiteboard. I'd postpone changes in this branch till
> we complete mering in changes into 2.1.6 and Fortress migration.
>
+1 :-D
Pier
Re: Status of SVN Conversion!!!
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Carsten Ziegeler wrote:
> I think the next steps should be:
> a) merge things back from 2.2 to the 2.1.x branch
Yup.
> 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?
That's an option.
> 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).
If it's only new kernel, then it's not a branch anymore - but
subdirectory in whiteboard. I'd postpone changes in this branch till we
complete mering in changes into 2.1.6 and Fortress migration.
Vadim
RE: Status of SVN Conversion!!!
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
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:vadim@reverycodes.com]
> Sent: Thursday, July 29, 2004 5:27 PM
> To: dev@cocoon.apache.org
> 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
>
Status of SVN Conversion!!!
Posted by Vadim Gritsenko <va...@reverycodes.com>.
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
RE: Status of SVN Conversion?
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Ok, it seems that it works (=compiles), but I think it's not ready to go.
The svn:ignore properties are missing!
Carsten
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Thursday, July 29, 2004 8:47 AM
> To: Cocoon-Dev
> Subject: Re: Status of SVN Conversion?
>
> Carsten Ziegeler wrote:
> > Just curious: what's the status of the SVN conversion?
>
> That is something that we are all wondering.
>
> I just presumed that is was ready to go and got it like this:
> svn co https://svn.apache.org/repos/asf/cocoon/trunk cocoon
>
> --
> David Crossley
>
Re: Status of SVN Conversion?
Posted by David Crossley <cr...@apache.org>.
Carsten Ziegeler wrote:
> Just curious: what's the status of the SVN conversion?
That is something that we are all wondering.
I just presumed that is was ready to go and got it like this:
svn co https://svn.apache.org/repos/asf/cocoon/trunk cocoon
--
David Crossley