Hi Jason,
That's an interesting question. I'll try to suggest an equally interesting answer.
Notes:
(1) There is no particular sharing of code, etc, between xerces-j and xerces-c that I know of, so there would seem to be no particular reason they need to share the same repository. Can anybody think of a good reason that they should?
Options:
(1) Get into a potentially long, drawn out debate with Xerces-j about migrating the repositories.
(2) Migrate just xerces-c to svn, but leave the top-level directory structure similar to what it is now to accommodate a potential future with xerces-j in it.
(3) Migrate just xerces-c to svn, leaving no accommodation for xerces-j in the same repository. This simplifies the directory structure a bit.
While I'm most inclined against (1), I do think we should at least notify the xerces-j list and/or pmc members that we're discussing this option. I don't know how much list overlap there is; I know I'm not on the xerces-j list. Gareth, do you have any ideas on this?
My inclination would be to do either (2) or (3). While (2) has some appeal, I also feel like there's no particular reason for us to share a single repository, and that maybe we should just do (3).
Thoughts, anyone?
-jdb
On Feb 20, 2005, at 2:19 AM, Jason E. Stewart wrote:
Hey All, Should we be involving the Xerces-J team in this discussion, since we are scheduled to become one big happy TLP at some point? Just a thought... Cheers, jas. --------------------------------------------------------------------- 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]
