"b) to keep the complete OOo HG repo in apache-extras to > keep the CWS developments but also to keep the repo > history for reference. >
"This is correct and is done already." Where? I see that there is an ooo project there, but I see no code. -----Original Message----- From: Pedro F. Giffuni [mailto:[email protected]] Sent: Wednesday, August 10, 2011 08:27 To: [email protected] Subject: Re: [Repo] SVN ETA? (was Re: Request for comments: Community Wiki Services web page.) --- On Wed, 8/10/11, Marcus (OOo) <[email protected]> wrote: ... > > > > Let me try to recap the consensus so far. I was on > vaction for two > > weeks, so I was not involved in all discussions. > > > > A full conversion hg -> svn for the trunk > repo and all cws is considered > > to be impossible, so all conversions will happen on > the trunk repo only. > > > > It was mentioned that preserving history looks hard, > so most of us > > agreed to move over the tip from the trunk repo into > svn only, without > > history. > > I had the impression that we agreed on > > a) moving the OOO340m1 tip into ASF SVN and to loose > history, so that we can start with further improvements > very fast and > Lose ALL history? I was under the impression we wanted to keep at least keep the trunk history in SVN. > b) to keep the complete OOo HG repo in apache-extras to > keep the CWS developments but also to keep the repo > history for reference. > This is correct and is done already. > So, at the end there is indeed a way to keep every data + > history but also to start with new developments in ASF > SVN. > I suggest that we do the CWS merge (only branch merging, no new code) in apache-extras. Doing it there is better than just committing a big patch in subversion and this gives a bit more time for the SVN conversion (if it's going on). Pedro.
