On Fri, 25 Nov 2016 11:49:54 -0800 (PST)
Tim Graham <timogra...@gmail.com> wrote:
> After doing releases about once a month for a while, I'm thinking it would
> be nice if releasing Django could be a bit more automated. As far as I
> know, the process hasn't changed too much in 10 years, while the state of
> Python packaging has improved.
>
> Currently doing a release requires bumping the VERSION tuple in
> django/__init__.py [0], creating tarball/wheel and checksum files, asking
> someone in IRC to verify the checks look fine, and upload files to various
> locations [1]. My idea would be to use setuptools_scm [2] (that choice
> because this is the only tool I know about) to eliminate the need to
> bump/set a VERSION tuple and instead fetch the version information based on
> git tags. Something like (based on what I found in djanog-hosts [3]):
>
> __version__ = pkg_resources.get_distribution('django').version
>
> One issue I'm not sure how to deal with is how to provides
> backwards-compatibility for django.VERSION, the tuple format that looks
> something like:
>
> VERSION = (1, 11, 0, 'alpha', 0)
>
> I think removing or deprecating it would be quite disruptive for the
> community as I've seen lots of third-party apps that do checks like "if
> django.VERSION < (1, 9): ...", for example. I suspect it's possible to
> parse the version string to create something similar, but I wondered if
> anyone has experience with that.
>
> Finally, uploading to PyPI and djangoproject.com (release and checksum
> files) could be done automatically by Jenkins or something similar.
>
> Thanks for your comments, concerns, and suggestions.
>
> [0]
> https://github.com/django/django/blob/6252fd6314f66d2d303cc47c791ffefd27169b42/django/__init__.py#L5
> [1]
> https://docs.djangoproject.com/en/dev/internals/howto-release-django/#actually-rolling-the-release
> [2] https://github.com/pypa/setuptools_scm
> [3]
> https://github.com/jazzband/django-hosts/blob/0eae77b31927ddb0267943d6f9bcfc22f14706f2/django_hosts/__init__.py#L11
>
Hi,
The process I use goes the other way around: with an automated tool, we type
``make release-minor`` and get:
1. Update the VERSION tuple
2. Update the ChangeLog with a release date
3. Create the adequate git tag
4. Prepare the ChangeLog for the next release
The tool we use is not open-source yet, however it seems very similar in design
to https://pypi.python.org/pypi/zest.releaser.
Moreover, this pattern does not change the way your package is installed or
detects its version number: that number is always available in the source code,
no matter how the package was installed.
--
Raphaël
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/20161125221633.3a5d1166%40anoth.
For more options, visit https://groups.google.com/d/optout.
