commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pascal Schumacher <pascalschumac...@gmx.net>
Subject Re: Moving component to dormant - Make JIRA read-only?
Date Sun, 24 Sep 2017 12:31:17 GMT
commons discovery already had this JIRA description:

"RELEASE PLAN: Project considered to be dormant - no release planned. "

I copied this for commons launcher.

Am 24.09.2017 um 14:28 schrieb sebb:
> The Attic is only for TLPs, not components of a TLP.
>
> It's up to the Commons PMC whether or not JIRA should be made read-only.
>
> I would be inclined to leave it open.
> Might be useful to collect reports against the component, even if
> nothing is planned to be done with them at present.
>
> Perhaps update the JIRA page header accordingly.
>
> On 24 September 2017 at 12:58, Bruno P. Kinoshita <kinow@apache.org> wrote:
>> I think dormant  means no activity, but anyone could try to restart work on the component
(tho I could be wrong).
>> So maybe we should do it when moving to the attic instead?
>> Bruno
>>
>> Sent from Yahoo Mail on Android
>>
>>    On Sun, 24 Sep 2017 at 21:42, Pascal Schumacher<pascalschumacher@gmx.net>
wrote:   Hello everybody,
>>
>> my understanding is that the JIRA of dormant components should be made
>> read-only.
>>
>> Is that correct? (I'm asking because
>> https://commons.apache.org/releases/moving-to-dormant.html does not
>> mention this.)
>>
>> Thanks,
>>
>> Pascal
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>


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


Mime
View raw message