incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Cheung <>
Subject Re: Podlings not following ASF release policy
Date Sun, 10 Feb 2019 20:26:46 GMT
... so I think we need to provide an option here.

No question that any unauthorized release is not allowed. But what about
while voting for a release?

It sounds like httpd has the same problem since some of these listed
“releases” are failed vote attempts (and so not official releases)

>From a casual check this seems like a very common problem for many projects
under as all git tags of RC show up as “release” on
GitHub automatically, and there isn’t a documented way to turn off this

What are our options?
a) do not push git tag for RC - it’s possible to vote on a git commit id
b) ok with RC git tag so long as they are pre-release on Github (and
annotated tag clearly stating not a release) and remove as soon as possible
(eg new RC, vote pass)
c) get GitHub to fix this

On Fri, Feb 8, 2019 at 11:59 PM Daniel Gruno <> wrote:

> On 2/9/19 8:50 AM, Justin Mclean wrote:
> > HI,
> >
> >>  From what I can see with httpd, the issue is the same(?)
> >
> > Not quite as I not see any release candidates listed.
> ah, well, httpd doesn't do release candidates :p we tag a release, vote
> on it, if it fails, you burn the version number and use a new one. so
> you'll see release "candidates" but just not recognize them unless you
> know which versions failed to get the proper votes.
> >
> > Thanks,
> > Justin
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message