Does any of this help? (1) https://commons.apache.org/releases/index.html (2) https://infra.apache.org/release-publishing.html
Eric Bresie ebre...@gmail.com (mailto:ebre...@gmail.com) > On July 17, 2022 at 2:59:26 PM CDT, Gary Gregory <garydgreg...@gmail.com > (mailto:garydgreg...@gmail.com)> wrote: > Yeah, there is code that looks odd for 2022, like a custom Closeable > interface instead of reusing the JRE's. I'll take a look. > > Gary > > On Sun, Jul 17, 2022 at 2:32 PM Matt Juntunen <matt.a.juntu...@gmail.com > (mailto:matt.a.juntu...@gmail.com)> wrote: > > > > Sounds good. Do you know of anything else that needs to be done? I'm > > guessing we can hold off on a full 1.x migration guide until the full > > 2.0.0 version. > > > > -Matt J > > > > On Sun, Jul 17, 2022 at 2:13 PM Gary Gregory <garydgreg...@gmail.com > > (mailto:garydgreg...@gmail.com)> wrote: > > > > > > We should at least remove deprecated elements. > > > > > > Gary > > > > > > On Sun, Jul 17, 2022 at 10:49 AM Matt Juntunen > > > <matt.a.juntu...@gmail.com (mailto:matt.a.juntu...@gmail.com)> wrote: > > > > > > > > I am going to put the 2.0.0-beta1 release on my TODO list. I am > > > > currently working toward a release of commons-text, so I can't be sure > > > > on a timeline. If anyone has questions or time to pick this up, please > > > > let me know. > > > > > > > > Regards, > > > > Matt J > > > > > > > > On Fri, Jul 15, 2022 at 12:35 PM Matt Juntunen > > > > <matt.a.juntu...@gmail.com (mailto:matt.a.juntu...@gmail.com)> wrote: > > > > > > > > > > It sounds like we've agreed on creating a 2.0.0-beta1 release. Does > > > > > anyone have availability to lead the release? > > > > > > > > > > Regards, > > > > > Matt J > > > > > > > > > > On Wed, Jul 13, 2022 at 9:35 AM sebb <seb...@gmail.com > > > > > (mailto:seb...@gmail.com)> wrote: > > > > > > > > > > > > It looks like Commons does not have the concept of Alpha releases. > > > > > > > > > > > > https://commons.apache.org/releases/versioning.html > > > > > > > > > > > > Sorry, I must have been thinking of a different project. > > > > > > > > > > > > Sebb > > > > > > > > > > > > On Wed, 13 Jul 2022 at 01:36, Gary Gregory <garydgreg...@gmail.com > > > > > > (mailto:garydgreg...@gmail.com)> wrote: > > > > > > > > > > > > > > A beta is a good idea IMO. > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > On Tue, Jul 12, 2022, 17:19 Matt Juntunen > > > > > > > <matt.a.juntu...@gmail.com (mailto:matt.a.juntu...@gmail.com)> > > > > > > > wrote: > > > > > > > > > > > > > > > Based on what I'm hearing, I'm thinking a beta release might be > > > > > > > > appropriate. That would give consumers a chance to move away > > > > > > > > from the > > > > > > > > previous version while giving us a chance to test and fine-tune > > > > > > > > the > > > > > > > > API. Thoughts? > > > > > > > > > > > > > > > > Regards, > > > > > > > > Matt J > > > > > > > > > > > > > > > > On Tue, Jul 12, 2022 at 4:15 PM Christoph Grüninger > > > > > > > > <f...@grueninger.de (mailto:f...@grueninger.de)> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Publishing a first release candidate might help. Currently > > > > > > > > > there is no > > > > > > > > > indication for anybody to invest in testing FileUpload. > > > > > > > > > > > > > > > > > > In doubt: release early, release often. People are using > > > > > > > > > FileUpload > > > > > > > > > together with vulnerable dependencies! > > > > > > > > > > > > > > > > > > Bye > > > > > > > > > Christoph > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > > > > > (mailto:dev-unsubscr...@commons.apache.org) > > > > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > (mailto:dev-h...@commons.apache.org) > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > > > > (mailto:dev-unsubscr...@commons.apache.org) > > > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > (mailto:dev-h...@commons.apache.org) > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > > (mailto:dev-unsubscr...@commons.apache.org) > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > (mailto:dev-h...@commons.apache.org) > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > (mailto:dev-unsubscr...@commons.apache.org) > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > (mailto:dev-h...@commons.apache.org) > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > (mailto:dev-unsubscr...@commons.apache.org) > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > (mailto:dev-h...@commons.apache.org) > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > (mailto:dev-unsubscr...@commons.apache.org) > > For additional commands, e-mail: dev-h...@commons.apache.org > > (mailto:dev-h...@commons.apache.org) > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > (mailto:dev-unsubscr...@commons.apache.org) > For additional commands, e-mail: dev-h...@commons.apache.org > (mailto:dev-h...@commons.apache.org) >
