On Tue, Sep 19, 2006 at 04:55:20PM +0200, Frank Steiner wrote:
Marcus Meissner wrote
The SLES cycle is not in my area ;)
Too bad :-) If you like, forward my mail to those, whose area it is. Maybe they would consider this idea in their release plans...
In general we plan to have 2 year cycles, but review them together with ISVs and partners.
So with 2 years, it will always be very very short to manage a common upgrade, if SLES and SuSE hosts...
The _life_ cycle of our Enterprise Products is 5 years regular maintenance, and 2 more years of extended maintenance. We just release new ones every 2 years. (as per current status) As for common upgrade, if you really want to track both, then yes.
Regarding SUSE Linux with the same codebase... If you find features lacking in SLES but which are in SUSE Linux we definitely want to hear about it, to improve upon our SLES package set.
Ehm, except the few gigabytes of software SuSE has more than SLES? :-) It's just that we run SuSE for our clients and some special servers who serve the diskless clients (by exporting themselves, so they must have the same OS like the clients). And it is nice to have a common code base for desktop clients and servers, so from time to time they can benefit from each other (like exchanging kernels, or having xv on the servers etc. :-))
In the end all necessary software should be covered by SLES+SLED+SDK. I think xv is not (as your example). I would suggest switching to some kind of solution where you export chrooted SUSE Linux versions ... Should not be that hard, right? Ciao, Marcus