rel-html: one fix and update for project renames
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest8 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | rel_html: add support for project aliasesrel-html.py | +58 | 0 replies | |
| 2/8 | rel-html: rename compat-drivers.cfg to backports.cfgprojects/ projects/ | +37 | 0 replies | |
| 3/8 | rel-html: really listen to ignore_changelogsrel-html.py | +2 | 0 replies | |
| 4/8 | rel-html: add RFC3339 / short style next release types supportrel-html.py | +42 | 0 replies | |
| 5/8 | rel-html: fix next release URLsrel-html.py | +1 | 0 replies | |
| 6/8 | rel-html: add v3.10 as supported for Linuxrel-html.cfg | +1 | 0 replies | |
| 7/8 | rel-html: update iw releaseprojects/ | +1 | 0 replies | |
| 8/8 | rel-html: update hostapd releasesprojects/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/8] rel-html: one fix and update for project renames
From: "Luis R. Rodriguez" <[email protected]>
rel-html [0] is used to generate the HTML5 release pages for the backports project but given the input received it was designed to support any project. The backports project was renamed and the release structure was updated as well. This series addresse the project rename and adds support for multiple daily snapshot releases styles. While at it update the other projects this supports making releases for and kick out new pages for them as examples [1].
Note the TODO from Readme.md:
* Figure out how to automatically determine releases from git.
- If we have many stable releases how should we annotate this via git ?
It seems that the way to go is to require a config file for the project with the oldest stable release supported and then annotate eols. We do this right now, so rel-html would just need to be modified to infer newer releases.
* The Linux kernel now (as of 2013-03-10) has json file for releases:
https://www.kernel.org/releases.json
We need to do a few things then:
- Get other projects to use json for releases
- Add json intepreter support to rel-html
If projects don't use json releases files as the Linux kernel does then the current usage of HTMLParser would allow us to parse / infer releases for us.
* See if we can copy the EOL release into an eol/ directory and moving forward instead of parsing the tags use the directory name to automatically determine other release attributes. This is only relevant for the Linux kernel right now.
[0] git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/rel-html.git
[1] http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/
Luis R. Rodriguez (8):
rel_html: add support for project aliases
rel-html: rename compat-drivers.cfg to backports.cfg
rel-html: really listen to ignore_changelogs
rel-html: add RFC3339 / short style next release types support
rel-html: fix next release URLs
rel-html: add v3.10 as supported for Linux
rel-html: update iw release
rel-html: update hostapd releases
projects/backports.cfg | 37 +++++++++++ projects/compat-drivers.cfg | 34 ---------- projects/hostapd.cfg | 1 + projects/iw.cfg | 1 + rel-html.cfg | 1 + rel-html.py | 149 +++++++++++++++++++++++++++---------------- 6 files changed, 134 insertions(+), 89 deletions(-) create mode 100644 projects/backports.cfg delete mode 100644 projects/compat-drivers.cfg
Signature · 1 line
1.7.10.4