You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by Justin Mclean <ju...@classsoftware.com> on 2015/09/25 17:11:03 UTC

3.1.1 release candidates

Hi,

Just noticed that there was a RC2 for 3.1.1 and now there’s an RC3. I don’t recall a VOTE on RC2 or any discussion around dropping RC2, but I certainly could of missed it given the volume of mail.

Release candidates have a particular meaning in Apache and it best to follow this [1] If the release candidates referred to are not release candidates as Apache understands them perhaps you need to name them something else?

Thanks,
Justin

1. http://incubator.apache.org/guides/releasemanagement.html#best-practices-release-candidates

Re: 3.1.1 release candidates

Posted by Thomas Weise <th...@datatorrent.com>.

Hi Justin,

We will make sure that 3.1.x is not referred to as Apache release. The plan
is to make the transition with creation of release-3.2 branch so that there
is sufficient time to adopt Apache compatible practices. There are a number
of source code changes (licensing related etc.) that will need to be
completed.

Thanks,
Thomas

On Fri, Sep 25, 2015 at 9:05 AM, Justin Mclean <ju...@classsoftware.com>
wrote:

> Hi,
>
> > Thanks for pointing this out. There is no plan to release 3.1.1 in
> Apache.
>
> Seems a little odd given the project is now part of the incubator, but as
> long as it not referred to as an Apache release that would be OK. I assume
> there are reasons for doing this, but would it be that hard to make it an
> Apache release?
>
> > Do you foresee any issues just pushing the version changes and tags for
> > 3.1.X to the ASF repo?]
>
> May cause a little confusion as you’ll have something that it tagged as a
> release when it’s not a voted on Apache release.
>
> Thanks,
> Justin

Re: 3.1.1 release candidates

Posted by Justin Mclean <ju...@classsoftware.com>.

Hi,

> Thanks for pointing this out. There is no plan to release 3.1.1 in Apache.

Seems a little odd given the project is now part of the incubator, but as long as it not referred to as an Apache release that would be OK. I assume there are reasons for doing this, but would it be that hard to make it an Apache release?

> Do you foresee any issues just pushing the version changes and tags for
> 3.1.X to the ASF repo?]

May cause a little confusion as you’ll have something that it tagged as a release when it’s not a voted on Apache release.

Thanks,
Justin

Re: 3.1.1 release candidates

Posted by Thomas Weise <th...@datatorrent.com>.

Hi Justin,

Thanks for pointing this out. There is no plan to release 3.1.1 in Apache.
The first release in Apache will be 3.2.0 and it will follow the ASF
guidelines, including vote. The prep work for that (including license
headers) is already happening in the devel-3 branch.

Do you foresee any issues just pushing the version changes and tags for
3.1.X to the ASF repo?

Thanks,
Thomas

On Fri, Sep 25, 2015 at 8:11 AM, Justin Mclean <ju...@classsoftware.com>
wrote:

> Hi,
>
> Just noticed that there was a RC2 for 3.1.1 and now there’s an RC3. I
> don’t recall a VOTE on RC2 or any discussion around dropping RC2, but I
> certainly could of missed it given the volume of mail.
>
> Release candidates have a particular meaning in Apache and it best to
> follow this [1] If the release candidates referred to are not release
> candidates as Apache understands them perhaps you need to name them
> something else?
>
> Thanks,
> Justin
>
> 1.
> http://incubator.apache.org/guides/releasemanagement.html#best-practices-release-candidates