You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Geoffrey Blake <ge...@gmail.com> on 2020/04/07 20:04:06 UTC
[crypto] Help getting new release of commons-crypto?
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-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [crypto] Help getting new release of commons-crypto?
Posted by Alex Remily <al...@gmail.com>.
Thanks for the links. I'll do just that.
On Wed, Apr 8, 2020 at 7:46 PM Gilles Sadowski <gi...@gmail.com> wrote:
> Hi.
>
> 2020-04-09 1:15 UTC+02:00, Alex Remily <al...@gmail.com>:
> > I guess we're both in the same boat.
>
> Did you try and ping the people[1] (or their respective project[2])
> who contributed to that component?
>
> Regards,
> Gilles
>
> [1] http://commons.apache.org/proper/commons-crypto/team-list.html
> [2]
> https://gitbox.apache.org/repos/asf?p=commons-crypto.git;a=blob;f=PROPOSAL.html;h=6d374ffff0dc4cc4c61c016d16cfd82020e38c17;hb=HEAD
>
> >>> [...]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [crypto] Help getting new release of commons-crypto?
Posted by Gilles Sadowski <gi...@gmail.com>.
Hi.
2020-04-09 1:15 UTC+02:00, Alex Remily <al...@gmail.com>:
> I guess we're both in the same boat.
Did you try and ping the people[1] (or their respective project[2])
who contributed to that component?
Regards,
Gilles
[1] http://commons.apache.org/proper/commons-crypto/team-list.html
[2] https://gitbox.apache.org/repos/asf?p=commons-crypto.git;a=blob;f=PROPOSAL.html;h=6d374ffff0dc4cc4c61c016d16cfd82020e38c17;hb=HEAD
>>> [...]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [crypto] Help getting new release of commons-crypto?
Posted by Alex Remily <al...@gmail.com>.
I guess we're both in the same boat.
On Wed, Apr 8, 2020 at 5:48 PM Geoffrey Blake <ge...@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 <al...@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.blake@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-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [crypto] Help getting new release of commons-crypto?
Posted by Geoffrey Blake <ge...@gmail.com>.
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 <al...@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 <ge...@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-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [crypto] Help getting new release of commons-crypto?
Posted by Alex Remily <al...@gmail.com>.
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 <ge...@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>