Proposal: Create an aggregated know issues page for SDC releases

[pannon]

This is just a proposal to create an aggregated page to allow SDC users to track known issues between SDC releases.

Currently it is hard to look up known issues between releases. One needs to check each SDC component on GH to figure out possible show stoppers before an actual upgrade is undertaken.

Some background on recent experiences: Encountered the following regression https://github.com/joyent/sdc-napi/issues/8 literally a day before the next "fixed" release was pushed to the release channel.

This was a know issue for roughly two weeks, could have been avoided if we knew it in advance.

Was thinking about a simple page which clearly outlines regressions between releases so folks can avoid possible pitfalls and surprises before upgrading to an affected release.

[trentm]

I'm definitely supportive of the idea. I don't know how to do a good job maintaining it.

@lloydde thoughts?

[pannon]

@trentm @lloydde maybe just a one liner a few days after the release , saying no known issues or known issues bullet points.

[bahamat]

Maybe bugview could also use the github API to pull in issues from all SDC subprojcts?

[dwlf]

I can think of a number of incremental improvements, but I think when Triton floats it's time to advocate for a open SDC (and SmartOS) Jira (or other open bug tracker).