From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: [layerindex-web][PATCH 00/16] Django 1.11 upgrade (cover letter only)
Date: Mon, 23 Apr 2018 15:03:13 +1200 [thread overview]
Message-ID: <cover.1524452299.git.paul.eggleton@linux.intel.com> (raw)
Django 1.8 has gone out of support upstream, so here are the necessary
changes to upgrade to Django 1.11.x (the next LTS release). Along the
way I switched the Bulk Change feature to use OE's code for patching
recipes, since that part was broken by the upgrade (and possibly
broken otherwise).
I've posted the cover letter only to avoid too much noise for folks
that aren't interested - see the branch for details.
The following changes since commit 611c96883c35240d3c291951146154d828745774:
requirements.txt: use the most recent Django 1.8 version (2018-03-26 08:29:27 +1300)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/django-upgrade
http://git.yoctoproject.org/cgit.cgi//log/?h=paule/django-upgrade
Paul Eggleton (16):
views: replace mimetype with content_type
settings.py: switch to django.template.context_processors
Make manage.py executable and tidy shebang
Use new TEMPLATES setting
Replace usage of model._meta.get_all_field_names()
Stop using string name for publish view in urls.py
urls*: Use new urlpatterns list syntax
templatetags/addurlparameter: remove unused reference
templates: replace use of = with ==
views: fix history tracking to work with current django-reversion
urls: add required exception parameter for page_not_found
views: Adapt to template rendering API change
utils: add function to add meta/lib/oe to sys.path
bulkchange.py: fix regression
bulkchange.py: use oe.recipeutils code to patch recipes
requirements.txt: bump Django and other dependency versions
README | 4 +-
layerindex/admin.py | 12 +--
layerindex/bulkchange.py | 134 ++---------------------------
layerindex/querysethelper.py | 2 +-
layerindex/recipeparse.py | 14 ---
layerindex/templatetags/addurlparameter.py | 2 +-
layerindex/urls.py | 10 +--
layerindex/urls_branch.py | 4 +-
layerindex/utils.py | 12 +++
layerindex/views.py | 92 +++++++++++---------
manage.py | 4 +-
requirements.txt | 16 ++--
settings.py | 42 ++++-----
templates/base_toplevel.html | 4 +-
templates/layerindex/detail.html | 6 +-
templates/layerindex/duplicates.html | 4 +-
templates/layerindex/editlayer.html | 8 +-
templates/layerindex/history.html | 8 +-
templates/layerindex/reviewdetail.html | 6 +-
urls.py | 7 +-
20 files changed, 139 insertions(+), 252 deletions(-)
mode change 100644 => 100755 manage.py
--
2.14.3
reply other threads:[~2018-04-23 3:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1524452299.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.