Hey all,
We've just released Cobbler version 2.6.8, another minor update in the stable 2.6 branch. This is probably the last release in the 2.6 series.
Please checkout the following resources:
Release notes: http://www.cobblerd.org/manuals/2.6.0/1/1_-_Release_Notes.html Downloads: http://www.cobblerd.org/downloads/2.6.x.html
On 06.05.2015 [22:02:27 +0200], J?rgen Maas wrote:
Hey all,
We've just released Cobbler version 2.6.8, another minor update in the stable 2.6 branch. This is probably the last release in the 2.6 series.
Please checkout the following resources:
Release notes: http://www.cobblerd.org/manuals/2.6.0/1/1_-_Release_Notes.html Downloads: http://www.cobblerd.org/downloads/2.6.x.html
So I noticed today that origin/release28 has been updated significantly since release (last update was May 29). But origin/master has not been updated since. Did the wrong branch by any chance get pushed to?
Also, it seems like the cobbler-web repository, which claims to be a work in progress/broken since it was forked off, has not had any updates since then. Does it work?
I follow upstream directly on my server by rebasing our local changes onto it and the fork and the state of origin/master mean I can't really right now.
-Nish
On 06/02/2015 07:59 PM, Nishanth Aravamudan wrote:
Also, it seems like the cobbler-web repository, which claims to be a work in progress/broken since it was forked off, has not had any updates since then. Does it work?
I and Jorgen agreed on undoing this repository split. Discussion: https://github.com/cobbler/cobbler/pull/1428 . He will probably do it soon and I hope he will keep the rpm/deb packages split.
Jorgen can answer your other questions better than me.
Regards, Alan Evangelista
@Nishanth: 28 is based of the 26 branch (weird, i know). Because a lot of stuff got removed from master already (eg. sql backends) i wanted another major release where we can properly document and deprecate all things that were sent to valhalla in master. So our users can better prepare for the upcoming changes in 3.0. Also, 28 will be some kind of LTS version for users that can not upgrade to 3.0 because of the missing features. And 3.0 will probably not be entirely compatible (api) with previous versions.
@Nishanth: are your local changes not suitable for upstream? would your life be easier if you'd have commit rights?
wrt master: the split (cobbler-web, koan) will be reversed when i find the time, i don't mind if someone else beats me to it though ;-)
On Wed, Jun 3, 2015 at 3:01 AM, Alan Evangelista alanoe@linux.vnet.ibm.com wrote:
On 06/02/2015 07:59 PM, Nishanth Aravamudan wrote:
Also, it seems like the cobbler-web repository, which claims to be a work in progress/broken since it was forked off, has not had any updates since then. Does it work?
I and Jorgen agreed on undoing this repository split. Discussion: https://github.com/cobbler/cobbler/pull/1428 . He will probably do it soon and I hope he will keep the rpm/deb packages split.
Jorgen can answer your other questions better than me.
Regards, Alan Evangelista
cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler-devel
Jorgen,
On 03.06.2015 [07:27:00 +0200], J?rgen Maas wrote:
@Nishanth: 28 is based of the 26 branch (weird, i know). Because a lot of stuff got removed from master already (eg. sql backends) i wanted another major release where we can properly document and deprecate all things that were sent to valhalla in master. So our users can better prepare for the upcoming changes in 3.0. Also, 28 will be some kind of LTS version for users that can not upgrade to 3.0 because of the missing features. And 3.0 will probably not be entirely compatible (api) with previous versions.
Ah that make sense actually. I just wasnt sure why master hadn't been updated in so long. But it follows that master28 needed further updates.
@Nishanth: are your local changes not suitable for upstream? would your life be easier if you'd have commit rights?
Well, my intent for rebasing is to send everything I can upstream :)
I feel bad asking for commit rights -- I think I'm ok just being a contributor, as I don't know want to inadvertently break the code base.
wrt master: the split (cobbler-web, koan) will be reversed when i find the time, i don't mind if someone else beats me to it though ;-)
If it would help to revert the commits, I can contribute to this -- not sure how clean the revert will be immediately, but I will look.
-Nish
On 03.06.2015 [08:51:32 -0700], Nishanth Aravamudan wrote:
Jorgen,
On 03.06.2015 [07:27:00 +0200], J?rgen Maas wrote:
@Nishanth: 28 is based of the 26 branch (weird, i know). Because a lot of stuff got removed from master already (eg. sql backends) i wanted another major release where we can properly document and deprecate all things that were sent to valhalla in master. So our users can better prepare for the upcoming changes in 3.0. Also, 28 will be some kind of LTS version for users that can not upgrade to 3.0 because of the missing features. And 3.0 will probably not be entirely compatible (api) with previous versions.
Ah that make sense actually. I just wasnt sure why master hadn't been updated in so long. But it follows that master28 needed further updates.
@Nishanth: are your local changes not suitable for upstream? would your life be easier if you'd have commit rights?
Well, my intent for rebasing is to send everything I can upstream :)
I feel bad asking for commit rights -- I think I'm ok just being a contributor, as I don't know want to inadvertently break the code base.
wrt master: the split (cobbler-web, koan) will be reversed when i find the time, i don't mind if someone else beats me to it though ;-)
If it would help to revert the commits, I can contribute to this -- not sure how clean the revert will be immediately, but I will look.
PR sent: https://github.com/cobbler/cobbler/pull/1481
-Nish
cobbler-devel@lists.fedorahosted.org