summaryrefslogtreecommitdiff
path: root/docs/RELEASE.md
Commit message (Collapse)AuthorAgeFilesLines
* docs: update instructions for translation stringsLuca Boccassi2023-01-241-1/+1
|
* docs: drop manual rc PR warning stepLuca Boccassi2023-01-241-13/+11
| | | | it is not automated, yay
* docs: update translation strings before new releaseFrantisek Sumsal2022-10-201-9/+10
|
* docs: add disabled PR template for code freezeLuca Boccassi2022-08-041-10/+12
| | | | | | To be enabled on rc1, and disabled again after the final release. Gives contributors a clear warning that new features/APIs will be postponed.
* docs/RELEASE: typo in target nameZbigniew Jędrzejewski-Szmek2022-05-051-1/+1
|
* docs/RELEASE: also mention syscall tablesZbigniew Jędrzejewski-Szmek2022-04-121-12/+13
|
* docs: stop recommending meson compileZbigniew Jędrzejewski-Szmek2022-04-121-5/+5
| | | | | | | | | | | | | | | | | | With meson-0.60, meson compile stopped working with some targets: $ meson compile -C build update-man-rules ERROR: Can't invoke target `update-man-rules`: ambiguous name. Add target type and/or path: `PATH/NAME:TYPE` This is obviously a regression in meson, but based on a chat with the maintainers, it seems that there's some disagreement as to whether 'meson compile' is useful and how exactly it should work. Since we're already at meson 0.60.3 and this hasn't been fixed, and people generally don't seem to consider this an issue, let's return to documenting the usual practice of 'ninja -C build' that just works everywhere. (Since nobody has raised any fuss in systemd, it means that people are generally using the shorter form during development too. I only noticed because I pasted a command from the release docs when preparing -rc1.)
* docs: update branch namesZbigniew Jędrzejewski-Szmek2022-01-031-1/+1
| | | | | Also use --atomic when pushing multiple items with git; adjust some external URLs.
* doc: fix typoYu Watanabe2021-12-091-1/+1
|
* docs: add spdx tags to all .md filesZbigniew Jędrzejewski-Szmek2021-09-271-0/+1
| | | | | | I have no idea if this is going to cause rendering problems, and it is fairly hard to check. So let's just merge this, and if it github markdown processor doesn't like it, revert.
* doc/RELEASE.md: document hwdb update stepLuca Boccassi2021-03-171-11/+12
|
* meson: rename target to update-dbus-docsZbigniew Jędrzejewski-Szmek2021-01-271-1/+1
| | | | | | | | | Very old versions of meson did not include the subdirectory name in the target name, so we started adding various "top-level" custom targets in subdirectories. This was nice because the main meson.build file wasn't as cluttered. But then meson started including the subdir name in the target name. So let's move the definition to the root so we can have all targets named uniformly.
* tree-wide: suggest meson command lines instead of ninja onesLennart Poettering2020-12-171-4/+4
| | | | | | | This only changes documentation. In various places we call "ninja" directly. I figured it would be safer to leave those in place for now, given the meson replacement commands lines appears to be supported in newer meson versions only.
* docs/RELEASE: clarify which steps are done whenZbigniew Jędrzejewski-Szmek2020-11-261-3/+3
|
* docs: add man/update-dbus-docs step to release instructionsZbigniew Jędrzejewski-Szmek2020-08-221-9/+10
|
* docs: make it prettyTobias Bernard2019-12-111-0/+1
| | | | | | | Add custom Jekyll theme, logo, webfont and .gitignore FIXME: the markdown files have some H1 headers which need to be replaced with H2
* docs: place all our markdown docs in rough categoriesLennart Poettering2019-12-111-0/+1
|
* docs: fix push recipe in RELEASE.mdZbigniew Jędrzejewski-Szmek2019-09-051-1/+1
|
* docs: also document updates to stable repoZbigniew Jędrzejewski-Szmek2019-04-031-0/+1
|
* docs: let's not close the milestone earlyZbigniew Jędrzejewski-Szmek2019-04-031-1/+1
|
* docs: update release steps for mesonZbigniew Jędrzejewski-Szmek2019-04-031-8/+10
|
* docs: add a "front matter" snippet to our markdown pagesFilipe Brandenburger2019-01-021-0/+4
| | | | | | | | | | | | | | | | It turns out Jekyll (the engine behind GitHub Pages) requires that pages include a "Front Matter" snippet of YAML at the top for proper rendering. Omitting it will still render the pages, but including it opens up new possibilities, such as using a {% for %} loop to generate index.md instead of requiring a separate script. I'm hoping this will also fix the issue with some of the pages (notably CODE_OF_CONDUCT.html) not being available under systemd.io Tested locally by rendering the website with Jekyll. Before this change, the *.md files were kept unchanged (so not sure how that even works?!), after this commit, proper *.html files were generated from it.
* docs: uppercase the title of our Markdown docsLennart Poettering2018-11-291-1/+1
|
* docs: move markdown docs from .github/ to docs/Filipe Brandenburger2018-09-081-0/+12
The GitHub guide on contributing file says: "Decide whether to store your contributing guidelines in your repository's root, docs, or .github directory." https://help.github.com/articles/setting-guidelines-for-repository-contributors/#adding-a-contributing-file But there's really no advantage to keeping it in the hidden .github/, since these are public and really belong together with the other documentation. We can still keep the issue templates under .github/, since they are not really documentation on their own. Updated the links pointing to CONTRIBUTING.md to refer to the one in docs/.
View Lorry Controller Status