Starting release process for 4.5.0

[Enrico Olivelli <eo...@gmail.com>]

Yesterday at the Community Meeting we discussed about when and how
starting the release process for 4.5.0.

First step is to choose a Release Manager.
I volunteer doing it.
Anyone else would like to manage the release ?

The second step (in charge to the release manager) will be to choose
final issues for 4.5.0. So we need to create all the issues that we
want to put in 4.5 before release.

The primary purpose of 4.5 was to join local forks from Salesforce,
Twitter and Yahoo.
We included security support and some other improvements/new features

Thoughts ?

-- Enrico

Re: Starting release process for 4.5.0

[Enrico Olivelli <eo...@gmail.com>]

Il ven 30 giu 2017, 18:04 Sijie Guo <gu...@gmail.com> ha scritto:

> On Jun 30, 2017 5:45 AM, "Enrico Olivelli" <eo...@gmail.com> wrote:
>
> Yesterday at the Community Meeting we discussed about when and how
> starting the release process for 4.5.0.
>
> First step is to choose a Release Manager.
> I volunteer doing it.
> Anyone else would like to manage the release ?
>
>
> Sorry about missing the meeting yesterday. I believed we discussed the 4.5
> release manager at the begining of this year. I think JV was the release
> manager for 4.5. because the goal for 4.5 is for merging Twitter and Yahoo
> branches. So I am helping with the Twitter branch and Matteo and Bobby's
> team are helping with Yahoo branch, Charan is helping with salesforce
> branch. JV was waiting from these three coordinators to finish their pieces
> before starting the 4.5 release.
>

No problem for me.
I have just sent this email on the dev@ list as we decided to do it at the
meeting.
Maybe I just misunderstood. I apologize.
Let's go ahead with the initial plan.


Enrico


> I'd like to continue with the plan and not change release manager at the
> last minute. Because we almost are reaching the point the current master
> work with both DL and Pulsar (Twitter and Yahoo).
>
>
> The second step (in charge to the release manager) will be to choose
> final issues for 4.5.0. So we need to create all the issues that we
> want to put in 4.5 before release.
>
>
> 4.5 is special because it is a merging effort. We should defer the
> questions to the representatives from three branches. Before they
> acknowledges the important changes from their branches has been merged, the
> release manager is still waiting.
>
> I think current blocker is on me merging the Twitter changes. If you want
> me to create an umbrella jira. I can do it.
>
>
> The primary purpose of 4.5 was to join local forks from Salesforce,
> Twitter and Yahoo.
>
>
> I believe people has been asking 4.5 a long time. If we set the goal for
> merging, I would stick to it and not change any release plan at last
> minute.
>
>
> We included security support and some other improvements/new features
>
> Thoughts ?
>
> -- Enrico
>
-- 


-- Enrico Olivelli

Re: Starting release process for 4.5.0

[Sijie Guo <gu...@gmail.com>]

On Jun 30, 2017 5:45 AM, "Enrico Olivelli" <eo...@gmail.com> wrote:

Yesterday at the Community Meeting we discussed about when and how
starting the release process for 4.5.0.

First step is to choose a Release Manager.
I volunteer doing it.
Anyone else would like to manage the release ?


Sorry about missing the meeting yesterday. I believed we discussed the 4.5
release manager at the begining of this year. I think JV was the release
manager for 4.5. because the goal for 4.5 is for merging Twitter and Yahoo
branches. So I am helping with the Twitter branch and Matteo and Bobby's
team are helping with Yahoo branch, Charan is helping with salesforce
branch. JV was waiting from these three coordinators to finish their pieces
before starting the 4.5 release.

I'd like to continue with the plan and not change release manager at the
last minute. Because we almost are reaching the point the current master
work with both DL and Pulsar (Twitter and Yahoo).


The second step (in charge to the release manager) will be to choose
final issues for 4.5.0. So we need to create all the issues that we
want to put in 4.5 before release.


4.5 is special because it is a merging effort. We should defer the
questions to the representatives from three branches. Before they
acknowledges the important changes from their branches has been merged, the
release manager is still waiting.

I think current blocker is on me merging the Twitter changes. If you want
me to create an umbrella jira. I can do it.


The primary purpose of 4.5 was to join local forks from Salesforce,
Twitter and Yahoo.


I believe people has been asking 4.5 a long time. If we set the goal for
merging, I would stick to it and not change any release plan at last minute.


We included security support and some other improvements/new features

Thoughts ?

-- Enrico