maas-devel team mailing list archive

[Mike Pontillo <mike.pontillo@xxxxxxxxxxxxx>]

On Thu, Sep 17, 2015 at 11:28 AM, Mark Shuttleworth <mark@xxxxxxxxxx> wrote:
>
> We will want to SRU newer versions of MAAS, is 1.8 going to be a great
> base for a good 18 months? If you're comfortable with that, +1
>

On Thu, Sep 17, 2015 at 1:46 PM, Gavin Panella <gavin.panella@xxxxxxxxxxxxx>
wrote:

> We've based MAAS on Django 1.6 on Trusty through to Wily and it has
> worked fine, though we have needed a distinct python-django16 package
> since Vivid. We can take a similar approach with Django 1.8 in the next
> LTS, with the advantage that 1.8 will be supported upstream until the
> 2018 Ubuntu LTS.
>

   Note that changing the version of Django means that MAAS on 15.10 and
earlier will likely need to be "frozen" in terms of both versions we can
support, and database schema. (unless we want to spend considerable
resources supporting both Django 1.6 and 1.8 -  keeping database
migrations, and any other idiosyncrasies we discover, in sync.) Therefore,
the following constraints should apply:

 - MAAS 1.9 will be the last release of MAAS that can be supported on 14.04
through 15.10, and will remain on Django 1.6. (MAAS 1.9 and earlier will
not run on any future Ubuntu release that does not contain the
python-django16 package; presumably, this includes 16.04, but I'm not
certain.)

 - MAAS-next (1.10? 2.0?) can be used on 16.04 and later, will be based on
Django 1.8, and must not be issued as a SRU to 15.10 or earlier (unless
Django 1.8 is issued as a SRU as well).

   Is everyone okay with the above?

Regards,
Mike