On 2011-06-20 7:25, Jörgen Maas wrote:
On Mon, Jun 20, 2011 at 2:08 PM, James Cammarata<jimi(a)sngx.net>
wrote:
> As far as I know, there is no official policy on this. However, if
> it's an officially supported release (whether it's RHEL, ubuntu, etc.)
> we should support it. I believe we were still supporting RHEL3 for a
> while, though we can remove that now if there are hooks in the code to
> support it still.
Well, you just provided us with a policy...
Cobbler's original compatibility policy was to have all code support
RHEL 4 (with Python 2.3). Shortly after extended support for RHEL 2.1
was announced in 2009, the replace-self code path gained support for
Python as far back as version 1.5 so all systems managed by Satellite
Server could be upgraded in place.
The current code may or may not still reflect those goals. Either way,
Cobbler's code and compatibility goals can change. But given those bits
of history, dropping support for RHEL 4 on the server sounds reasonable.
The client-side code, however, should strive to remain compatible with
as many releases as possible for, at a minimum, its replace-self
functionality. Note that RHEL 3 (with Python 2.2) has 28 months of
extended support left.