Conversation
The /releases page lists the Release announcements from WildFly (based on the tags "release announcement") to provide a one-page destination for all WildFly releases. This fixes wildfly#611 Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>
|
Live example is available at http://jmesnil.github.io/wildfly.org/ Release Announcements page is linked at the top of the Project News page |
jmesnil
force-pushed
the
611_releases_page
branch
from
f93cedc to
f5689c7
Compare
Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>
jmesnil
force-pushed
the
611_releases_page
branch
from
f5689c7 to
0a87e07
Compare
|
@bstansberry I also added a link on the homepage to the latest release announcement based on the |
| {% endif %} | ||
| {% endfor %} | ||
|
|
||
| <h3>Now available: <a href="{{ releaseNoteLink }}"><span style="font-weight: 100;">Wild</span><strong>Fly</strong> {{latestRelease.version_shortname}}</a></h3> |
There was a problem hiding this comment.
With this I think we need a rule that the "Release Notes" data for future versions in release.yaml can never be a link to the oddly formatted JIRA releases notes. It must be to a blog post or to the GitHub release page.
I think such a rule is ok, but needs socialization as our requirements around this have been changing a bit in the last year and people coordinating releases may not be aware of things.
I added release process content related to this: https://docs.google.com/document/d/1Bjefo56-J_8PtPxTbHCiE-M3TeelHjxKppaJMmu6HSE/edit#bookmark=id.byujw232n9l
Yesterday I updated the content at https://docs.google.com/document/d/1Bjefo56-J_8PtPxTbHCiE-M3TeelHjxKppaJMmu6HSE/edit#bookmark=id.p51r3vc134gk to add a requirement for a release announcement news post. That was somewhat a trial balloon as I'd not discussed it. Your change here increases the need for such a requirement as having gaps in the list of announcements will be more noticeable and will look poor.
3 participants
The /releases page lists the Release announcements from WildFly (based on the tags "release announcement") to provide a one-page destination for all WildFly releases.
This fixes #611