> 2. Submitting fixes to the vxl 1.0 -beta2 branch (and the main trunk)
For bug fixes, those should indeed be committed to the beta2 branch as well.
> 3. Just going to release vxl 1.0 from the main trunk in the near future with
> untested new features?
This rather than 1., but not with *untested* new features!
There should be a release shortly after the vxl meeting, incorporating any
decisions taken there, with the following procedure:
= creation of a CVS branch tag;
= thorough testing and bug fixing inside the branch;