changes.hood.ie (working title)

[gr2m]

As discussed with @boennemann, the idea is to create a script that we run once per week. It does the following:

1. Walk trough all Hoodie Core repositories and get all Release notes since last week
2. Write new changes grouped by module into a central changelog
3. Bump the Hoodie "Marketing" Version number.

The current Hoodie Marketing version number will start at Hoodie 1.0 Aplha-1. The script always bumps the -1 part, no matter how small or big the changes have been. The Hoodie 1.0 Aplha- part is hard coded and can be changed manually as we see fit.

Subtasks:

• [ ] create static page as input on what the outcome should look like
• [ ] agree on name / url
• [ ] build it

[lenareinhard]

lgtm. for the title: I'd suggest "status.hood.ie" (so people see the current version + changes made until then). Will also add this to the website relaunch.

[gr2m]

I've put together a quick draft on how it could look like http://gr2m.github.io/status.hood.ie/. Just at brain fart status right now, I'll think more about it

[gr2m]

I like how Firefox' end user release notes https://www.mozilla.org/en-US/firefox/30.0/releasenotes/

[tordans]

Hi @gr2m, two suggestions: a. I really like the though by http://keepachangelog.com/. Meaning: Are your sure that an auto generated changelog will be helpfull for users? b. IMO there is an established pattern for status.* domains which show downtime/uptime information. E.g. https://status.github.com/, http://status.twitter.com/, … – Meaning: Maybe use some other domain to have status.* free for later.

[gr2m]

Thanks for your input @tordans. For the chanelogs in the actual repositories, we follow angular's styleguides paired with grunt-conventional-changelog and some amazing sugar on top of it, listed in https://github.com/hoodiehq/grunt-release-hoodie. It automatically generates CHANGELOGs (example) and addes releases on Github (example).

For status.hood.ie, I'm not sure yet if it should be fully automated. This issue is more about dreaming up the ideal outcome of a Hoodie status page (or however we will call it), that answers the following question:

• What is the current Hoodie version
  As Hoodie consists of several modules, we want to create a "marketing" version, to show where Hoodie stands and what has been done since another version (that I might use in production)
• Are there any known issues with the current (or a past) Hoodie version?
  It should be the go-to page if there I run into a problem with Hoodie, to find out if it is a known issue, and if an update is available that fixes it.
• other ideas would be to show, what we are currently working on, thanking other people for their respective contributions, and probably more.

I'm not sure where this is heading, but the idea is to agree on where it should go conceptually, than take the simplest subset of it, build it, and leave the rest for later™

[lenareinhard]

Like the general idea, and I'm happy to discuss how a) this aligns with the new release process (which is also supposed to include release notes, we should see which can be auto-generated and which ones we create manually) b) this can be integrated in the new website. In terms of design, we then can also discuss if we e.g. integrate a sidebar displaying all earlier versions so the page only shows the current version and people with older versions can click on version numbers, so we could keep this page itself shorter (or similar). I'm also +1 for integrating parts of the Firefox release notes as we have this content anyway and it's a good place for displaying it. For the wording, I'd also suggest e.g. status.hood.ie so we can use it to display both Hoodie's current version (+ release notes etc.) and changes to earlier versions.

[gr2m]

As discussed with @boennemann, we will leave that out of the Quality Assurance milestone and get back to it later