mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carin Meier <carinme...@gmail.com>
Subject Re: Help with the Clojure release jars
Date Sun, 24 Feb 2019 23:52:49 GMT
Ok. I will open an INFRA ticket for it and keep this thread updated.

On Sun, Feb 24, 2019 at 6:49 PM Naveen Swamy <mnnaveen@gmail.com> wrote:

> Since we release and vote on source and these were not a part of the
> voting, I think it's ok do it independently I.e proceed with clean up
> followed by rerelease so it won't impact closure users
>
> > On Feb 24, 2019, at 3:46 PM, Carin Meier <carinmeier@gmail.com> wrote:
> >
> > Yes. It looks a bit confusing because I have a copy for the jars both in
> > staging and in releases since after I hit release, I created them again
> > while my brain was trying to figure out what went wrong.
> >
> > My understanding after talking with #asfinfra is that we would have to:
> > 1) Create an infra ticket to delete it from repository.apache.org
> > 2) Create a ticket with issues.sonatype.org to delete it from central
> >
> > We can either
> > -  Wait and let them be until the vote concludes, if the vote doesn't
> pass
> > I can make the tickets to delete them.
> > - Create the tickets and delete them now.
> >
> > Let me know if this is what we want to do and I will kick off the
> process.
> >
> > -Carin
> >
> >> On Sun, Feb 24, 2019 at 6:39 PM Naveen Swamy <mnnaveen@gmail.com>
> wrote:
> >>
> >> 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 <carinmeier@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 <carinmeier@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 <carinmeier@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
> >>>>>
> >>>>
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message