nixos/doc/releases: update the docs as promised #86368
Conversation
ofborg
bot
added
6.topic: nixos
|
cc @cole-h |
ofborg
bot
added
10.rebuild-darwin: 0
| <para> | ||
| decide which bug fixes, features, etc… get backported after a release | ||
| </para> | ||
| </listitem> | ||
| </itemizedlist> | ||
| </section> | ||
| <section xml:id="release-schedule"> |
There was a problem hiding this comment.
Out of view from here, but maybe the release schedule should be updated or something, since it still refers to the nix-dev mailing list which, to the best of my knowledge, is dead? (Or at least under-used to the point of me not having used/read it in my 3 months here...)
There was a problem hiding this comment.
Sure, I probably should do this in this PR.
| </listitem> | ||
| <listitem> | ||
| <para> | ||
| <link xlink:href="https://github.com/NixOS/nixos-homepage/blob/a5626c71c03a2dd69086564e56f1a230a2bb177a/logo/nixos-logo-19.09-loris-lores.png">Add a compressed version of the NixOS logo for 19.09</link>. |
There was a problem hiding this comment.
IIRC, this was just some convert magic -- could this be documented? (I don't know who actually does this, but I imagine you do.)
There was a problem hiding this comment.
I think I just used gimp. but we probably want convert command for this.
I hope soon to start conversation in marketing team about next release process and where we can help out. I think writing announcement and handling artwork could be done by marketing and then reviewed / signed off by release manager.
This goes through a recent example of 19.09 (because the workflow should be everchanging, so our example needs to be recent). Lots of changes, just read idk.
worldofpeace
force-pushed
the
update-rm-docs
branch
from
4484f8f to
4ea275d
Compare
|
I just need to fix #86368 (comment), but by what time it is currently I don't think I have the required synapses firing in order to format proper docbook. |
|
FTFY, along with code blocks being outside of the list items and lists being broken. Also changed the chapter 4 reference to |
| Discuss with Eelco Dolstra and the community (via IRC, ML) about what | ||
| will reach the deadline. Any issue or Pull Request targeting the release | ||
| should be included in the release milestone. | ||
| Discuss with Eelco Dolstra and the community (via IRC, ML) about what will reach the deadline. Any issue or Pull Request targeting the release should be included in the release milestone. |
There was a problem hiding this comment.
via IRC, ML
We no longer use mailing list. Currently it is being discussed on an issue #95475
There was a problem hiding this comment.
Thx, I think in a followup I'm going to change this.
|
omg @jtojnar thank u. That totally saveeed me. |
|
Yesterday, I also packaged XMLmind XML Editor #95593 which should help you edit existing DocBook documents without having to wrangle the elements manually. |
Ooohh cooool |
|
Going to try it out |
There was a problem hiding this comment.
I was able to build the manual with these changes.
I'll iterate on them in a new PR.
Thanks @worldofpeace :)
This goes through a recent example of 19.09 (because the workflow
should be everchanging, so our example needs to be recent).
Lots of changes, just read idk.
Motivation for this change
Ok, so don't judge me but I converted
releases.xmlto markdown withpandoc, edited it, then usedpandocto convert it back, edited it. (and then some xmlformat).Probably not perfect, but the manual builds.
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)