If its being linked to later I'd just put it in a subdir of the website. I'd do that even before/during the vote so it isnt complicating the final release steps as it did this time. Alternatively, or if it isnt being linked to later, at least moving it to a different subdir of the dist dev area than the release files would give the same effect.
On 21 May 2018 at 19:01, Clebert Suconic <clebert.suco...@gmail.com> wrote: > If we update the Release guide to include the commit report. Is there > any git repo we could include it, as a sub project of ActiveMQ? > > The report could actually work on both ActiveMQ and Artemis codebases. > > On Thu, May 17, 2018 at 8:35 AM, Clebert Suconic > <clebert.suco...@gmail.com> wrote: >> I meant the announcement email. And the report staying along with the >> release notes as you said. Not on the mirrors no. >> >> >> On Thu, May 17, 2018 at 7:29 AM Robbie Gemmell <robbie.gemm...@gmail.com> >> wrote: >>> >>> I think the report is nice, consolidating the details as it does. Its >>> worth saying much of it is essentially available live via the JIRA >>> release notes though given appropriate JIRA/commit handling. >>> >>> When you mention "the release report", do you mean the announcement >>> email? If so I dont think including it would be an issue, though I >>> probably wouldnt as the existing JIRA based release notes output (e.g >>> http://activemq.apache.org/artemis/release-notes-2.5.0.html) seems >>> more suited for typical user needs to me than this, which feels like >>> it would be more useful to e.g the community before/during the vote. >>> >>> I dont think it should be put on the mirrors however, which it >>> currently would be if left in the location it is now and the release >>> is published in the prior manner. Putting it on the website seems more >>> appropriate. If it is to be put on the mirrors however its essentially >>> 'released' and so likely needs some licensing information added as the >>> HTML has none (though it is generated, so that may be ok) and the js >>> files distributed alongside dont detail any other than URLs which isnt >>> sufficient. The css at least mentions the names along with its URLs, >>> but thats perhaps not sufficient either. >>> >>> Robbie >>> >>> On 17 May 2018 at 03:52, Clebert Suconic <clebert.suco...@gmail.com> >>> wrote: >>> > Before someone asks on the VOTE Thread.. I wanted to point out that I >>> > made a small project to parse git commit and generate a report. >>> > >>> > I have ran the report on top of artemis and I'm adding a commit report >>> > here that can be useful at least on the voter's thread: >>> > >>> > >>> > https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.6.0/artemis-2.6.0.html >>> > >>> > >>> > >>> > I think it would be useful to have this one on top of the release >>> > report as well. If nobody opposes I would like to add it to the next >>> > release report. >>> > >>> > The report generator current lives on my github page but it could be >>> > moved somewhere else if someone bothers about being on my github fork: >>> > >>> > https://github.com/clebertsuconic/git-release-report >>> > >>> > -- >>> > Clebert Suconic >> >> -- >> Clebert Suconic > > > > -- > Clebert Suconic
