diff options
| author | Erik Faye-Lund <[email protected]> | 2019-06-03 18:30:23 +0200 |
|---|---|---|
| committer | Erik Faye-Lund <[email protected]> | 2019-06-05 23:48:45 +0200 |
| commit | 8620f53212df1a96f5ae1d180dacb28418bf6cc8 (patch) | |
| tree | c09844b604cccb8eb72088ec532a550403f6490a /docs/release-calendar.html | |
| parent | d5e273aad24ae28b53422599d17177714aabf3e7 (diff) | |
docs: do not use br-tag for non-significant breaks
According to the W3C, we shouldn't use the br-tag unless the line-break
is part of the content:
https://www.w3.org/TR/2011/WD-html5-author-20110809/the-br-element.html
All of these instances are for non-content usage, and is as such technically
out-of-spec. So let's either remove them, or split paragraphs, based on
how related the content are.
Signed-off-by: Erik Faye-Lund <[email protected]>
Reviewed-by: Emil Velikov <[email protected]>
Reviewed-by: Eric Engestrom <[email protected]>
Diffstat (limited to 'docs/release-calendar.html')
| -rw-r--r-- | docs/release-calendar.html | 31 |
1 files changed, 20 insertions, 11 deletions
diff --git a/docs/release-calendar.html b/docs/release-calendar.html index e356af7fe48..70ed0112576 100644 --- a/docs/release-calendar.html +++ b/docs/release-calendar.html @@ -21,20 +21,29 @@ <p> Mesa provides feature/development and stable releases. </p> + <p> The table below lists the date and release manager that is expected to do the specific release. -<br> -Regular updates will ensure that the schedule for the current and the -next two feature releases are shown in the table. -<br> -In order to keep the whole releasing team up to date with the tools -used, best practices and other details, the member in charge of the -next feature release will be in constant rotation. -<br> -The way the release schedule works is -explained <a href="releasing.html#schedule" target="_parent">here</a>. -<br> +</p> + +<p> +Regular updates will ensure that the schedule for the current and the next two +feature releases are shown in the table. +</p> + +<p> +In order to keep the whole releasing team up to date with the tools used, best +practices and other details, the member in charge of the next feature release +will be in constant rotation. +</p> + +<p> +The way the release schedule works is explained +<a href="releasing.html#schedule" target="_parent">here</a>. +</p +> +<p> Take a look <a href="submittingpatches.html#criteria" target="_parent">here</a> if you'd like to nominate a patch in the next stable release. </p> |