>Actually, I'd very much prefer if you'd take the snapshot
tonight. I have touched quite some files, so I'm not keen on
merging these into 2 source trees. What about taking the
snapshot tomorrow morning and create the new module
*tomorrow*?
OK. I've successfully tried the scripts I used so it should
be easy enough to run again tomorrow.
- "spring10" forces us to put Spring 1.1, 1.2, etc *each* in
a new module: too fine-granular IMO, branches are a way
better choice for such point releases.
- "spring1" just forces us to put Spring 2.0 into a new
module: much better IMO, using branches within the module for
1.1, 1.2, etc.
- "spring" would allow to use to stay with the module as long
as we want (including 2.0 or longer), as it would still allow
for a later "spring2" or "spring3" name if ever necessary:
admittedly debatable, but the way that Hibernate chose
("hibernate", then "hibernate2").
I think spring1 is probably best. But spring would be fine
also. Votes?
Regards,
Rod
|
