"Release Info" Documentation

[maxandersen]

Description

As a stakeholder in Almighty I want to be able to see what is new and noteworthy on the site.

Functional Acceptance Criteria

• There is a "News" link on the system that shows a changelog for the current version.
• The UX needs to be implemented for the wireframe class.
• The content of the changelog can also be retrieved by a static, permanent link in adoc format.

Non-functional Acceptance Criteria

• The "News" link is easily reachable from everywhere in the application.

Note: the direkt link is the source for or the actual release notes for Red Hat Documentation.

Note: idea: initially just do for core and UI via a sha1 link, but need to find approach for overall docs too.

[aslakknutsen]

A Quick fix here could be:

Executing GitHub search query:

is:closed is:issue user:almighty label:userstory closed:<2016-10-26 

Where closed date is based on Core build date.

https://github.com/issues?utf8=%E2%9C%93&q=is%3Aclosed+is%3Aissue+user%3Aalmighty++label%3Auserstory+closed%3A%3C2016-10-26+

[sbose78]

Just a thought, the content which appears here should get reviewed by marketing/product team.
That will ensure that we don't include too many low level details.

There should be a process in place for this.