Reporter.a.o does not automatically extract release data from JIRA. You have to tell it which JIRA keys to use.
Where a PMC has multiple products, you also need to provide a prefix if the JIRA release ids don't include that. Otherwise it gets very confusing... Or you can maintain the release versions manually. Note: Whenever a new release is detected in SVN dist, an email is sent to the committer, as they are assumed to be the RM. On 20 April 2017 at 11:02, John D. Ament <johndam...@apache.org> wrote: > Romain, > > Releases are sourced based on commits to your dist directory. Do xbean > releases go through our normal mirroring (e.g. source releases)? > > John > > On Thu, Apr 20, 2017 at 5:56 AM Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > >> Hi guys, >> >> working on geronimo board i realized https://reporter.apache.org/ can >> provide misleading result. I suspect it comes from the fact geronimo uses >> multiple jira projects. >> >> Question is: how can we validate there is an issue (bug, config issue or >> something else) regarding jira integration? for instance ATM it reports >> last release in 2014 but we got several since (multiple xbean in 2015 for >> instance). >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <https://blog-rmannibucau.rhcloud.com> | Old Blog >> <http://rmannibucau.wordpress.com> | Github < >> https://github.com/rmannibucau> | >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory >> <https://javaeefactory-rmannibucau.rhcloud.com> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
