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

Posted to dev@samoa.apache.org by Gianmarco De Francisci Morales <gd...@apache.org> on 2015/04/27 10:10:20 UTC

[DISCUSS] First Apache release

Hi,

I think the time is ripe for us to cut the first Apache release.
Apart from a few fixes, I would like to include the new Flink integration.
If you would like something else to be included, this is the right place.

I volunteer to be the release manager for this round.

I have a few questions on the prerequisites for the release that maybe our
mentors might answer:

1) Do we need to fix the namespace of the source to an org.apache.* one?
2) Do we need to change the artifacts produced to be apache compliant?
3) Is there a guide to help cutting the release?

Thanks,
--
Gianmarco

Re: [DISCUSS] First Apache release

Posted by Gianmarco De Francisci Morales <gd...@apache.org>.

Daniel, Ted, Alan,
Does any of you have suggestions to give?

Thanks,



--
Gianmarco

On 27 April 2015 at 11:10, Gianmarco De Francisci Morales <gd...@apache.org>
wrote:

> Hi,
>
> I think the time is ripe for us to cut the first Apache release.
> Apart from a few fixes, I would like to include the new Flink integration.
> If you would like something else to be included, this is the right place.
>
> I volunteer to be the release manager for this round.
>
> I have a few questions on the prerequisites for the release that maybe our
> mentors might answer:
>
> 1) Do we need to fix the namespace of the source to an org.apache.* one?
> 2) Do we need to change the artifacts produced to be apache compliant?
> 3) Is there a guide to help cutting the release?
>
> Thanks,
> --
> Gianmarco
>

Re: [DISCUSS] First Apache release

Posted by Gianmarco De Francisci Morales <gd...@apache.org>.

Thanks for the info.

Then I will wait to merge SAMOA-16 and SAMOA-26, and create a PR to perform
the necessary changes.

--
Gianmarco

On 12 May 2015 at 01:21, Alan Gates <al...@gmail.com> wrote:

>
>
>   Gianmarco De Francisci Morales <gd...@apache.org>
>  April 27, 2015 at 1:10
> Hi,
>
> I think the time is ripe for us to cut the first Apache release.
> Apart from a few fixes, I would like to include the new Flink integration.
> If you would like something else to be included, this is the right place.
>
> I volunteer to be the release manager for this round.
>
> I have a few questions on the prerequisites for the release that maybe our
> mentors might answer:
>
> 1) Do we need to fix the namespace of the source to an org.apache.* one?
>
> You don't have to, but in my opinion this is great opportunity to do it.
> After a release it's harder because you'll (hopefully) have users that
> don't want you to change it.  I realize you may already have users who
> don't want the change, but moving to Apache is a natural boundary that
> makes it easier to get the change done.
>
> 2) Do we need to change the artifacts produced to be apache compliant?
>
> In what way?  The licensing, code grants, etc. certainly need to be dealt
> with.
>
> 3) Is there a guide to help cutting the release?
>
> http://incubator.apache.org/guides/releasemanagement.html
>
> Alan.
>
>
> Thanks,
> --
> Gianmarco
>
>

Re: [DISCUSS] First Apache release

Posted by Alan Gates <al...@gmail.com>.


> Gianmarco De Francisci Morales <ma...@apache.org>
> April 27, 2015 at 1:10
> Hi,
>
> I think the time is ripe for us to cut the first Apache release.
> Apart from a few fixes, I would like to include the new Flink integration.
> If you would like something else to be included, this is the right place.
>
> I volunteer to be the release manager for this round.
>
> I have a few questions on the prerequisites for the release that maybe our
> mentors might answer:
>
> 1) Do we need to fix the namespace of the source to an org.apache.* one?
You don't have to, but in my opinion this is great opportunity to do 
it.  After a release it's harder because you'll (hopefully) have users 
that don't want you to change it.  I realize you may already have users 
who don't want the change, but moving to Apache is a natural boundary 
that makes it easier to get the change done.
> 2) Do we need to change the artifacts produced to be apache compliant?
In what way?  The licensing, code grants, etc. certainly need to be 
dealt with.
> 3) Is there a guide to help cutting the release?
http://incubator.apache.org/guides/releasemanagement.html

Alan.
>
> Thanks,
> --
> Gianmarco
>