Jason,
Thanks for your work on this. It looks good to me.
Here's my +1 to send it off and get it done.
One question that is not addressed in your proposal below, and which should probably be addressed, is what the final location we'll have in svn, given that xerces is now a TLP. Will there be xerces at the top level, with subdirectories for c, j, and p? You suggest this to infrastructure, given the tlp rating, and see what they recommend.
-jdb
On Mar 4, 2005, at 11:54 PM, Jason E. Stewart wrote:
Hi All,
Here is the first draft of the final proposal that we need to send to the infrastructure team.
From what I could tell, Xerces-C maintains the website from withingthe xml-xerces/c/doc/html directory - we may want to change this, but that can be done most simply *after* converting to SVN. So our request seems really, REALLY simple - just convert all of the CVS repository to SVN and then we'll take it from there.
We should begin a seperate discussion about what to do after the migration.
All comments welcome.
Cheers, jas.
--
The Xerces-C project has decided to move to subversion, so we need your
help, along with an indication about when it can be done. TIA
<quick-summary> We need to export
xml-xerces/c
to SVN and then lock the CVS module.
The resulting repo we need is:
/xerces-c/ /trunk/ (xerces-c HEAD) /tags/ (xerces-c tags) /branches/ (xerces-c branches)
</quick-summary>
<long-version>
The modules we need to move are:
xerces-c/ -> current trunk + site
Basically, this is what we need:
1: convert xerces-c to SVN
xml-xerces/c CVS
| | V /xerces-c/ /trunk/ /tags/ /branches/
Thus resulting into:
/xerces-c/ /trunk/ (xerces-c HEAD) /tags/ (xerces-c tags) /branches/ (xerces-c branches)
</long-version>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]