I guess we're both in the same boat. On Wed, Apr 8, 2020 at 5:48 PM Geoffrey Blake <geoffrey.w.bl...@gmail.com> wrote:
> Marcelo Vanzin was the one to help get a patch I submitted pushed into > commons-crypto for natively supported arm64 this past week. He is > still around but mentioned in my PR he is not aware of how to create > the release and upload it. I'm able to manually build the different > bits of the release on the required platforms, but I certainly don't > know what is needed in terms of credentials and process to make a new > release of a commons* package. > > -Geoff > > On Tue, Apr 7, 2020 at 8:43 PM Alex Remily <alex.rem...@gmail.com> wrote: > > > > I think most of the original developers have moved on. I did some of the > > recent updates surrounding 1.1.1 support, and Marcelo was a big help > > throughout the process. He established design goals, reviewed code, > > provided tips, etc. I haven't seen him around in a while though, and I'm > > not sure that he's still active. I've also asked about getting a new > > release out, and I'm happy to work with someone who has commit > permissions > > to make it happen. I've never done a release for apache commons, but I'm > > sure I could figure it out if I was teamed with someone who had the > proper > > access and was pointed in the right direction. > > > > Alex > > > > On Tue, Apr 7, 2020 at 4:04 PM Geoffrey Blake < > geoffrey.w.bl...@gmail.com> > > wrote: > > > > > Hi all, > > > > > > I see its been 4 years since the last release of commons crypto to > > > https://mvnrepository.com/artifact/org.apache.commons/commons-crypto. > > > There has been many updates to the repository since then, notably the > > > integration of OpenSSL 1.1.1, and native arm64 support. > > > > > > What are the blockers to make a new release of commons-crypto, say > > > v1.1? Is there a maintainer around that can help with getting a new > > > release uploaded to Maven central? > > > > > > Thanks, > > > Geoff Blake > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
