expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-09 23:28:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

Handbook/docum update

Browse Source
This commit is contained in:
Philip Sargent
2021-05-01 22:38:58 +01:00
parent da34579547
commit 1d88123040
3 changed files with 6 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
handbook/troggle/trogdjangup.html
View File

@@ -25,7 +25,7 @@
</tr>
<tr>
<td>3.2 LTS</td>
<td>due April 2021</td>
<td>April 2021</td>
<td>December 2021</td>
<td>April 2024</td>
</tr>
@@ -43,7 +43,7 @@
</tr>
<tr>
<td>2.2 LTS</td>
<td>2.2.19</td>
<td>2.2.20</td>
<td>December 2019</td>
<td>April 2022</td>
</tr>
@@ -84,7 +84,7 @@
python manage.py validate -v 3 --traceback<br />
django-admin check <br />
python manage.py test -v 3 --traceback</var>
<li>Use the <em>highest release number</em> when upgrading between minor-versions of django. <br />So we went from 1.8.19 to 1.9.13 to 1.10.8 to 1.11.29 to 2.0.13 to 2.1.15 and then 2.2.19 .
<li>Use the <em>highest release number</em> when upgrading between minor-versions of django. <br />So we went from 1.8.19 to 1.9.13 to 1.10.8 to 1.11.29 to 2.0.13 to 2.1.15 then 2.2.19 (.20 was not released then) and next we will go to 3.2.x .
<li>Use the django 'check' maintenance system at the most verbose setting at each release<br />
<var>troggle$ python manage.py check -v 3 --deploy</var><br>
<var>troggle$ python -Wall manage.py check</var><br>