You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by Roman Shaposhnik <rv...@apache.org> on 2014/05/20 18:26:47 UTC
Picking up Giraph 1.1.0 release
Hi!
with apologies for dropping the ball on 1.1.0
back in March/April I'd like to restart the
release activities in earnest.
First things first: if you have a JIRA that you'd
like to see in 1.1.0 that hasn't been marked with
1.1.0 as "Fix version" please reply to this thread
this week.
As it stands today, our official bug count for 1.1.0
is not bad at all: http://s.apache.org/Jnu
Even better news is that *all* of the ones marked
for 1.1.0 have 'patch available'. There's stuff to
review and commit.
So here's what I'd propose we do for the rest of
this week: lets divvy up the load of reviewing of
committing the patches. If you guys don't mind,
I'd like to track this by having reviewers assign the
issues to themselves.
Here's the schedule:
1. by 5/26 we would expect all the JIRAs tagged
for 1.1.0 have committers assigned to them. Those
JIRAs that stay unassigned get pushed out of 1.1.0
2. by 6/2 those assigned to JIRAs make sure to
either resolve their JIRAs or push them out of 1.1.0
3. on 6/2 I cut a branch for 1.1.0 and we do the
usual round of testing/etc for a few weeks culminating
in actual release
Sounds good?
Thanks,
Roman (AKA reluctant RM for Giraph 1.1.0)
Re: Picking up Giraph 1.1.0 release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Jun 9, 2014 at 2:14 PM, Claudio Martella
<cl...@gmail.com> wrote:
> Actually, I was going to commit 874. Shall I commit it to release-1.1?
Just keep committing to trunk (the usual way), but every time
you think the JIRA should also go into 1.1 -- please ping me.
Thanks,
Roman.
Re: Picking up Giraph 1.1.0 release
Posted by Claudio Martella <cl...@gmail.com>.
Actually, I was going to commit 874. Shall I commit it to release-1.1?
On Mon, Jun 9, 2014 at 8:30 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> Hi!
>
> good news everyone! We've got just one JIRA left
> that is assigned to be fixed in 1.1:
> https://issues.apache.org/jira/browse/GIRAPH-747
> Everything else is either resolved or just tracks
> the release activities.
>
> Based on this, I have create a release-1.1 branch
> and will proceed with Bigtop-based testing for the
> next week. Based on the result of system testing
> hopefully we would be able to release in a week or so.
>
> For the next couple of weeks please be extra
> careful marking JIRAs with 1.1 to get things
> into the release.
>
> I plan to announce our first RC mid-week. It would
> be really nice if folks can jump on it and provide
> some additional testing.
>
> Finally, if somebody can look at GIRAPH-747 that
> also would be very much appreciated!
>
> Thanks,
> Roman.
>
--
Claudio Martella
Re: Picking up Giraph 1.1.0 release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Hi!
good news everyone! We've got just one JIRA left
that is assigned to be fixed in 1.1:
https://issues.apache.org/jira/browse/GIRAPH-747
Everything else is either resolved or just tracks
the release activities.
Based on this, I have create a release-1.1 branch
and will proceed with Bigtop-based testing for the
next week. Based on the result of system testing
hopefully we would be able to release in a week or so.
For the next couple of weeks please be extra
careful marking JIRAs with 1.1 to get things
into the release.
I plan to announce our first RC mid-week. It would
be really nice if folks can jump on it and provide
some additional testing.
Finally, if somebody can look at GIRAPH-747 that
also would be very much appreciated!
Thanks,
Roman.
Re: Picking up Giraph 1.1.0 release
Posted by Avery Ching <ac...@apache.org>.
Sounds good to me.
On 6/1/14, 7:17 AM, Roman Shaposhnik wrote:
> Last call for 1.1.0 'unassigned' issues:
> according to: http://s.apache.org/Jnu
> the following issues are still unassigned:
> https://issues.apache.org/jira/browse/GIRAPH-904
> https://issues.apache.org/jira/browse/GIRAPH-902
> https://issues.apache.org/jira/browse/GIRAPH-886
> https://issues.apache.org/jira/browse/GIRAPH-874
> https://issues.apache.org/jira/browse/GIRAPH-800
>
> As per our prior agreement, I'll be pushing
> them out of 1.1.0 on Monday, unless somebody
> volunteers and assigns them.
>
> Thanks,
> Roman.
>
>
> On Thu, May 22, 2014 at 1:19 PM, Avery Ching <av...@gmail.com> wrote:
>
>> Thanks for getting back to this Roman. The schedule sounds great. Let's
>> get this release cut!
>>
>>
>> On 5/20/14, 9:26 AM, Roman Shaposhnik wrote:
>>
>>> Hi!
>>>
>>> with apologies for dropping the ball on 1.1.0
>>> back in March/April I'd like to restart the
>>> release activities in earnest.
>>>
>>> First things first: if you have a JIRA that you'd
>>> like to see in 1.1.0 that hasn't been marked with
>>> 1.1.0 as "Fix version" please reply to this thread
>>> this week.
>>>
>>> As it stands today, our official bug count for 1.1.0
>>> is not bad at all: http://s.apache.org/Jnu
>>>
>>> Even better news is that *all* of the ones marked
>>> for 1.1.0 have 'patch available'. There's stuff to
>>> review and commit.
>>>
>>> So here's what I'd propose we do for the rest of
>>> this week: lets divvy up the load of reviewing of
>>> committing the patches. If you guys don't mind,
>>> I'd like to track this by having reviewers assign the
>>> issues to themselves.
>>>
>>> Here's the schedule:
>>> 1. by 5/26 we would expect all the JIRAs tagged
>>> for 1.1.0 have committers assigned to them. Those
>>> JIRAs that stay unassigned get pushed out of 1.1.0
>>>
>>> 2. by 6/2 those assigned to JIRAs make sure to
>>> either resolve their JIRAs or push them out of 1.1.0
>>>
>>> 3. on 6/2 I cut a branch for 1.1.0 and we do the
>>> usual round of testing/etc for a few weeks culminating
>>> in actual release
>>>
>>> Sounds good?
>>>
>>> Thanks,
>>> Roman (AKA reluctant RM for Giraph 1.1.0)
>>>
>>
Re: Picking up Giraph 1.1.0 release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Last call for 1.1.0 'unassigned' issues:
according to: http://s.apache.org/Jnu
the following issues are still unassigned:
https://issues.apache.org/jira/browse/GIRAPH-904
https://issues.apache.org/jira/browse/GIRAPH-902
https://issues.apache.org/jira/browse/GIRAPH-886
https://issues.apache.org/jira/browse/GIRAPH-874
https://issues.apache.org/jira/browse/GIRAPH-800
As per our prior agreement, I'll be pushing
them out of 1.1.0 on Monday, unless somebody
volunteers and assigns them.
Thanks,
Roman.
On Thu, May 22, 2014 at 1:19 PM, Avery Ching <av...@gmail.com> wrote:
> Thanks for getting back to this Roman. The schedule sounds great. Let's
> get this release cut!
>
>
> On 5/20/14, 9:26 AM, Roman Shaposhnik wrote:
>
>> Hi!
>>
>> with apologies for dropping the ball on 1.1.0
>> back in March/April I'd like to restart the
>> release activities in earnest.
>>
>> First things first: if you have a JIRA that you'd
>> like to see in 1.1.0 that hasn't been marked with
>> 1.1.0 as "Fix version" please reply to this thread
>> this week.
>>
>> As it stands today, our official bug count for 1.1.0
>> is not bad at all: http://s.apache.org/Jnu
>>
>> Even better news is that *all* of the ones marked
>> for 1.1.0 have 'patch available'. There's stuff to
>> review and commit.
>>
>> So here's what I'd propose we do for the rest of
>> this week: lets divvy up the load of reviewing of
>> committing the patches. If you guys don't mind,
>> I'd like to track this by having reviewers assign the
>> issues to themselves.
>>
>> Here's the schedule:
>> 1. by 5/26 we would expect all the JIRAs tagged
>> for 1.1.0 have committers assigned to them. Those
>> JIRAs that stay unassigned get pushed out of 1.1.0
>>
>> 2. by 6/2 those assigned to JIRAs make sure to
>> either resolve their JIRAs or push them out of 1.1.0
>>
>> 3. on 6/2 I cut a branch for 1.1.0 and we do the
>> usual round of testing/etc for a few weeks culminating
>> in actual release
>>
>> Sounds good?
>>
>> Thanks,
>> Roman (AKA reluctant RM for Giraph 1.1.0)
>>
>
>
Re: Picking up Giraph 1.1.0 release
Posted by Avery Ching <av...@gmail.com>.
Thanks for getting back to this Roman. The schedule sounds great. Let's
get this release cut!
On 5/20/14, 9:26 AM, Roman Shaposhnik wrote:
> Hi!
>
> with apologies for dropping the ball on 1.1.0
> back in March/April I'd like to restart the
> release activities in earnest.
>
> First things first: if you have a JIRA that you'd
> like to see in 1.1.0 that hasn't been marked with
> 1.1.0 as "Fix version" please reply to this thread
> this week.
>
> As it stands today, our official bug count for 1.1.0
> is not bad at all: http://s.apache.org/Jnu
>
> Even better news is that *all* of the ones marked
> for 1.1.0 have 'patch available'. There's stuff to
> review and commit.
>
> So here's what I'd propose we do for the rest of
> this week: lets divvy up the load of reviewing of
> committing the patches. If you guys don't mind,
> I'd like to track this by having reviewers assign the
> issues to themselves.
>
> Here's the schedule:
> 1. by 5/26 we would expect all the JIRAs tagged
> for 1.1.0 have committers assigned to them. Those
> JIRAs that stay unassigned get pushed out of 1.1.0
>
> 2. by 6/2 those assigned to JIRAs make sure to
> either resolve their JIRAs or push them out of 1.1.0
>
> 3. on 6/2 I cut a branch for 1.1.0 and we do the
> usual round of testing/etc for a few weeks culminating
> in actual release
>
> Sounds good?
>
> Thanks,
> Roman (AKA reluctant RM for Giraph 1.1.0)
Re: Picking up Giraph 1.1.0 release
Posted by Lukas Nalezenec <lu...@firma.seznam.cz>.
Hi,
I would like to open one new ticket (patch is ready), I need GIRAPH-886
<https://issues.apache.org/jira/browse/GIRAPH-886> to be included in 1.1.0.
Regards,
Lukas
On 20.5.2014 18:26, Roman Shaposhnik wrote:
> Hi!
>
> with apologies for dropping the ball on 1.1.0
> back in March/April I'd like to restart the
> release activities in earnest.
>
> First things first: if you have a JIRA that you'd
> like to see in 1.1.0 that hasn't been marked with
> 1.1.0 as "Fix version" please reply to this thread
> this week.
>
> As it stands today, our official bug count for 1.1.0
> is not bad at all: http://s.apache.org/Jnu
>
> Even better news is that *all* of the ones marked
> for 1.1.0 have 'patch available'. There's stuff to
> review and commit.
>
> So here's what I'd propose we do for the rest of
> this week: lets divvy up the load of reviewing of
> committing the patches. If you guys don't mind,
> I'd like to track this by having reviewers assign the
> issues to themselves.
>
> Here's the schedule:
> 1. by 5/26 we would expect all the JIRAs tagged
> for 1.1.0 have committers assigned to them. Those
> JIRAs that stay unassigned get pushed out of 1.1.0
>
> 2. by 6/2 those assigned to JIRAs make sure to
> either resolve their JIRAs or push them out of 1.1.0
>
> 3. on 6/2 I cut a branch for 1.1.0 and we do the
> usual round of testing/etc for a few weeks culminating
> in actual release
>
> Sounds good?
>
> Thanks,
> Roman (AKA reluctant RM for Giraph 1.1.0)