Hi Raphael, I do understand and agree with your maintainability and upstream security support argumentation. But there's still some issues we'll have to address (see below).
On 07/23/2014 02:01 AM, Raphael Hertzog wrote: > So I don't really buy your argument Thomas. Have you just tried to run > it with Django 1.7? Well, that's my point! I haven't tried, just like upstream didn't try. And just "try" isn't the correct thing to do, you need a much deeper expertise in the upstream code to be able to tell if the app will work or not. I haven't asked (I will soon though), but I'm almost certain that upstream for OpenStack will reject any of my requests to add Django 1.7 support in Horizon for Icehouse: this is out of the scope of maintenance for a stable release, which is perfectly understandable. I don't think it is reasonable to expect upstream to work on this when the final version of Django 1.7 isn't even out, and when it is, upstream (for OpenStack at least) will be in feature freeze (at the end of August), and therefore, I don't think they will even accept compatibility patches, which is very reasonable. If I decide to upgrade to Juno before the freeze of Jessie (which, again, I don't wish to do at all because Icehouse will more or less be a LTS for OpenStack), then there's a bunch of new dependencies which I will have to deal with, including probably a big issue with Jquery. Horizon will need >=1.10, and currently we only have 1.7.2 in Jessie. That's also clearly out of scope just before the freeze of Jessie. So, whatever happen, I'll have to deal, alone, with the Django 1.7 compatibility in OpenStack Horizon. At this point, I do *not* have the time available to investigate this, and I don't think I will before the freeze of Jessie (due to a mix of personal issues...). I don't think I have the expertise to deal with it anyway (I don't know much about Django myself, and again, just "trying" isn't enough IMO). Now, if someone *else* than me work on checking: - horizon - python-django-bootstrap-form - tuskar-ui - python-django-openstack-auth - python-django-discover-runner - python-django-pyscss - python-django-compressor - python-django- app-conf ... then make sure that they will work correctly with Django 1.7, and all of this *before* the upload of Django 1.7 in Sid, then I'm ok with migrating to it. Until you find the needed workforce for this, then I don't think it is reasonable to upload Django 1.7. Anyway, I'll be raising the topic in the OpenStack dev list. Thanks a lot Raphael for taking the time to ask before the upload, this is very very much appreciated. Some other DDs didn't do this way, and the result was really bad. I'll do my best to at least *try* to make it possible to upgrade to Django 1.7 (even though, as you can tell, I'm not convinced yet, I'll at least try...). Thoughts and help welcome, Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
