Hey,

Jason and I talked and agreed that this should be part of the infrastructure bug that has been submitted (last week) about what needs to be done to move Xerces to a TLP. They have not got back to me yet. I would expect them to next week.

Cheers,

Gareth

James Berry wrote:
Hi Jason,

Any status on this?

-jdb

On Mar 18, 2005, at 7:53 PM, Jason E. Stewart wrote:

**

*From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> (Jason E. Stewart)

*Date: *March 17, 2005 5:36:15 AM PST

*To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>

*Subject: **Xerces-C migration from CVS to SVN*



Hello Infrastructure team,


The Xerces-C project has decided to move to subversion and all

committers have agreed on the following proposal, so we need your

help, along with an indication about when it can be done.


Xerces has now become a TLP, so I'm not sure where the SVN wants to be

rooted, but once it's in SVN it could be easily shifted I suppose.


Thanks for your time,

jas (proxy for xerces-c committers)


<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] <mailto:[EMAIL PROTECTED]>

For additional commands, e-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>



-- Gareth Reakes, Managing Director Parthenon Computing +44-1865-811184 http://blog.parthenoncomputing.com/xerces/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to