Hello, I did not take part in the discussions but when just using github-issues instead of JIRA, this would probably be a piece of cake. With the added benefit, that finally creation of milestones/releases would be in the responsibility of a plugin team.
Today even linking issues between different projects/organizations is easily possible. Regards Mirko -- Sent from my mobile On Apr 18, 2013 7:18 PM, "Kohsuke Kawaguchi" <[email protected]> wrote: > On 04/17/2013 02:24 PM, Stephen Connolly wrote: > >> We could ask Sacha about open sourcing the release-notes part of our >> internal >> tools.... unless you're still bitching about them that is ;-) >> >> Yes yes, I used backbone and didn't use stapler... but come on, I did use >> JAX-RS >> and that was your baby too ;-) >> > > The reservation I have with what you've done has nothing to do with > Backbone/Stapler. FWIW I've built an app that uses both backbone and > stapler --- they aren't competing. > > And no, claiming that JAX-RS is my baby is stealing the credit from the > JAX-RS team. > > > On 17 April 2013 21:25, Kohsuke Kawaguchi <[email protected] >> <mailto:kkawaguchi@cloudbees.**com <[email protected]>>> wrote: >> >> >> As discussed in the project meeting several weeks ago, I dig up what >> I >> wrote, made a bit of improvement, and put it in [1]. It is being run >> at [2]. >> >> This looks at the usual commit markers of the form [FIXED >> JENKINS-1234], and >> generates a JSON file like [4]. >> >> Now, the original conversation involved perhaps using git-notes to >> supplement what's in the commit messages, but according to [3] it >> doesn't >> look very promising, because of the lack of support in the mechanism >> to >> share/merge notes. >> >> Another possibility is to use GitHub commit comments and scrape them, >> although the GitHub UI doesn't allow humans to very easily list them >> all >> (while REST API does allow the program to efficiently iterate them >> all.) >> >> Another disadvantage is that those comments are no longer in Git >> itself. >> >> [1] >> https://github.com/jenkinsci/_**_backend-commit-history-parser<https://github.com/jenkinsci/__backend-commit-history-parser> >> >> <https://github.com/jenkinsci/**backend-commit-history-parser<https://github.com/jenkinsci/backend-commit-history-parser> >> > >> [2] >> https://ci.jenkins-ci.org/__**view/Infrastructure/job/infra_** >> __commit_history_generation<https://ci.jenkins-ci.org/__view/Infrastructure/job/infra___commit_history_generation> >> <https://ci.jenkins-ci.org/**view/Infrastructure/job/infra_** >> commit_history_generation<https://ci.jenkins-ci.org/view/Infrastructure/job/infra_commit_history_generation> >> > >> [3] >> http://git-scm.com/2010/08/25/**__notes.html<http://git-scm.com/2010/08/25/__notes.html> >> >> <http://git-scm.com/2010/08/**25/notes.html<http://git-scm.com/2010/08/25/notes.html> >> > >> [4] >> https://ci.jenkins-ci.org/__**view/Infrastructure/job/infra_** >> __commit_history_generation/__**lastSuccessfulBuild/artifact/_** >> _release-changelog.json<https://ci.jenkins-ci.org/__view/Infrastructure/job/infra___commit_history_generation/__lastSuccessfulBuild/artifact/__release-changelog.json> >> <https://ci.jenkins-ci.org/**view/Infrastructure/job/infra_** >> commit_history_generation/**lastSuccessfulBuild/artifact/** >> release-changelog.json<https://ci.jenkins-ci.org/view/Infrastructure/job/infra_commit_history_generation/lastSuccessfulBuild/artifact/release-changelog.json> >> > >> -- >> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ >> Try Nectar, our professional version of Jenkins >> >> -- >> You received this message because you are subscribed to the Google >> Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, >> send an >> email to >> jenkinsci-dev+unsubscribe@__go**oglegroups.com<http://googlegroups.com> >> >> <mailto:jenkinsci-dev%**[email protected]<jenkinsci-dev%[email protected]> >> **>. >> For more options, visit >> https://groups.google.com/__**groups/opt_out<https://groups.google.com/__groups/opt_out> >> >> <https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> >. >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email >> to >> jenkinsci-dev+unsubscribe@**googlegroups.com<jenkinsci-dev%[email protected]> >> . >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> >> > > -- > Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ > Try Nectar, our professional version of Jenkins > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > jenkinsci-dev+unsubscribe@**googlegroups.com<jenkinsci-dev%[email protected]> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
