Hello everyone,
I’m writing to start collecting release notes for Katello 4.19. If you think a contribution should be added to these notes please feel free to put them to this HackMD[0]. I made it writable only by signed in users, but only to discourage any sort of unwanted attention. Please let me know if you have any issues reaching or editing it.
Thanks!
Also note, it doesn’t just have to be a feature, this can also be an upgrade warning or a notice of deprecation!
Since I was not sure about the process for gathering release notes, I opened a draft PR, here: Add Katello 4.19 structured APT for deb content upgrade docs by quba42 · Pull Request #4452 · theforeman/foreman-documentation · GitHub
I will transfer this to the hackmd document (and also rework it, it is still pretty early draft state).
@Zhunting I went and added my stuff regarding the “structured APT migration for deb content”. I added it under “Headline features”, “Upgrade warnings”, as well as “Removals”. Since I am not in the habit of writing release notes for upstream Katello I would appreciate some feedback/a review/a second pair of eyes. 
How we normally work is that you submit a PR to foreman-documentation directly with your proposed change. We can do that during the entire release cycle. When we branch to the stable version we always clear nightly again to start the next release cycle. This gives us a proper way to review each individual note using the well established GitHub review process.
Care must be taken that when you do branch and haven’t merged all PRs that they’re reopened or changed to be against the correct branch.
In that case I will work on updating my foreman-documentation PR.