incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <johndam...@apache.org>
Subject Re: Non-voted Release Candidate binary downloadable from project homepage possible?
Date Fri, 08 Jan 2016 02:48:21 GMT
All,

I wanted to get others opinions.  Currently Freemarker creates two
artifacts - one is a GAE compatible module, the other is a regular
library.  They are created from two distinct branches in their SCM.  Are
those artifacts voted on together or separately?

John

On Thu, Dec 31, 2015 at 10:57 AM Daniel Dekany <ddekany@freemail.hu> wrote:

> Thursday, December 31, 2015, 3:26:19 PM, Marvin Humphrey wrote:
>
> > On Thu, Dec 31, 2015 at 3:25 AM, Daniel Dekany <ddekany@freemail.hu>
> wrote:
> >> OK thanks, makes sense, then RC-s at FreeMarker will go through the
> >> same process as final releases (except that they don't go to stable
> >> Maven Repo-s such as the Central).
> >>
> >> This, however, means that sometimes we will have two "latest releases"
> >> under http://www.apache.org/dist/incubator/freemarker/engine/, like
> >> 2.3.24-incubating/ and 2.3.25-incubating-rc1/. I hope that's fine.
> >> (The release policy says "/www.apache.org/dist should contain the
> >> latest release in each branch that is currently under development.",
> >> which doesn't strictly stand here.)
> >
> > Yes, that's fine.  That passage in the Release Distribution Policy is
> > primarily motivated by the need to keep the volume of material in
> mirrored
> > distribution under control.  Clearly it is appropriate in this case to go
> > against the SHOULD.
> >
> > Earlier I suggested that you would need two VOTEs for this approach.  If
> the
> > content of the "public RC"[1] source archive differs from that of the
> "final"
> > source archive, that's definitely true.  However, if the "final" is only
> a
> > renaming of the "public RC", I'd like to explore whether or not we can
> spare
> > you from the second VOTE.
> >
> > Is it the case that you could transform a "public RC" into a "final"
> using
> > only `svn mv` (and similar) to rename files within `
> dist.apache.org/release` <http://dist.apache.org/release>?
>
> The two releases aren't exactly the same because both the source and
> the binary contains the version number (which includes "rc01"). Also
> in practice there used to be at least some typo fixes anyway.
>
> > Marvin Humphrey
> >
> > [1] I'm using "public RC" here to differentiate from an RC which has not
> yet
> >     been approved for public distribtion by an Apache PMC following the
> >     Release Policy.
>
> --
> Thanks,
>  Daniel Dekany
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

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