Did you close the repo? In my understanding, the repo(*.Apache.org) is under 
infra's control, so we porbably have to create a infra ticket, last time I 
wasn't able to delete( luckily it was in staging, so I abandoned and released 
to staging again.)

> On Feb 24, 2019, at 2:36 PM, Carin Meier <carinme...@gmail.com> wrote:
> From the #infra channel, the options to fix seem to be that it can be
> deleted from the repository.apache.org, but we'd need to talk to sonatype
> about getting it removed.
> I'm not exactly sure where we are in the voting process for release, so
> please let me know how everyone would like to proceed.
> Sorry again and I'll take steps to make sure that it won't happen again.
> Best,
> Carin
>> On Sun, Feb 24, 2019 at 5:19 PM Carin Meier <carinme...@gmail.com> wrote:
>> It appears I did accidentally release them :(
>> I'm chatting with Infra in the slack room to see if there are any fixes.
>> If anyone has any other ideas please let me know.
>>> On Sun, Feb 24, 2019 at 4:35 PM Carin Meier <carinme...@gmail.com> wrote:
>>> I was wondering if someone could help me verify if I accidentally
>>> released the Clojure jars.
>>> Background:
>>> I was creating and testing the Clojure jars for staging according my my
>>> instructions[1].
>>> I hit the close button on the repository but I didn't see it updated at
>>> the link
>>> https://repository.apache.org/content/repositories/staging/org/apache/mxnet/contrib/clojure/clojure-mxnet-linux-cpu/1.4.0/
>>> - so I hit the release button.
>>> Last time I did a release, I remember I had to explicitly hit the
>>> "promote" button to get it promoted to maven central at the release time,
>>> but now I'm not sure.
>>> So could someone please help me:
>>> 1) Figure out if I accidentally released it by mistake
>>>  - there are 3 jars: The clojure linux-cpu, linux-gpu, and osx-cpu
>>> 2) If I did, please tell me how/if I can fix it (and sorry of course)
>>> 3) Please let me know any corrections so I that I can update my process
>>> instructions and make sure it doesn't happen again.
>>> Thanks,
>>> Carin

Reply via email to