I agree with Michael. I think it would be a good idea to release 2.7.0 and then look at changing over to SVN.
I dont think there is any need to rush into this when we already have other things on the plate.
Its not as if CVS is giving us big problems to make switching critical at this very moment.
Thanks
Ankit Pasricha
XML Parser Development
IBM Toronto Lab
8200 Warden Avenue, Ontario L6G 1C7
Phone: (905) 413 4941
| Michael Glavassevich/Toronto/[EMAIL PROTECTED]
02/21/2005 12:18 PM
|
|
Hi Gareth,
Speaking for myself, I would prefer if we made the move to SVN during a
lull in development, where this is the only change that's going on. It's
going to cause considerably more churn to the community than the JIRA
migration we did last year. We're in the middle (though hopefully coming
to a close soon) of development of Xerces 2.7.0. I think the ideal time
for such a move is after the release when we're looking at what's next,
just as the Xerces-C community is doing right now with mapping out the
road for 3.0.
What do other people think?
Thanks.
Gareth Reakes <[EMAIL PROTECTED]> wrote on 02/21/2005 05:03:10
AM:
> Hey all,
>
> In Xerces-C we have discussed moving over to SVN and have decided
that
> we will do this as part of the move over to a 3.0 release. This will
> happen fairly soon. Given that Xerces is going to become a TLP very soon
> (resolution going in front of board shortly) we thought we should ask
> what your opinions are / whether you thought it would make sense to pull
> Xerces-J over and the same time as C and P.
>
> Cheers,
>
> Gareth
>
> --
> Gareth Reakes, Managing Director Parthenon Computing
> +44-1865-811184 http://www.parthcomp.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTED]
E-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
