You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,15 +21,15 @@
21
21
22
22
* Added more validation of GMN settings
23
23
* Added migrations to generate Postgres indexes for default sorting
24
-
*Suprisingly, Django does not generate indexes for default sort ordering specified when using the ORM
24
+
*Surprisingly, Django does not generate indexes for default sort ordering specified when using the ORM
25
25
26
26
* Reconfigured logging to take advantage of Django's support for rotating logs, much like logrotate does. Maximum space to use for logging is now a config setting.
27
27
* Other usability improvements (see log)
28
28
29
29
* GMN deployment
30
30
31
31
* Improved and streamline GMN install procedures, including
32
-
* Refactored install so that it can be accomplished by in two stages, where only the first stage needs to be performed by account with sudo access
32
+
* Refactored install so that it can be accomplished in two stages, where only the first stage needs to be performed by account with sudo access
Building the release packages from a fresh clone is a simple way of ensuring that only tracked files are released. It is a workaround for the way setuptools works, which is basically that it vacuums up everything that looks like a Python script in anything that looks like a package, which makes it easy to publish local files by accident.
0 commit comments