On Mon, Oct 10, 2011 at 10:29 AM, Jörgen Maas <[email protected]> wrote: > On Fri, Oct 7, 2011 at 1:56 PM, James Cammarata <[email protected]> wrote: >> Cobbler 2.2 has been tagged and released, with RPMS built and >> available in EPEL-testing now. This release incorporates a ton of new >> features: >> > > This is really nice, thanks! > > Is anyone willing to document the current stable release version on > the main page of the wiki? > And what about 2.0.x, will there be any bugfix releases or is it > unmaintained as of now? > I think some clarification would be very useful for users.
Standard practice is 2.0.x will receive bugfixes and security updates only - no new features, and 1.6.x should only get critical security patches now. We really need to organize the branches better, which is something I'd like to focus on next. Not sure if many people have seen this, but I think it's a great model, and one I'd like to look at adopting for cobbler: http://nvie.com/posts/a-successful-git-branching-model/ The major change here is that origin/master would be the stable branch, instead of dev like it is now. We'd create a new branch called devel which (following our even/odd model) would be 2.3.x. We already create release branches, so that wouldn't change (I've created release22 locally on my machine already). Just a thought, if people hate it we don't have to do it, I just thought it might make keeping track of things easier. _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
