You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Matt Sicker <bo...@gmail.com> on 2021/07/09 16:25:30 UTC
Can we put together some sort of contributors guide for release requesters?
There seems to be an increased interest from users around making
releases of various components in order to clean up their security
checklists mandated from above. Since making releases is somewhat
standardized here, would it make sense to create some sort of guide
for volunteers who want releases to get involved and do the work? It
would definitely be great to point to a link whenever someone comes in
asking for commons-xyz to be released because it has an outdated
dependency or some security scanner identified some issue that was
fixed but unreleased.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Can we put together some sort of contributors guide for release requesters?
Posted by Gary Gregory <ga...@gmail.com>.
See also https://commons.apache.org/releases/index.html
Gary
On Fri, Jul 9, 2021, 19:02 Matt Sicker <bo...@gmail.com> wrote:
> Yes, and that’s one thing that can be in the guide. Anyone at Apache can
> commit here. If there are users who want to step up and do release
> management, they could perhaps shadow with someone else a few times before
> becoming a committer.
>
> On Fri, Jul 9, 2021 at 16:20 Enrico Olivelli <eo...@gmail.com> wrote:
>
> > Matt,
> >
> > Il Ven 9 Lug 2021, 18:25 Matt Sicker <bo...@gmail.com> ha scritto:
> >
> > > There seems to be an increased interest from users around making
> > > releases of various components in order to clean up their security
> > > checklists mandated from above. Since making releases is somewhat
> > > standardized here, would it make sense to create some sort of guide
> > > for volunteers who want releases to get involved and do the work? It
> > > would definitely be great to point to a link whenever someone comes in
> > > asking for commons-xyz to be released because it has an outdated
> > > dependency or some security scanner identified some issue that was
> > > fixed but unreleased.
> > >
> >
> > Wouldn't the volunteer need committer karma?
> >
> >
> > Enrico
> >
> >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> >
>
Re: Can we put together some sort of contributors guide for release requesters?
Posted by Matt Sicker <bo...@gmail.com>.
Yes, and that’s one thing that can be in the guide. Anyone at Apache can
commit here. If there are users who want to step up and do release
management, they could perhaps shadow with someone else a few times before
becoming a committer.
On Fri, Jul 9, 2021 at 16:20 Enrico Olivelli <eo...@gmail.com> wrote:
> Matt,
>
> Il Ven 9 Lug 2021, 18:25 Matt Sicker <bo...@gmail.com> ha scritto:
>
> > There seems to be an increased interest from users around making
> > releases of various components in order to clean up their security
> > checklists mandated from above. Since making releases is somewhat
> > standardized here, would it make sense to create some sort of guide
> > for volunteers who want releases to get involved and do the work? It
> > would definitely be great to point to a link whenever someone comes in
> > asking for commons-xyz to be released because it has an outdated
> > dependency or some security scanner identified some issue that was
> > fixed but unreleased.
> >
>
> Wouldn't the volunteer need committer karma?
>
>
> Enrico
>
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
Re: Can we put together some sort of contributors guide for release requesters?
Posted by Enrico Olivelli <eo...@gmail.com>.
Matt,
Il Ven 9 Lug 2021, 18:25 Matt Sicker <bo...@gmail.com> ha scritto:
> There seems to be an increased interest from users around making
> releases of various components in order to clean up their security
> checklists mandated from above. Since making releases is somewhat
> standardized here, would it make sense to create some sort of guide
> for volunteers who want releases to get involved and do the work? It
> would definitely be great to point to a link whenever someone comes in
> asking for commons-xyz to be released because it has an outdated
> dependency or some security scanner identified some issue that was
> fixed but unreleased.
>
Wouldn't the volunteer need committer karma?
Enrico
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>