On 31/10/2013 10:50, "Damian, Alexandru" <[email protected]> wrote:
>We can test various Django versions, but I see no value in investing a >lot of time to support running on multiple versions at the same time. > > >- Django versions are not generally backward compatible. This is because >a typical project isn't expected to have code that needs to run on >multiple versions, i.e. if you need to upgrade Django for new features or >bugfixes, you will upgrade all of your code. > Supporting multiple code paths in Toaster for different Django versions >is gonna lead to a maintenance nightmare. > > >- The previous point leads to the idea of upgrading through porting the >whole codebase to a single supported Django version, i.e. ditching >support for older Django versions. This raises the problem - which Django >version do we support, and why ? Currently > we selected 1.4.5 as it is well supported on an array of host >distributions, and it's easy to install. I think this is the criteria we >need to use in the future - when we upgrade Django, it should be to the >version used by default by most of our users. All sounds reasonable. Thanks! Belén > > >Cheers, > >Alex > > > >On Thu, Oct 31, 2013 at 10:32 AM, Barros Pena, Belen ><[email protected]> wrote: > >Toaster is currently compatible with Django 1.4.5. Django has released two >more versions: 1.4.9 and 1.5.5 (https://www.djangoproject.com/download/), >and has a 1.6 RC too. > >This might not be important, but I am wondering if compatibility with any >of these newer versions of Django is something we should consider for 1.6. > >Belén > >_______________________________________________ >toaster mailing list >[email protected] >https://lists.yoctoproject.org/listinfo/toaster > > > > > > >-- >Alex Damian >Yocto Project > >SSG / OTC > > _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
