Hi All,
Just coming back to this again (time flies), although we've got a while
until 4.0 is released so no rush here.
I've got a few different thoughts here:
*Data*
I had a look at the various tools discussed above to see if any give us
what we need. While on that journey I came accross git'
Hey David.
Thanks for the follow-up here.
I think at least for 4.0 we should focus on adding callouts/recognition to the
release blog post, rather than the release notes.
For one, release notes only contain new features, and we want to call out all
the different contributions that don’t fal
Related to this discussion, what's the current policy / practice around
linking to tickets from the release notes? It looks the release notes for
patch releases already link to tickets, e.g.
https://docs.djangoproject.com/en/dev/releases/3.2.6/
However, for feature release, it looks like the tic
I started including ticket numbers in patch releases because there aren't
too many changes there and every change has a release note. I think the
ticket numbers are useful to quickly identify the cause of some change or
regression in a patch release where upgrades should generally be safer and
Just to expand on my question a little bit with a comment, I think it would
help to make the ticket corresponding to a release note easier to find
because it would give people an easier way to answer the question, "what is
the reasoning / background / discussion for this change?" Currently, ther
