whoops, kk. What I usually do is to add a comment to all staging repos I close. 
That way we know quickly what it is supposed to do.
Especially in bigger projects with many artifacts like geronimo, tomee, owb, 
etc it helps tremendously. In G we often have 5 staging repos open in parallel. 
Ofc this is a manual step release managers have to do.

LieGrue,
strub

> Am 06.08.2019 um 07:58 schrieb David Blevins <[email protected]>:
> 
> I was wrong :)  We did need that.  I was supposed to click release on that 
> one as it contained the patched bval from the M3 release.
> 
> I've quickly replaced it, so things are all fine.  Mental note to use the 
> same staging repo should we need to do that again -- which we hopefully won't 
> any time soon.
> 
> 
> -David
> 
> 
>> On Aug 4, 2019, at 11:40 PM, Mark Struberg <[email protected]> wrote:
>> 
>> Done.
>> 
>> LieGrue,
>> strub
>> 
>> 
>>> Am 05.08.2019 um 08:28 schrieb David Blevins <[email protected]>:
>>> 
>>> Go ahead and drop it.  Thank you!
>>> 
>>> Good catch.
>>> 
>>> -- 
>>> David Blevins
>>> http://twitter.com/dblevins
>>> http://www.tomitribe.com
>>> 
>>>> On Aug 4, 2019, at 11:15 PM, Mark Struberg <[email protected]> 
>>>> wrote:
>>>> 
>>>> Good morning!
>>>> 
>>>> While releasing Johnzon-1.1.13 I stumbled across a TomEE staging repo from 
>>>> May
>>>> https://repository.apache.org/content/repositories/orgapachetomee-1134
>>>> 
>>>> Can we drop this, or is it still needed?
>>>> 
>>>> LieGrue,
>>>> strub
>>> 
>> 
> 

Reply via email to