But yes, doing a proper branch for 3.0 maintanence is what we want to do
for the real release.
/max
> I'd like to propose that after the 3.0 release, we branch to
a
> 3.0_maintenance and use that for 3.0.1. This will leave TRUNK open
> for further development and new features. I realize this is not how
> we've done it in the past. In the past we'd branch to 3.0.0 a few
> days before release, and then future work would go into TRUNK for
> 3.0.1. But I think this is the proper way to do things.
That is exactly how we did it for JBoss Tools 2 GA as far as I
remember. If we didn't it was because of same issues as we have had a
couple of times that things were breaking too much to do a spin off.
We didn't do it for JBT 3 yet because they have all been milestones.
> I don't have many "bug fixes" for the 3.0.1 release. In fact, after
> scanning my list, almost all are new features, not bugs. I clearly
> see me implementing new features as something that should go in TRUNK
> and not something I should have to branch my own project for.
Why did you mark them for 3.0.1 then ? They should be changed to 3.1.
/max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev