All releases go to MC.

Gary

On Fri, Jul 21, 2023, 10:47 <jeremias.epp...@mercedes-benz.com.invalid>
wrote:

> Hello Gary,
>
> are you releasing the Apache Commons FileUpload 2.0.0-M1 to Maven Central
> as well?
> That would make the testing easier.
>
> Regards
>   Jeremias
>
> -----Original Message-----
> From: Gary Gregory <garydgreg...@gmail.com>
> Sent: Friday, 21 July 2023 15:43
> To: Commons Developers List <dev@commons.apache.org>
> Subject: Re: [ANNOUNCE] Apache Commons FileUpload 2.0.0-M1
>
> [**EXTERNAL E-MAIL**]
>
> This is a milestone release because we might not have the gotten the API
> just right for a major release. This gives up the opportunity to receive
> feedback and adjust the API for what will be 2.0.0. All lot of folks will
> not try a snapshot build, which then leaves us in the dark.
>
> WRT to the missing data, I'll adjust that but it won't show up on the site
> until the next version is published.
>
> HTH,
> Gary
>
>
> On Fri, Jul 21, 2023, 08:53 Christoph GrĂ¼ninger <f...@grueninger.de>
> wrote:
>
> > Hi Gary!
> >
> > Thank you for this release and thanks to all the diligent contributors!
> > Having a new release with new features, cleaned-up interfaces, and
> > updated dependencies is much appreciated!
> > I also learned from the recent discussion whether FileUpload is still
> > a good idea [1].
> >
> >  > The Apache Commons FileUpload Parent team is pleased to announce
> > the  > release of Apache Commons FileUpload Parent 2.0.0-M1.
> >
> > Why is the release called "-M1" and not plain 2.0.0?
> >
> > When I follow
> >   https://commons.apache.org/proper/commons-fileupload/
> > the top release entry in the Downloading section for version 2.0.0
> > lacks the release date.
> >
> > Kind regards,
> > Christoph
> >
> >
> > [1] https://lists.apache.org/thread/js8fccsvwbgx9x6ntpy0v0br1cbb77n9
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>
> If you are not the addressee, please inform us immediately that you have
> received this e-mail by mistake, and delete it. We thank you for your
> support.
>
>

Reply via email to