You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Jason E. Stewart" <ja...@openinformatics.com> on 2005/02/20 11:17:32 UTC
[cvs => svn] new SVN repository structure
Hey All,
Email #2 in my series...
The current ASF repos at:
https://svn.apache.org/repos/asf/
has all the TLP's as top-level projects. Since Xerces-C is officially
still part of XML and not it's own TLP (true??), we would go under
https://svn.apache.org/repos/asf/xml/xerces-c
The current suggested repository style is to have
trunk/
branches/
tags/
site/
under the project directory. site/ would contain the website pages,
while trunk is the current HEAD, branches have any other active
branches, and tags all the historical tags.
<aside>
Once the whole thing is in SVN we can adjust the layout *very*
simply. Compared to CVS, SVN is truly a wonder when it comes to
adjusting the repository layout. You can move and rename directories
in zero time by using commands like "svn mv ..." and "svn cp ..."
which operate directly on the repository (and of course everything is
versioned in case you change your mind).
This means the projects directory structure can be easily cleaned up
as part of the autoconf cleanup for 3.0, without losing any project
history.
This also means that when Xerces becomes a TLP, the xml/xerces-c/
directory can be renamed to xerces/xerces-c/ and then xerces/xerces-j/
can be added. Eventually xml/xerces-p/ can be folded into xerces-c
during the 3.0 migration.
<aside>
So are people are comfortable with this?
+1 from me.
Cheers,
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] final proposal, first draft
Posted by Alberto Massari <am...@datadirect.com>.
Jason, here is my +1
Alberto
At 11.56 11/03/2005 +0530, Jason E. Stewart wrote:
>Gareth Reakes <ga...@parthenoncomputing.com> writes:
>
>
> > Hey, here is my +1, but I don't know if we really need a
> > vote. I say that because the Xerces TLP does not even have any
> > committers yet. We have a PMC (without a mailing list!!), but
> > thats it. I am still happy to go down this route if it means
> > we get it done sooner.
>
>Hey All,
>
>I asked for the vote just for my own CYA - I wanted to make sure that
>you all had seen the "official" letter to infrastructure in case I
>missed something...
>
>I'll add Gareth's comments about the TLP issue and resend.
>
>Cheers,
>jas.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] final proposal, first draft
Posted by Vitaly Prapirny <ma...@mebius.net>.
+1
> Hey All,
>
> I asked for the vote just for my own CYA - I wanted to make sure that
> you all had seen the "official" letter to infrastructure in case I
> missed something...
>
> I'll add Gareth's comments about the TLP issue and resend.
>
> Cheers,
> jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] final proposal, first draft
Posted by da...@us.ibm.com.
+1
> Gareth Reakes <ga...@parthenoncomputing.com> writes:
>
>
> > Hey, here is my +1, but I don't know if we really need a
> > vote. I say that because the Xerces TLP does not even
have any
> > committers yet. We have a PMC (without a mailing list!!),
but
> > thats it. I am still happy to go down this route if it
means
> > we get it done sooner.
>
> Hey All,
>
> I asked for the vote just for my own CYA - I wanted to make sure that
> you all had seen the "official" letter to infrastructure in case I
> missed something...
>
> I'll add Gareth's comments about the TLP issue and resend.
>
> Cheers,
> jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] final proposal, first draft
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
Gareth Reakes <ga...@parthenoncomputing.com> writes:
> Hey, here is my +1, but I don't know if we really need a
> vote. I say that because the Xerces TLP does not even have any
> committers yet. We have a PMC (without a mailing list!!), but
> thats it. I am still happy to go down this route if it means
> we get it done sooner.
Hey All,
I asked for the vote just for my own CYA - I wanted to make sure that
you all had seen the "official" letter to infrastructure in case I
missed something...
I'll add Gareth's comments about the TLP issue and resend.
Cheers,
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] final proposal, first draft
Posted by Gareth Reakes <ga...@parthenoncomputing.com>.
Hey,
Hey, here is my +1, but I don't know if we really need a vote. I say
that because the Xerces TLP does not even have any committers yet. We
have a PMC (without a mailing list!!), but thats it. I am still happy
to go down this route if it means we get it done sooner.
Cheers,
Gareth
On 10 Mar 2005, at 18:46, James Berry wrote:
> 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 withing
>> the 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: xerces-c-dev-unsubscribe@xml.apache.org
>> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
>
>
--
Gareth Reakes, Managing Director Parthenon Computing
+44-1865-811184 http://www.parthcomp.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] final proposal, first draft
Posted by James Berry <jb...@apache.org>.
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 withing
> the 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: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] final proposal, first draft
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
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 withing
the 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: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by James Berry <jb...@apache.org>.
On Feb 21, 2005, at 4:28 AM, Alberto Massari wrote:
> I don't know if the trunk/HEAD directory will be immediately used for
> breaking changes; in any case, it would be nice if the first thing we
> do after the import is a "svn cp" of it into a new
> "tags/xerces-2.x-head", so that we keep our options open for a 2.7
> release, containing the non-breaking changes committed since 2.6.
To alter this just slightly, I believe we should:
- Tag the freshly imported head as tags/cvs-import-point
- Create a new branches/xerces-2-head
-jdb
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by Alberto Massari <am...@datadirect.com>.
Hi Jason,
+1 for the new structure.
I don't know if the trunk/HEAD directory will be immediately used for
breaking changes; in any case, it would be nice if the first thing we do
after the import is a "svn cp" of it into a new "tags/xerces-2.x-head", so
that we keep our options open for a 2.7 release, containing the
non-breaking changes committed since 2.6.
Alberto
At 15.47 20/02/2005 +0530, Jason E. Stewart wrote:
>Hey All,
>
>Email #2 in my series...
>
>The current ASF repos at:
>
> https://svn.apache.org/repos/asf/
>
>has all the TLP's as top-level projects. Since Xerces-C is officially
>still part of XML and not it's own TLP (true??), we would go under
>
> https://svn.apache.org/repos/asf/xml/xerces-c
>
>The current suggested repository style is to have
>
> trunk/
> branches/
> tags/
> site/
>
>under the project directory. site/ would contain the website pages,
>while trunk is the current HEAD, branches have any other active
>branches, and tags all the historical tags.
>
><aside>
>Once the whole thing is in SVN we can adjust the layout *very*
>simply. Compared to CVS, SVN is truly a wonder when it comes to
>adjusting the repository layout. You can move and rename directories
>in zero time by using commands like "svn mv ..." and "svn cp ..."
>which operate directly on the repository (and of course everything is
>versioned in case you change your mind).
>
>This means the projects directory structure can be easily cleaned up
>as part of the autoconf cleanup for 3.0, without losing any project
>history.
>
>This also means that when Xerces becomes a TLP, the xml/xerces-c/
>directory can be renamed to xerces/xerces-c/ and then xerces/xerces-j/
>can be added. Eventually xml/xerces-p/ can be folded into xerces-c
>during the 3.0 migration.
><aside>
>
>So are people are comfortable with this?
>
>+1 from me.
>
>Cheers,
>jas.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
>For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by Gareth Reakes <ga...@parthenoncomputing.com>.
Xerces-J are in the middle of some devel at the moment so don't want to
move over yet. I said we would keep them informed of any problems.
Gareth
--
Gareth Reakes, Managing Director Parthenon Computing
+44-1865-811184 http://www.parthcomp.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
James Berry <jb...@apache.org> writes:
> As it sits, all of the xml projects are under asf/xml. So xerces-c wil
> become asf/xml/xerces-c up until whatever time (and if) they decide it
> needs to move. I'm not sure that it's particularly important that the
> repository structure match the political structure. All it means to us
> is that our code may, at some point, move within the larger repository
> structure, which will take only a small amount of effort to update.
svn mkdir https://svn.apache.org/repos/asf/xerces
svn mv https://svn.apache.org/repos/asf/xml/xerces-c \
https://svn.apache.org/repos/asf/xerces/xerces-c
svn mv https://svn.apache.org/repos/asf/xml/xerces-p \
https://svn.apache.org/repos/asf/xerces/xerces-p
svn rm https://svn.apache.org/repos/asf/xml
easy as pie ...
Cheers,
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by Gareth Reakes <ga...@parthenoncomputing.com>.
Hey,
James Berry wrote:
>
> On Feb 21, 2005, at 1:49 AM, Gareth Reakes wrote:
>
>> Hey,
>>
>>> has all the TLP's as top-level projects. Since Xerces-C is officially
>>> still part of XML and not it's own TLP (true??), we would go under
>>
>> True for not very long hopefully. The resolution is going in front of
>> the board this time round. Perhaps we should hold off until they have
>> made the decision?
>
>
> As it sits, all of the xml projects are under asf/xml. So xerces-c wil
> become asf/xml/xerces-c up until whatever time (and if) they decide it
> needs to move. I'm not sure that it's particularly important that the
> repository structure match the political structure. All it means to us
> is that our code may, at some point, move within the larger repository
> structure, which will take only a small amount of effort to update.
>
> I propose that we move ahead with our "move" without waiting for board
> action and subsequent changes to "trickle down" (that could take quite a
> bit of time).
I have no problem with that.
Gareth
--
Gareth Reakes, Managing Director Parthenon Computing
+44-1865-811184 http://www.parthcomp.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by James Berry <jb...@apache.org>.
On Feb 21, 2005, at 1:49 AM, Gareth Reakes wrote:
> Hey,
>> has all the TLP's as top-level projects. Since Xerces-C is officially
>> still part of XML and not it's own TLP (true??), we would go under
> True for not very long hopefully. The resolution is going in front of
> the board this time round. Perhaps we should hold off until they have
> made the decision?
As it sits, all of the xml projects are under asf/xml. So xerces-c wil
become asf/xml/xerces-c up until whatever time (and if) they decide it
needs to move. I'm not sure that it's particularly important that the
repository structure match the political structure. All it means to us
is that our code may, at some point, move within the larger repository
structure, which will take only a small amount of effort to update.
I propose that we move ahead with our "move" without waiting for board
action and subsequent changes to "trickle down" (that could take quite
a bit of time).
-jdb
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by Gareth Reakes <ga...@parthenoncomputing.com>.
Hey,
>
> has all the TLP's as top-level projects. Since Xerces-C is officially
> still part of XML and not it's own TLP (true??), we would go under
True for not very long hopefully. The resolution is going in front of
the board this time round. Perhaps we should hold off until they have
made the decision?
Gareth
--
Gareth Reakes, Managing Director Parthenon Computing
+44-1865-811184 http://www.parthcomp.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by "Jason E. Stewart" <ja...@openinformatics.com>.
James Berry <jb...@apache.org> writes:
> On Feb 20, 2005, at 2:17 AM, Jason E. Stewart wrote:
>
> Maybe we'd like to clean house and get rid of the _dxxxx and Beta tags
> for the 1.x line? That seems like ancient history. We might also do
> something like move create a tags/releases directory to hold the
> tagged releases. Thoughts?
I thought about proposing the same thing, but I decided against it for
two reasons: in svn tags are free (resource wise), so you can have as
many as you like without bogging anything down. And it's way more
trouble to spend time figuring out which tags to keep and which to
leave then it is to dump the whole CVS repos...
If we had some major CVS reorganization or ugly stuff we wanted to
dump, then it might matter, but as James pointed out, we're pretty
clean.
Cheers,
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by Gareth Reakes <ga...@parthenoncomputing.com>.
Hey,
James Berry wrote:
>
> On Feb 20, 2005, at 2:17 AM, Jason E. Stewart wrote:
>
>> Hey All,
>> Email #2 in my series...
>> The current ASF repos at:
>> https://svn.apache.org/repos/asf/
>> has all the TLP's as top-level projects. Since Xerces-C is officially
>> still part of XML and not it's own TLP (true??), we would go under
>
>
> Gareth, can you confirm status on this issue?
>
To confirm. The resolution is going in front of the board shortly.
>
> Maybe we'd like to clean house and get rid of the _dxxxx and Beta tags
> for the 1.x line? That seems like ancient history. We might also do
> something like move create a tags/releases directory to hold the tagged
> releases. Thoughts?
I have no objection to 1.* going.
Gareth
--
Gareth Reakes, Managing Director Parthenon Computing
+44-1865-811184 http://www.parthcomp.com
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: [cvs => svn] new SVN repository structure
Posted by James Berry <jb...@apache.org>.
On Feb 20, 2005, at 2:17 AM, Jason E. Stewart wrote:
> Hey All,
> Email #2 in my series...
> The current ASF repos at:
> https://svn.apache.org/repos/asf/
> has all the TLP's as top-level projects. Since Xerces-C is officially
> still part of XML and not it's own TLP (true??), we would go under
Gareth, can you confirm status on this issue?
> https://svn.apache.org/repos/asf/xml/xerces-c
> The current suggested repository style is to have
> trunk/
> branches/
> tags/
> site/
> under the project directory. site/ would contain the website pages,
> while trunk is the current HEAD, branches have any other active
> branches, and tags all the historical tags.
This sounds good. And I'm not completely against keeping all of our
tags, as I don't think xerces-c has gone overboard in tagging/branching
in the past. svn is a little different from cvs, however, in that if
you check out the entire tree you'll get local copies in full of each
tagged copy--a good reason not to check out the whole tree.
Doing cvs log -l doc/index.html, I see the following tags:
Xerces-C_2_6_0: 1.2
Xerces-C_2_5_0: 1.2
Xerces-C_2_4_0: 1.2
Xerces-C_2_3_0: 1.2
Xerces-C_2_2_0: 1.2
Xerces-C_2_1_0: 1.2
Xerces-C_2_0_0: 1.2
Xerces-C_1_7_0: 1.2
Xerces-C_1_6_0: 1.2
Xerces-C_1_5_2: 1.2
Xerces-C_1_5_1: 1.2
Xerces-C_1_5_0: 1.2
Xerces-C_1_4_0: 1.2
xerces-c-1_3_0d04: 1.2
xerces-c-1_3_0d03: 1.2
Xerces-C_1_3_0_d02: 1.2
Xerces-C_1_2_0: 1.2
Xerces-C_1_1_0: 1.2
Xerces-C_1_1_0_d17: 1.2
Xerces-C_1_1_0_d016: 1.2
Xerces-C_1_1_0_d015: 1.2
Xerces-C_1_1_0_d014: 1.2
Xerces-C_1_1_0_d06: 1.2
Xerces-C_1_1_0Beta: 1.2
Xerces-C_1_1_0_d05: 1.2
Maybe we'd like to clean house and get rid of the _dxxxx and Beta tags
for the 1.x line? That seems like ancient history. We might also do
something like move create a tags/releases directory to hold the tagged
releases. Thoughts?
> This also means that when Xerces becomes a TLP, the xml/xerces-c/
> directory can be renamed to xerces/xerces-c/ and then xerces/xerces-j/
> can be added. Eventually xml/xerces-p/ can be folded into xerces-c
> during the 3.0 migration.
> <aside>
> So are people are comfortable with this?
Relatively so, though it'd be interesting to hear some more comment on
the above...
-jdb
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org