It is true that users who just want a working binary download
have the M1 release to work with. However, the Tuscany community
itself will benefit from being able to run end to end scenarios
to exercise code that they contribute to the new trunk. So if we
do make this switch now, I believe that we need to focus as a
community on getting the new trunk into a state where it can run
end to end scenarios with comparable functionality to what we had
previously in M1. I'd feel more comfortable if I saw comments on
this list agreeing that this should be the priority immediately
following the switch.
Simon
Rick wrote:
For me the vote said it all; its good to go to switch. I think I can
understand your position and probably would side with you if it wasn't
for two things: We have a release so users just wanting to understand
SCA and the basics of Tuscany have something stable to work with. Also
this is just a switch, the head of the trunk should be preserved in a
branch. Just before the switch I would recommend both have tags too.
Doing this doesn't stop any discussion, it doesn't stop bringing
function/code from the current head back in to Chianti; it even doesn't
prevent in the case community decides we prefer to switch back.
Simon Nash wrote:
Jeremy,
Before you do this, I'd prefer to see some discussion about the
functional differences between chianti and the current trunk code
and how we would see these being addressed, as I said in my
previous email on this subject. What do you (or others) think
about this?
Simon
Jeremy Boynes wrote:
With the vote in favour of switching, I am about to start moving
chianti into trunk. I will move the current sca parts into a branch
(branches/pre-chianti) and move the chianti code into trunk. I will
make the version in the poms 1.0-SNAPSHOT like the SDO tree.
I expect to complete this tomorrow or possibly Wed if there are
build issues. If anyone has a bunch of uncommitted changes or a big
patch for submission please speak up soon to avoid merge issues.
Thanks
--
Jeremy
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
