All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Orling" <ticotimo@gmail.com>
To: yocto@lists.yoctoproject.org
Cc: mhalstead@linuxfoundation.org, Tim Orling <timothy.t.orling@intel.com>
Subject: [layerindex-web][PATCH 15/15] README.devel: update versions
Date: Sun, 18 Jul 2021 16:07:20 -0700	[thread overview]
Message-ID: <4af5048d559c2b4c241a903f18a5761a5bdf25bf.1626647881.git.timothy.t.orling@intel.com> (raw)
In-Reply-To: <cover.1626647881.git.timothy.t.orling@intel.com>

This updated code-base should be compatible with
Django 3.1 and obviously 3.2 (but not 3.0 or earlier).

Django 3.2 requires Python 3.6+.

With the upgrade to Celery 5, it is safer to recommend
RabbitMQ 3.8.x, since that is what we are using.

Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
---
 README.devel | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.devel b/README.devel
index b535304..cbf54bf 100644
--- a/README.devel
+++ b/README.devel
@@ -7,9 +7,9 @@ covered in the main README.
 
 In order to run this application standalone, you will need:
 
-* Python 3.4+
-* Django 1.11.x (not compatible with 2.0 or newer)
-* RabbitMQ 3.7.x
+* Python 3.6+
+* Django 3.2.x (not compatible with 3.0 or older)
+* RabbitMQ 3.8.x
 * For production usage, a web server set up to host Django applications
   (not needed for local-only testing/development)
 * A database system supported by Django (SQLite, MariaDB/MySQL, etc.).
-- 
2.32.0


  parent reply	other threads:[~2021-07-18 23:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 23:07 [layerindex-web][PATCH 00/15] Upgrade to Django 3.2.5 LTS and Celery 5 Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 01/15] dockersetup.py: fix EMAIL_USE_SSL/TLS Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 02/15] requirements.txt: fix range check Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 03/15] Dockerfile: cleanup, install python3-wheel Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 04/15] dockersetup.py: letsencrypt 2048 bit rsa Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 05/15] layerindex/*: make all shebangs python3 Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 06/15] requirements.txt: bump to Django 3.0 Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 07/15] Updates for " Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 08/15] requirements.txt: bump to Django 3.1 Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 09/15] docker-compose: bump mariadb to 10.3 Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 10/15] requirements.txt: update all to latest Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 11/15] about.html: update contributors Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 12/15] requirements.txt: bump to Django 3.2 LTS Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 13/15] settings: set DEFAULT_AUTO_FIELD Tim Orling
2021-07-18 23:07 ` [layerindex-web][PATCH 14/15] docker-compose: fix celery Tim Orling
2021-07-18 23:07 ` Tim Orling [this message]
2021-07-20 18:01 ` [yocto] [layerindex-web][PATCH 00/15] Upgrade to Django 3.2.5 LTS and Celery 5 Richard Purdie

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=4af5048d559c2b4c241a903f18a5761a5bdf25bf.1626647881.git.timothy.t.orling@intel.com \
    --to=ticotimo@gmail.com \
    --cc=mhalstead@linuxfoundation.org \
    --cc=timothy.t.orling@intel.com \
    --cc=yocto@lists.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.