You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2017/04/20 09:55:40 UTC

https://reporter.apache.org/ jira integration issue?

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>

Re: https://reporter.apache.org/ jira integration issue?

Posted by sebb <se...@gmail.com>.
On 20 April 2017 at 20:02, Mark Struberg <st...@yahoo.de.invalid> wrote:
> This has not bean dealt with that way for many projects historically.
> E.g. not all maven plugins are served via dist, but via repository.a.o.

The ASF mission is to release open *source* to the public.
It is a requirement that the full source needed to build the product
is published via the ASF mirror system.
(refer back to the links I provided earlier)

That does not mean that the source and binaries cannot be published elsewhere.

> LieGrue,
> strub
>
>
>> Am 20.04.2017 um 18:11 schrieb sebb <se...@gmail.com>:
>>
>> On 20 April 2017 at 11:08, Mark Struberg <st...@yahoo.de.invalid> wrote:
>>> The geronimo-spec jars do most probably not.
>>> Should we set this up that way? Probably a good idea...
>>
>> AIUI all source releases MUST be made through the ASF mirror system.
>>
>> http://www.apache.org/legal/release-policy.html#source-packages
>> http://www.apache.org/legal/release-policy.html#release-distribution
>>
>> The source can also be made available through other channels, but the
>> primary publication mechanism is via the ASF mirror system.
>>
>>> LieGrue,
>>> strub
>>>
>>>> Am 20.04.2017 um 12:02 schrieb John D. Ament <jo...@apache.org>:
>>>>
>>>> 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 <rm...@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-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org

Re: https://reporter.apache.org/ jira integration issue?

Posted by Mark Struberg <st...@yahoo.de.INVALID>.
This has not bean dealt with that way for many projects historically.
E.g. not all maven plugins are served via dist, but via repository.a.o.

LieGrue,
strub


> Am 20.04.2017 um 18:11 schrieb sebb <se...@gmail.com>:
> 
> On 20 April 2017 at 11:08, Mark Struberg <st...@yahoo.de.invalid> wrote:
>> The geronimo-spec jars do most probably not.
>> Should we set this up that way? Probably a good idea...
> 
> AIUI all source releases MUST be made through the ASF mirror system.
> 
> http://www.apache.org/legal/release-policy.html#source-packages
> http://www.apache.org/legal/release-policy.html#release-distribution
> 
> The source can also be made available through other channels, but the
> primary publication mechanism is via the ASF mirror system.
> 
>> LieGrue,
>> strub
>> 
>>> Am 20.04.2017 um 12:02 schrieb John D. Ament <jo...@apache.org>:
>>> 
>>> 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 <rm...@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-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org

Re: https://reporter.apache.org/ jira integration issue?

Posted by sebb <se...@gmail.com>.
On 20 April 2017 at 11:08, Mark Struberg <st...@yahoo.de.invalid> wrote:
> The geronimo-spec jars do most probably not.
> Should we set this up that way? Probably a good idea...

AIUI all source releases MUST be made through the ASF mirror system.

http://www.apache.org/legal/release-policy.html#source-packages
http://www.apache.org/legal/release-policy.html#release-distribution

The source can also be made available through other channels, but the
primary publication mechanism is via the ASF mirror system.

> LieGrue,
> strub
>
>> Am 20.04.2017 um 12:02 schrieb John D. Ament <jo...@apache.org>:
>>
>> 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 <rm...@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-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org

Re: https://reporter.apache.org/ jira integration issue?

Posted by Mark Struberg <st...@yahoo.de.INVALID>.
The geronimo-spec jars do most probably not.
Should we set this up that way? Probably a good idea...

LieGrue,
strub

> Am 20.04.2017 um 12:02 schrieb John D. Ament <jo...@apache.org>:
> 
> 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 <rm...@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-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org

Re: https://reporter.apache.org/ jira integration issue?

Posted by sebb <se...@gmail.com>.
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 <jo...@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 <rm...@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-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org

Re: https://reporter.apache.org/ jira integration issue?

Posted by "John D. Ament" <jo...@apache.org>.
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 <rm...@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>
>