From: Jonathan S. Katz Date: Mon, 5 Nov 2018 15:32:03 +0000 (-0500) Subject: Update help text for core.Version.eoldate in the migration file. X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=aec859f55a78642ad02215f5f675f9b83d3ba1b8;p=pgweb.git Update help text for core.Version.eoldate in the migration file. The change to the help text was introduced in 669b3782, which caused a Django migration warning, even though schema changes were introduced. This also shows the proper way for updating non-schema-altering field changes that are introduced into Django. --- diff --git a/pgweb/core/migrations/0001_initial.py b/pgweb/core/migrations/0001_initial.py index 44238103..65fb2bab 100644 --- a/pgweb/core/migrations/0001_initial.py +++ b/pgweb/core/migrations/0001_initial.py @@ -118,7 +118,7 @@ class Migration(migrations.Migration): ('testing', models.IntegerField(default=0, help_text=b'Testing level of this release. latestminor indicates beta/rc number', choices=[(0, b'Release'), (1, b'Release candidate'), (2, b'Beta'), (3, b'Alpha')])), ('docsloaded', models.DateTimeField(help_text=b'The timestamp of the latest docs load. Used to control indexing and info on developer docs.', null=True, blank=True)), ('firstreldate', models.DateField(help_text=b'The date of the .0 release in this tree')), - ('eoldate', models.DateField(help_text=b'The planned EOL date for this tree')), + ('eoldate', models.DateField(help_text=b'The final release date for this tree')), ], options={ 'ordering': ('-tree',),