-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matt Hogstrom wrote, On 1/6/2006 7:07 AM: > I'll summarize what I think I read. > > HEAD will be 2.0 which includes JEE 5 and other significant work (Maven > 2 conversion, etc.) > > Branches/1.0 will be where the work for 1.0.x will take place. It would > be from this code base we'd branch to a 1.1 when appropriate.
So, we would eventually have 2 branches and 1 trunk: branches/1.0 branches/1_trunk tags/* trunk > I'm updating my local copy of the branches/1.0 with a version change for > Geronimo to 1.0.1-SNAPSHOT as well as updating to Tomcay 5.1.15 and > Jetty 5.1.10 to incoroporate the latent fixes. > > I'll build and test to make sure its still working (I'm not going to run > TCK). and then commit these changes back when I've confirmed we're ready > to go for 1.0.1. Does this sound workable? Can we have jira issues assigned to 1.0.1 so that we can see what's coming down the pipeline? Regards, Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDvqSa1xC6qnMLUpYRArhpAJ91d5cSrHGEsY0pG6Jf+Nb+9gNuSgCfR8gH m3qYJWEG9Zej/Sg+O5pMPQA= =goh1 -----END PGP SIGNATURE-----
