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 44238103fca6c97695574d0890b02225aee118e4..65fb2bab2275e6e3b85f85f203dd41d5a0c4d384 100644 (file)
--- 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',),