Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #13000
| From | Jeremy Stanley <fungi@yuggoth.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: How to watch pypi.org |
| Date | 2020-11-01 21:10 +0100 |
| Message-ID | <B6rPP-2Pr-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <AWoqe-65e-9@gated-at.bofh.it> <B5Dq2-3F1-5@gated-at.bofh.it> <B5WVH-71D-3@gated-at.bofh.it> <B5Y1r-7F1-5@gated-at.bofh.it> <B6rd8-2cp-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On 2020-11-01 20:23:20 +0100 (+0100), Thomas Goirand wrote: [...] > However, if I am to put more efforts on stuff like that, my priority > would be first on getting the reno release notes published in the Debian > package. I've been thinking about this for a long time, and haven't > figured out yet what would be the best way, with a reasonable workflow. > > From the Debian perspective, I'd have to: > - generate the release notes from the last version in Debian Stable, up > to what's in Sid. For example, I would include all the OpenStack release > notes for Stein, Train, Ussuri and Victoria in all packages uploaded for > Debian Bullseye, as this would concern anyone upgrading from Buster. > - make it so that release notes would be generated from Git, and maybe > stored in a debian/release-notes folder, so that it wouldn't generate a > diff with the original upstream tag. > > The drawback would be that, on each upload of a new Debian revision, the > debian.tar.xz will contain the release notes, which could be of > significant size (especially if they include static objects like CSS, > JS, and all what makes a theme). > > If you have any other suggestion concerning how to handle these release > notes, please let me know. It's likely I'm missing some subtle reason for the complexities you outline above, but if you install python3-reno and then run `reno report` in the upstream Git repository for any project with a releasenotes tree (or pass the path to said Git repository in the command line) it will generate a reStructuredText compilation of the release notes contained therein. Very lightweight, no need for extra files or anything. I'd think you could just dump that output into a NEWS file or similar at binary package build time. This is basically the same thing reno's Sphinx extension does under the covers. Check out `reno report --help` for a number of flags you might want to pass it to make the results more readable like omitting the source filename comments, skipping notes earlier than a certain version, collapsing pre-release notes, and so on. A quick test of Nova's release notes indicates that even if you don't truncate them though and include everything back to when the project started using reno 5 years ago, that NEWS file would only increase the compressed size of the nova-doc package by 1%. -- Jeremy Stanley
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to watch pypi.org Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-04 17:30 +0200
Re: How to watch pypi.org Geert Stappers <stappers@stappers.nl> - 2020-10-04 17:50 +0200
Re: How to watch pypi.org Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-30 15:10 +0100
Re: How to watch pypi.org Andrey Rahmatullin <wrar@debian.org> - 2020-10-04 17:50 +0200
Re: How to watch pypi.org Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-30 15:10 +0100
Re: How to watch pypi.org Paul Wise <pabs@debian.org> - 2020-10-05 04:30 +0200
Re: How to watch pypi.org Scott Kitterman <debian@kitterman.com> - 2020-10-05 05:10 +0200
Re: How to watch pypi.org, example Geert Stappers <stappers@stappers.nl> - 2020-10-05 08:20 +0200
Re: How to watch pypi.org Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-30 15:20 +0100
Re: How to watch pypi.org Andrey Rahmatullin <wrar@debian.org> - 2020-10-30 15:30 +0100
Re: How to watch pypi.org Paul Wise <pabs@debian.org> - 2020-10-31 02:40 +0100
Re: How to watch pypi.org Jeremy Stanley <fungi@yuggoth.org> - 2020-10-31 03:40 +0100
Re: How to watch pypi.org Paul Wise <pabs@debian.org> - 2020-10-31 05:30 +0100
Re: How to watch pypi.org Thomas Goirand <zigo@debian.org> - 2020-10-31 12:10 +0100
Re: How to watch pypi.org Jeremy Stanley <fungi@yuggoth.org> - 2020-10-31 13:20 +0100
Re: How to watch pypi.org Thomas Goirand <zigo@debian.org> - 2020-11-01 20:30 +0100
Re: How to watch pypi.org Jeremy Stanley <fungi@yuggoth.org> - 2020-11-01 21:10 +0100
Re: How to watch pypi.org Andrey Rahmatullin <wrar@debian.org> - 2020-10-31 15:50 +0100
Re: How to watch pypi.org Jeremy Stanley <fungi@yuggoth.org> - 2020-10-31 18:40 +0100
csiph-web