You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by Avery Ching <ac...@apache.org> on 2013/04/16 07:36:06 UTC
[VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0.
Roman, this is a source code release, we can't really deploy jars to
maven since we use munge to support different versions of Hadoop. Once
we get rid of munge, we'll be able to do this in the future.
Release notes:
http://people.apache.org/~aching/giraph-1.0.0-RC3/RELEASE_NOTES.html
Release artifacts:
http://people.apache.org/~aching/giraph-1.0.0-RC3/
Corresponding git tag:
https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC3
Signing keys:
http://people.apache.org/keys/group/giraph.asc
The vote runs for 72 hours, until Thusday 4pm PST.
Thanks for everyone's input!
Avery
On 4/14/13 7:12 PM, Avery Ching wrote:
> Hopefully last RC release. This patch includes GIRAPH-630. I also
> changed the version number to be 1.0.0 so our next release can be 1.0.1.
>
> Release notes:
> http://people.apache.org/~aching/giraph-1.0.0-RC2/RELEASE_NOTES.html
>
> Release artifacts:
> http://people.apache.org/~aching/giraph-1.0.0-RC2/
>
> Corresponding git tag:
> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC2
>
>
> Signing keys:
> http://people.apache.org/keys/group/giraph.asc
>
> The vote runs for 72 hours, until Wednesday 7:15pm PST.
>
> Thanks,
>
> Avery
>
> On 4/12/13 10:39 PM, Avery Ching wrote:
>> Thanks to the quick feedback from Roman and Lewis, we have cut a new
>> RC1 that addresses the following issues.
>>
>> * Got rid of .git repo in tarball
>> * Fixed issue with not compiling without git repo (GIRAPH-628)
>> * Used gnutar in OSX rather than tar to generate the tarball and get
>> rid of warnings
>> * Pushed GIRAPH-627 to support the yarn profile better
>> * Tarball name changed to the final artifact name (giraph-1.0.tar.gz)
>>
>> Release notes:
>> http://people.apache.org/~aching/giraph-1.0-RC1/RELEASE_NOTES.html
>>
>> Release artifacts:
>> http://people.apache.org/~aching/giraph-1.0-RC1/
>>
>> Corresponding git tag:
>> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0-RC1
>>
>>
>> Signing keys:
>> http://people.apache.org/keys/group/giraph.asc
>>
>> The vote runs for 72 hours, until Monday 11pm PST.
>>
>> Thanks,
>>
>> Avery
>>
>> Original message below regarding rc0:
>>
>> -------------------------------
>>
>> Fellow Giraphers,
>>
>> We have a our first release candidate since graduating from
>> incubation. This is a source release, primarily due to the different
>> versions of Hadoop we support with munge (similar to the 0.1
>> release). Since 0.1, we've made A TON of progress on overall
>> performance, optimizing memory use, split vertex/edge inputs, easy
>> interoperability with Apache Hive, and a bunch of other areas. In
>> many ways, this is an almost totally different codebase. Thanks
>> everyone for your hard work!
>>
>> Apache Giraph has been running in production at Facebook (against
>> Facebook's Corona implementation of Hadoop -
>> https://github.com/facebook/hadoop-20/tree/master/src/contrib/corona)
>> since around last December. It has proven to be very scalable,
>> performant, and enables a bunch of new applications. Based on the
>> drastic improvements and the use of Giraph in production, it seems
>> appropriate to bump up our version to 1.0.
>>
>> While anyone can vote, the ASF requires majority approval from the
>> PMC -- i.e., at least three PMC members must vote affirmatively for
>> release, and there must be more positive than negative votes.
>> Releases may not be vetoed. Before voting +1 PMC members are required
>> to download the signed source code package, compile it as provided,
>> and test the resulting executable on their own platform, along with
>> also verifying that the package meets the requirements of the ASF
>> policy on releases.
>>
>> Please test this against many other Hadoop versions and let us know
>> how this goes!
>>
>> Release notes:
>> http://people.apache.org/~aching/giraph-1.0-RC0/RELEASE_NOTES.html
>>
>> Release artifacts:
>> http://people.apache.org/~aching/giraph-1.0-RC0/
>>
>> Corresponding git tag:
>> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0-RC0
>>
>>
>> Signing keys:
>> http://people.apache.org/keys/group/giraph.asc
>>
>> The vote runs for 72 hours, until Monday 4pm PST.
>>
>> Thanks everyone for your patience with this release!
>>
>> Avery
>
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Eli Reisman <ap...@gmail.com>.
My instinct is to immediately say yes but I don't think I should commit to
that right now. I would be happy to be part of the discussion as to ideas,
proposed methods to replace/remove it. But mentoring might spread me too
thin this summer, as you know ;)
On Sun, Apr 21, 2013 at 2:44 PM, Claudio Martella <
claudio.martella@gmail.com> wrote:
> Also, just to make sure we're on the same page on the munge topic and GSoC,
> I started the bureaucracy for the project, but I won't be able to mentor
> also that project. I plan to mentor the tinkerpop project, in case we get a
> student. In case we get students for both projects, somebody would step in
> for the munge one?
>
>
> On Sun, Apr 21, 2013 at 3:06 AM, Claudio Martella <
> claudio.martella@gmail.com> wrote:
>
> > I am afraid we're not going to get students this round. We really moved
> at
> > the last minute. On this topic, I sent a couple of emails to master
> > students mailing lists to a couple of universities, but if you guys could
> > also forward some recruiting emails to whom you think would be suitable,
> it
> > would probably help. Maybe also Sebastian can help here at TU Berlin?
> >
> >
> > On Sun, Apr 21, 2013 at 2:55 AM, Eli Reisman <apache.mailbox@gmail.com
> >wrote:
> >
> >> Thats a good point. It would represent a temporary solution. I'd like to
> >> see us done with munge for all sorts of reasons if its possible. Might
> be
> >> a
> >> difficult student project to complete cleanly though. Any other thoughts
> >> on
> >> this?
> >>
> >>
> >>
> >> On Sat, Apr 20, 2013 at 3:08 PM, Nitay Joffe <ni...@apache.org> wrote:
> >>
> >> > Just FYI our use of munge does not prevent us from doing binary jar
> >> > release. We can use classifier to release multiple Giraph jars (each
> >> built
> >> > for different Hadoop).
> >> >
> >> > See e.g.
> >> >
> >> >
> >>
> http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
> >> >
> >> >
> >>
> http://stackoverflow.com/questions/3092085/building-same-project-in-maven-with-different-artifactid-based-on-jdk-used
> >> >
> >> > So we would have like giraph-1.0.0-hadoop-0.20.203.0.jar,
> >> > giraph-1.0.0-hadoop-2.0.0.jar, etc
> >> >
> >> > Seems to me like we don't know how long it will take to get rid of
> >> munge.
> >> > Perhaps we should do this as pulling in Giraph into Maven projects
> would
> >> > make it a lot easier for others to work with and lessen the barrier to
> >> > entry?
> >> >
> >> > - Nitay
> >> >
> >> > On Apr 16, 2013, at 1:36 AM, Avery Ching <ac...@apache.org> wrote:
> >> >
> >> > > Okay, we're on our 3rd RC now, mainly to incorporate Roman's
> >> suggestion
> >> > about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0.
> Roman,
> >> > this is a source code release, we can't really deploy jars to maven
> >> since
> >> > we use munge to support different versions of Hadoop. Once we get rid
> >> of
> >> > munge, we'll be able to do this in the future.
> >> > >
> >> > > Release notes:
> >> > >
> http://people.apache.org/~aching/giraph-1.0.0-RC3/RELEASE_NOTES.html
> >> > >
> >> > > Release artifacts:
> >> > > http://people.apache.org/~aching/giraph-1.0.0-RC3/
> >> > >
> >> > > Corresponding git tag:
> >> > >
> >> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC3
> >> > >
> >> > > Signing keys:
> >> > > http://people.apache.org/keys/group/giraph.asc
> >> > >
> >> > > The vote runs for 72 hours, until Thusday 4pm PST.
> >> > >
> >> > > Thanks for everyone's input!
> >> > >
> >> > > Avery
> >> >
> >> >
> >>
> >
> >
> >
> > --
> > Claudio Martella
> > claudio.martella@gmail.com
> >
>
>
>
> --
> Claudio Martella
> claudio.martella@gmail.com
>
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Claudio Martella <cl...@gmail.com>.
Also, just to make sure we're on the same page on the munge topic and GSoC,
I started the bureaucracy for the project, but I won't be able to mentor
also that project. I plan to mentor the tinkerpop project, in case we get a
student. In case we get students for both projects, somebody would step in
for the munge one?
On Sun, Apr 21, 2013 at 3:06 AM, Claudio Martella <
claudio.martella@gmail.com> wrote:
> I am afraid we're not going to get students this round. We really moved at
> the last minute. On this topic, I sent a couple of emails to master
> students mailing lists to a couple of universities, but if you guys could
> also forward some recruiting emails to whom you think would be suitable, it
> would probably help. Maybe also Sebastian can help here at TU Berlin?
>
>
> On Sun, Apr 21, 2013 at 2:55 AM, Eli Reisman <ap...@gmail.com>wrote:
>
>> Thats a good point. It would represent a temporary solution. I'd like to
>> see us done with munge for all sorts of reasons if its possible. Might be
>> a
>> difficult student project to complete cleanly though. Any other thoughts
>> on
>> this?
>>
>>
>>
>> On Sat, Apr 20, 2013 at 3:08 PM, Nitay Joffe <ni...@apache.org> wrote:
>>
>> > Just FYI our use of munge does not prevent us from doing binary jar
>> > release. We can use classifier to release multiple Giraph jars (each
>> built
>> > for different Hadoop).
>> >
>> > See e.g.
>> >
>> >
>> http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
>> >
>> >
>> http://stackoverflow.com/questions/3092085/building-same-project-in-maven-with-different-artifactid-based-on-jdk-used
>> >
>> > So we would have like giraph-1.0.0-hadoop-0.20.203.0.jar,
>> > giraph-1.0.0-hadoop-2.0.0.jar, etc
>> >
>> > Seems to me like we don't know how long it will take to get rid of
>> munge.
>> > Perhaps we should do this as pulling in Giraph into Maven projects would
>> > make it a lot easier for others to work with and lessen the barrier to
>> > entry?
>> >
>> > - Nitay
>> >
>> > On Apr 16, 2013, at 1:36 AM, Avery Ching <ac...@apache.org> wrote:
>> >
>> > > Okay, we're on our 3rd RC now, mainly to incorporate Roman's
>> suggestion
>> > about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman,
>> > this is a source code release, we can't really deploy jars to maven
>> since
>> > we use munge to support different versions of Hadoop. Once we get rid
>> of
>> > munge, we'll be able to do this in the future.
>> > >
>> > > Release notes:
>> > > http://people.apache.org/~aching/giraph-1.0.0-RC3/RELEASE_NOTES.html
>> > >
>> > > Release artifacts:
>> > > http://people.apache.org/~aching/giraph-1.0.0-RC3/
>> > >
>> > > Corresponding git tag:
>> > >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC3
>> > >
>> > > Signing keys:
>> > > http://people.apache.org/keys/group/giraph.asc
>> > >
>> > > The vote runs for 72 hours, until Thusday 4pm PST.
>> > >
>> > > Thanks for everyone's input!
>> > >
>> > > Avery
>> >
>> >
>>
>
>
>
> --
> Claudio Martella
> claudio.martella@gmail.com
>
--
Claudio Martella
claudio.martella@gmail.com
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Claudio Martella <cl...@gmail.com>.
I am afraid we're not going to get students this round. We really moved at
the last minute. On this topic, I sent a couple of emails to master
students mailing lists to a couple of universities, but if you guys could
also forward some recruiting emails to whom you think would be suitable, it
would probably help. Maybe also Sebastian can help here at TU Berlin?
On Sun, Apr 21, 2013 at 2:55 AM, Eli Reisman <ap...@gmail.com>wrote:
> Thats a good point. It would represent a temporary solution. I'd like to
> see us done with munge for all sorts of reasons if its possible. Might be a
> difficult student project to complete cleanly though. Any other thoughts on
> this?
>
>
>
> On Sat, Apr 20, 2013 at 3:08 PM, Nitay Joffe <ni...@apache.org> wrote:
>
> > Just FYI our use of munge does not prevent us from doing binary jar
> > release. We can use classifier to release multiple Giraph jars (each
> built
> > for different Hadoop).
> >
> > See e.g.
> >
> >
> http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
> >
> >
> http://stackoverflow.com/questions/3092085/building-same-project-in-maven-with-different-artifactid-based-on-jdk-used
> >
> > So we would have like giraph-1.0.0-hadoop-0.20.203.0.jar,
> > giraph-1.0.0-hadoop-2.0.0.jar, etc
> >
> > Seems to me like we don't know how long it will take to get rid of munge.
> > Perhaps we should do this as pulling in Giraph into Maven projects would
> > make it a lot easier for others to work with and lessen the barrier to
> > entry?
> >
> > - Nitay
> >
> > On Apr 16, 2013, at 1:36 AM, Avery Ching <ac...@apache.org> wrote:
> >
> > > Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
> > about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman,
> > this is a source code release, we can't really deploy jars to maven since
> > we use munge to support different versions of Hadoop. Once we get rid of
> > munge, we'll be able to do this in the future.
> > >
> > > Release notes:
> > > http://people.apache.org/~aching/giraph-1.0.0-RC3/RELEASE_NOTES.html
> > >
> > > Release artifacts:
> > > http://people.apache.org/~aching/giraph-1.0.0-RC3/
> > >
> > > Corresponding git tag:
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC3
> > >
> > > Signing keys:
> > > http://people.apache.org/keys/group/giraph.asc
> > >
> > > The vote runs for 72 hours, until Thusday 4pm PST.
> > >
> > > Thanks for everyone's input!
> > >
> > > Avery
> >
> >
>
--
Claudio Martella
claudio.martella@gmail.com
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Eli Reisman <ap...@gmail.com>.
Thats a good point. It would represent a temporary solution. I'd like to
see us done with munge for all sorts of reasons if its possible. Might be a
difficult student project to complete cleanly though. Any other thoughts on
this?
On Sat, Apr 20, 2013 at 3:08 PM, Nitay Joffe <ni...@apache.org> wrote:
> Just FYI our use of munge does not prevent us from doing binary jar
> release. We can use classifier to release multiple Giraph jars (each built
> for different Hadoop).
>
> See e.g.
>
> http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
>
> http://stackoverflow.com/questions/3092085/building-same-project-in-maven-with-different-artifactid-based-on-jdk-used
>
> So we would have like giraph-1.0.0-hadoop-0.20.203.0.jar,
> giraph-1.0.0-hadoop-2.0.0.jar, etc
>
> Seems to me like we don't know how long it will take to get rid of munge.
> Perhaps we should do this as pulling in Giraph into Maven projects would
> make it a lot easier for others to work with and lessen the barrier to
> entry?
>
> - Nitay
>
> On Apr 16, 2013, at 1:36 AM, Avery Ching <ac...@apache.org> wrote:
>
> > Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman,
> this is a source code release, we can't really deploy jars to maven since
> we use munge to support different versions of Hadoop. Once we get rid of
> munge, we'll be able to do this in the future.
> >
> > Release notes:
> > http://people.apache.org/~aching/giraph-1.0.0-RC3/RELEASE_NOTES.html
> >
> > Release artifacts:
> > http://people.apache.org/~aching/giraph-1.0.0-RC3/
> >
> > Corresponding git tag:
> >
> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC3
> >
> > Signing keys:
> > http://people.apache.org/keys/group/giraph.asc
> >
> > The vote runs for 72 hours, until Thusday 4pm PST.
> >
> > Thanks for everyone's input!
> >
> > Avery
>
>
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Nitay Joffe <ni...@apache.org>.
Just FYI our use of munge does not prevent us from doing binary jar release. We can use classifier to release multiple Giraph jars (each built for different Hadoop).
See e.g.
http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
http://stackoverflow.com/questions/3092085/building-same-project-in-maven-with-different-artifactid-based-on-jdk-used
So we would have like giraph-1.0.0-hadoop-0.20.203.0.jar, giraph-1.0.0-hadoop-2.0.0.jar, etc
Seems to me like we don't know how long it will take to get rid of munge.
Perhaps we should do this as pulling in Giraph into Maven projects would make it a lot easier for others to work with and lessen the barrier to entry?
- Nitay
On Apr 16, 2013, at 1:36 AM, Avery Ching <ac...@apache.org> wrote:
> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman, this is a source code release, we can't really deploy jars to maven since we use munge to support different versions of Hadoop. Once we get rid of munge, we'll be able to do this in the future.
>
> Release notes:
> http://people.apache.org/~aching/giraph-1.0.0-RC3/RELEASE_NOTES.html
>
> Release artifacts:
> http://people.apache.org/~aching/giraph-1.0.0-RC3/
>
> Corresponding git tag:
> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC3
>
> Signing keys:
> http://people.apache.org/keys/group/giraph.asc
>
> The vote runs for 72 hours, until Thusday 4pm PST.
>
> Thanks for everyone's input!
>
> Avery
Re: [VOTE][RESULT] Release Giraph 1.0.0 (rc3)
Posted by Eli Reisman <ap...@gmail.com>.
Awesome!
On Sat, Apr 20, 2013 at 1:24 AM, Avery Ching <ac...@apache.org> wrote:
> Vote result:
>
> Binding:
> +1 Avery
> +1 Eli
> +1 Claudio
> +1 Sebastian
>
> Non-binding:
> +1 Lewis
> +1 Roman
>
> The vote passes! I will work on getting the tarball out in the open!
>
> Thanks everyone for all your help with this release.
>
> Avery
>
>
> On 4/18/13 9:52 AM, Sebastian Schelter wrote:
>
>> +1 on the release, let's go!
>>
>> On 18.04.2013 18:49, Avery Ching wrote:
>>
>>> Currently the vote on Giraph-1.0.0 (rc3) is
>>>
>>> Binding:
>>> +1 (Avery)
>>> +1 (Eli)
>>>
>>> Non-binding:
>>> +1 (Lewis)
>>> +1 Roman
>>>
>>> We need at least one more PMC +1 to make this release official.
>>> Sebastian? Claudio?
>>>
>>> Deadline is Thursday (today) at 10:30 PM PST.
>>>
>>> Avery
>>>
>>> On 4/17/13 10:00 PM, Roman Shaposhnik wrote:
>>>
>>>> On Mon, Apr 15, 2013 at 10:36 PM, Avery Ching <ac...@apache.org>
>>>> wrote:
>>>>
>>>>> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
>>>>> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0.
>>>>> Roman,
>>>>> this is a source code release, we can't really deploy jars to maven
>>>>> since we
>>>>> use munge to support different versions of Hadoop. Once we get rid of
>>>>> munge, we'll be able to do this in the future.
>>>>>
>>>> Understood.
>>>>
>>>> The vote runs for 72 hours, until Thusday 4pm PST.
>>>>>
>>>>> Thanks for everyone's input!
>>>>>
>>>> +1 (non-binding).
>>>>
>>>> Built packages as part of Bigtop:
>>>> http://bigtop01.cloudera.org:**8080/view/Upstream-tests/job/**
>>>> Giraph-1.0.0/<http://bigtop01.cloudera.org:8080/view/Upstream-tests/job/Giraph-1.0.0/>
>>>> tested on a 4 node fully distributed, secure
>>>> and unsecure Hadoop 2.0.4-alpha cluster.
>>>>
>>>> Thanks,
>>>> Roman.
>>>>
>>>
>
Re: [VOTE][RESULT] Release Giraph 1.0.0 (rc3)
Posted by Avery Ching <ac...@apache.org>.
Vote result:
Binding:
+1 Avery
+1 Eli
+1 Claudio
+1 Sebastian
Non-binding:
+1 Lewis
+1 Roman
The vote passes! I will work on getting the tarball out in the open!
Thanks everyone for all your help with this release.
Avery
On 4/18/13 9:52 AM, Sebastian Schelter wrote:
> +1 on the release, let's go!
>
> On 18.04.2013 18:49, Avery Ching wrote:
>> Currently the vote on Giraph-1.0.0 (rc3) is
>>
>> Binding:
>> +1 (Avery)
>> +1 (Eli)
>>
>> Non-binding:
>> +1 (Lewis)
>> +1 Roman
>>
>> We need at least one more PMC +1 to make this release official.
>> Sebastian? Claudio?
>>
>> Deadline is Thursday (today) at 10:30 PM PST.
>>
>> Avery
>>
>> On 4/17/13 10:00 PM, Roman Shaposhnik wrote:
>>> On Mon, Apr 15, 2013 at 10:36 PM, Avery Ching <ac...@apache.org> wrote:
>>>> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
>>>> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0.
>>>> Roman,
>>>> this is a source code release, we can't really deploy jars to maven
>>>> since we
>>>> use munge to support different versions of Hadoop. Once we get rid of
>>>> munge, we'll be able to do this in the future.
>>> Understood.
>>>
>>>> The vote runs for 72 hours, until Thusday 4pm PST.
>>>>
>>>> Thanks for everyone's input!
>>> +1 (non-binding).
>>>
>>> Built packages as part of Bigtop:
>>>
>>> http://bigtop01.cloudera.org:8080/view/Upstream-tests/job/Giraph-1.0.0/
>>> tested on a 4 node fully distributed, secure
>>> and unsecure Hadoop 2.0.4-alpha cluster.
>>>
>>> Thanks,
>>> Roman.
Re: [VOTE][RESULT] Release Giraph 1.0.0 (rc3)
Posted by Avery Ching <ac...@apache.org>.
Vote result:
Binding:
+1 Avery
+1 Eli
+1 Claudio
+1 Sebastian
Non-binding:
+1 Lewis
+1 Roman
The vote passes! I will work on getting the tarball out in the open!
Thanks everyone for all your help with this release.
Avery
On 4/18/13 9:52 AM, Sebastian Schelter wrote:
> +1 on the release, let's go!
>
> On 18.04.2013 18:49, Avery Ching wrote:
>> Currently the vote on Giraph-1.0.0 (rc3) is
>>
>> Binding:
>> +1 (Avery)
>> +1 (Eli)
>>
>> Non-binding:
>> +1 (Lewis)
>> +1 Roman
>>
>> We need at least one more PMC +1 to make this release official.
>> Sebastian? Claudio?
>>
>> Deadline is Thursday (today) at 10:30 PM PST.
>>
>> Avery
>>
>> On 4/17/13 10:00 PM, Roman Shaposhnik wrote:
>>> On Mon, Apr 15, 2013 at 10:36 PM, Avery Ching <ac...@apache.org> wrote:
>>>> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
>>>> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0.
>>>> Roman,
>>>> this is a source code release, we can't really deploy jars to maven
>>>> since we
>>>> use munge to support different versions of Hadoop. Once we get rid of
>>>> munge, we'll be able to do this in the future.
>>> Understood.
>>>
>>>> The vote runs for 72 hours, until Thusday 4pm PST.
>>>>
>>>> Thanks for everyone's input!
>>> +1 (non-binding).
>>>
>>> Built packages as part of Bigtop:
>>>
>>> http://bigtop01.cloudera.org:8080/view/Upstream-tests/job/Giraph-1.0.0/
>>> tested on a 4 node fully distributed, secure
>>> and unsecure Hadoop 2.0.4-alpha cluster.
>>>
>>> Thanks,
>>> Roman.
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Sebastian Schelter <ss...@apache.org>.
+1 on the release, let's go!
On 18.04.2013 18:49, Avery Ching wrote:
> Currently the vote on Giraph-1.0.0 (rc3) is
>
> Binding:
> +1 (Avery)
> +1 (Eli)
>
> Non-binding:
> +1 (Lewis)
> +1 Roman
>
> We need at least one more PMC +1 to make this release official.
> Sebastian? Claudio?
>
> Deadline is Thursday (today) at 10:30 PM PST.
>
> Avery
>
> On 4/17/13 10:00 PM, Roman Shaposhnik wrote:
>> On Mon, Apr 15, 2013 at 10:36 PM, Avery Ching <ac...@apache.org> wrote:
>>> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
>>> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0.
>>> Roman,
>>> this is a source code release, we can't really deploy jars to maven
>>> since we
>>> use munge to support different versions of Hadoop. Once we get rid of
>>> munge, we'll be able to do this in the future.
>> Understood.
>>
>>> The vote runs for 72 hours, until Thusday 4pm PST.
>>>
>>> Thanks for everyone's input!
>> +1 (non-binding).
>>
>> Built packages as part of Bigtop:
>>
>> http://bigtop01.cloudera.org:8080/view/Upstream-tests/job/Giraph-1.0.0/
>> tested on a 4 node fully distributed, secure
>> and unsecure Hadoop 2.0.4-alpha cluster.
>>
>> Thanks,
>> Roman.
>
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Claudio Martella <cl...@gmail.com>.
I just tested it on our small cluster and it builds cleanly.
+1.
On Thu, Apr 18, 2013 at 6:49 PM, Avery Ching <ac...@apache.org> wrote:
> Currently the vote on Giraph-1.0.0 (rc3) is
>
> Binding:
> +1 (Avery)
> +1 (Eli)
>
> Non-binding:
> +1 (Lewis)
> +1 Roman
>
> We need at least one more PMC +1 to make this release official. Sebastian?
> Claudio?
>
> Deadline is Thursday (today) at 10:30 PM PST.
>
> Avery
>
>
> On 4/17/13 10:00 PM, Roman Shaposhnik wrote:
>
>> On Mon, Apr 15, 2013 at 10:36 PM, Avery Ching <ac...@apache.org> wrote:
>>
>>> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
>>> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman,
>>> this is a source code release, we can't really deploy jars to maven
>>> since we
>>> use munge to support different versions of Hadoop. Once we get rid of
>>> munge, we'll be able to do this in the future.
>>>
>> Understood.
>>
>> The vote runs for 72 hours, until Thusday 4pm PST.
>>>
>>> Thanks for everyone's input!
>>>
>> +1 (non-binding).
>>
>> Built packages as part of Bigtop:
>> http://bigtop01.cloudera.org:**8080/view/Upstream-tests/job/**
>> Giraph-1.0.0/<http://bigtop01.cloudera.org:8080/view/Upstream-tests/job/Giraph-1.0.0/>
>> tested on a 4 node fully distributed, secure
>> and unsecure Hadoop 2.0.4-alpha cluster.
>>
>> Thanks,
>> Roman.
>>
>
>
--
Claudio Martella
claudio.martella@gmail.com
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Avery Ching <ac...@apache.org>.
Currently the vote on Giraph-1.0.0 (rc3) is
Binding:
+1 (Avery)
+1 (Eli)
Non-binding:
+1 (Lewis)
+1 Roman
We need at least one more PMC +1 to make this release official.
Sebastian? Claudio?
Deadline is Thursday (today) at 10:30 PM PST.
Avery
On 4/17/13 10:00 PM, Roman Shaposhnik wrote:
> On Mon, Apr 15, 2013 at 10:36 PM, Avery Ching <ac...@apache.org> wrote:
>> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
>> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman,
>> this is a source code release, we can't really deploy jars to maven since we
>> use munge to support different versions of Hadoop. Once we get rid of
>> munge, we'll be able to do this in the future.
> Understood.
>
>> The vote runs for 72 hours, until Thusday 4pm PST.
>>
>> Thanks for everyone's input!
> +1 (non-binding).
>
> Built packages as part of Bigtop:
> http://bigtop01.cloudera.org:8080/view/Upstream-tests/job/Giraph-1.0.0/
> tested on a 4 node fully distributed, secure
> and unsecure Hadoop 2.0.4-alpha cluster.
>
> Thanks,
> Roman.
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Avery Ching <ac...@apache.org>.
Currently the vote on Giraph-1.0.0 (rc3) is
Binding:
+1 (Avery)
+1 (Eli)
Non-binding:
+1 (Lewis)
+1 Roman
We need at least one more PMC +1 to make this release official.
Sebastian? Claudio?
Deadline is Thursday (today) at 10:30 PM PST.
Avery
On 4/17/13 10:00 PM, Roman Shaposhnik wrote:
> On Mon, Apr 15, 2013 at 10:36 PM, Avery Ching <ac...@apache.org> wrote:
>> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
>> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman,
>> this is a source code release, we can't really deploy jars to maven since we
>> use munge to support different versions of Hadoop. Once we get rid of
>> munge, we'll be able to do this in the future.
> Understood.
>
>> The vote runs for 72 hours, until Thusday 4pm PST.
>>
>> Thanks for everyone's input!
> +1 (non-binding).
>
> Built packages as part of Bigtop:
> http://bigtop01.cloudera.org:8080/view/Upstream-tests/job/Giraph-1.0.0/
> tested on a 4 node fully distributed, secure
> and unsecure Hadoop 2.0.4-alpha cluster.
>
> Thanks,
> Roman.
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Roman Shaposhnik <rv...@apache.org>.
On Mon, Apr 15, 2013 at 10:36 PM, Avery Ching <ac...@apache.org> wrote:
> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman,
> this is a source code release, we can't really deploy jars to maven since we
> use munge to support different versions of Hadoop. Once we get rid of
> munge, we'll be able to do this in the future.
Understood.
> The vote runs for 72 hours, until Thusday 4pm PST.
>
> Thanks for everyone's input!
+1 (non-binding).
Built packages as part of Bigtop:
http://bigtop01.cloudera.org:8080/view/Upstream-tests/job/Giraph-1.0.0/
tested on a 4 node fully distributed, secure
and unsecure Hadoop 2.0.4-alpha cluster.
Thanks,
Roman.
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Roman Shaposhnik <rv...@apache.org>.
On Mon, Apr 15, 2013 at 10:36 PM, Avery Ching <ac...@apache.org> wrote:
> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman,
> this is a source code release, we can't really deploy jars to maven since we
> use munge to support different versions of Hadoop. Once we get rid of
> munge, we'll be able to do this in the future.
Understood.
> The vote runs for 72 hours, until Thusday 4pm PST.
>
> Thanks for everyone's input!
+1 (non-binding).
Built packages as part of Bigtop:
http://bigtop01.cloudera.org:8080/view/Upstream-tests/job/Giraph-1.0.0/
tested on a 4 node fully distributed, secure
and unsecure Hadoop 2.0.4-alpha cluster.
Thanks,
Roman.
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Nitay Joffe <ni...@gmail.com>.
Just FYI we munge does not prevent us from doing jar release. We can use classifier to release multiple Giraph jars (each built for different Hadoop).
See e.g.
http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
http://stackoverflow.com/questions/3092085/building-same-project-in-maven-with-different-artifactid-based-on-jdk-used
So we would have like giraph-1.0.0-hadoop-0.20.203.0.jar, giraph-1.0.0-hadoop-2.0.0.jar, etc
Seems to me like we don't know how long it will take to get rid of munge.
Perhaps we should do this as pulling in Giraph into Maven projects would make it a lot easier for others to work with and lessen the barrier to entry?
- Nitay
On Apr 16, 2013, at 1:36 AM, Avery Ching <ac...@apache.org> wrote:
> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman, this is a source code release, we can't really deploy jars to maven since we use munge to support different versions of Hadoop. Once we get rid of munge, we'll be able to do this in the future.
>
> Release notes:
> http://people.apache.org/~aching/giraph-1.0.0-RC3/RELEASE_NOTES.html
>
> Release artifacts:
> http://people.apache.org/~aching/giraph-1.0.0-RC3/
>
> Corresponding git tag:
> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC3
>
> Signing keys:
> http://people.apache.org/keys/group/giraph.asc
>
> The vote runs for 72 hours, until Thusday 4pm PST.
>
> Thanks for everyone's input!
>
> Avery
>
> On 4/14/13 7:12 PM, Avery Ching wrote:
>> Hopefully last RC release. This patch includes GIRAPH-630. I also changed the version number to be 1.0.0 so our next release can be 1.0.1.
>>
>> Release notes:
>> http://people.apache.org/~aching/giraph-1.0.0-RC2/RELEASE_NOTES.html
>>
>> Release artifacts:
>> http://people.apache.org/~aching/giraph-1.0.0-RC2/
>>
>> Corresponding git tag:
>> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC2
>>
>> Signing keys:
>> http://people.apache.org/keys/group/giraph.asc
>>
>> The vote runs for 72 hours, until Wednesday 7:15pm PST.
>>
>> Thanks,
>>
>> Avery
>>
>> On 4/12/13 10:39 PM, Avery Ching wrote:
>>> Thanks to the quick feedback from Roman and Lewis, we have cut a new RC1 that addresses the following issues.
>>>
>>> * Got rid of .git repo in tarball
>>> * Fixed issue with not compiling without git repo (GIRAPH-628)
>>> * Used gnutar in OSX rather than tar to generate the tarball and get rid of warnings
>>> * Pushed GIRAPH-627 to support the yarn profile better
>>> * Tarball name changed to the final artifact name (giraph-1.0.tar.gz)
>>>
>>> Release notes:
>>> http://people.apache.org/~aching/giraph-1.0-RC1/RELEASE_NOTES.html
>>>
>>> Release artifacts:
>>> http://people.apache.org/~aching/giraph-1.0-RC1/
>>>
>>> Corresponding git tag:
>>> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0-RC1
>>>
>>> Signing keys:
>>> http://people.apache.org/keys/group/giraph.asc
>>>
>>> The vote runs for 72 hours, until Monday 11pm PST.
>>>
>>> Thanks,
>>>
>>> Avery
>>>
>>> Original message below regarding rc0:
>>>
>>> -------------------------------
>>>
>>> Fellow Giraphers,
>>>
>>> We have a our first release candidate since graduating from incubation. This is a source release, primarily due to the different versions of Hadoop we support with munge (similar to the 0.1 release). Since 0.1, we've made A TON of progress on overall performance, optimizing memory use, split vertex/edge inputs, easy interoperability with Apache Hive, and a bunch of other areas. In many ways, this is an almost totally different codebase. Thanks everyone for your hard work!
>>>
>>> Apache Giraph has been running in production at Facebook (against Facebook's Corona implementation of Hadoop - https://github.com/facebook/hadoop-20/tree/master/src/contrib/corona) since around last December. It has proven to be very scalable, performant, and enables a bunch of new applications. Based on the drastic improvements and the use of Giraph in production, it seems appropriate to bump up our version to 1.0.
>>>
>>> While anyone can vote, the ASF requires majority approval from the PMC -- i.e., at least three PMC members must vote affirmatively for release, and there must be more positive than negative votes. Releases may not be vetoed. Before voting +1 PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases.
>>>
>>> Please test this against many other Hadoop versions and let us know how this goes!
>>>
>>> Release notes:
>>> http://people.apache.org/~aching/giraph-1.0-RC0/RELEASE_NOTES.html
>>>
>>> Release artifacts:
>>> http://people.apache.org/~aching/giraph-1.0-RC0/
>>>
>>> Corresponding git tag:
>>> https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0-RC0
>>>
>>> Signing keys:
>>> http://people.apache.org/keys/group/giraph.asc
>>>
>>> The vote runs for 72 hours, until Monday 4pm PST.
>>>
>>> Thanks everyone for your patience with this release!
>>>
>>> Avery
>>
>
Re: [VOTE][CHANGED] Release Giraph 1.0.0 (rc3)
Posted by Eli Reisman <ap...@gmail.com>.
+1
On Tue, Apr 16, 2013 at 1:36 AM, Avery Ching <ac...@apache.org> wrote:
> Okay, we're on our 3rd RC now, mainly to incorporate Roman's suggestion
> about fixing the maven version number from 0.2-SNAPSHOT => 1.0.0. Roman,
> this is a source code release, we can't really deploy jars to maven since
> we use munge to support different versions of Hadoop. Once we get rid of
> munge, we'll be able to do this in the future.
>
> Release notes:
> http://people.apache.org/~**aching/giraph-1.0.0-RC3/**RELEASE_NOTES.html<http://people.apache.org/~aching/giraph-1.0.0-RC3/RELEASE_NOTES.html>
>
> Release artifacts:
> http://people.apache.org/~**aching/giraph-1.0.0-RC3/<http://people.apache.org/~aching/giraph-1.0.0-RC3/>
>
> Corresponding git tag:
> https://git-wip-us.apache.org/**repos/asf?p=giraph.git;a=**
> shortlog;h=refs/tags/release-**1.0.0-RC3<https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC3>
>
> Signing keys:
> http://people.apache.org/keys/**group/giraph.asc<http://people.apache.org/keys/group/giraph.asc>
>
> The vote runs for 72 hours, until Thusday 4pm PST.
>
> Thanks for everyone's input!
>
> Avery
>
> On 4/14/13 7:12 PM, Avery Ching wrote:
>
>> Hopefully last RC release. This patch includes GIRAPH-630. I also
>> changed the version number to be 1.0.0 so our next release can be 1.0.1.
>>
>> Release notes:
>> http://people.apache.org/~**aching/giraph-1.0.0-RC2/**RELEASE_NOTES.html<http://people.apache.org/~aching/giraph-1.0.0-RC2/RELEASE_NOTES.html>
>>
>> Release artifacts:
>> http://people.apache.org/~**aching/giraph-1.0.0-RC2/<http://people.apache.org/~aching/giraph-1.0.0-RC2/>
>>
>> Corresponding git tag:
>> https://git-wip-us.apache.org/**repos/asf?p=giraph.git;a=**
>> shortlog;h=refs/tags/release-**1.0.0-RC2<https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0.0-RC2>
>>
>> Signing keys:
>> http://people.apache.org/keys/**group/giraph.asc<http://people.apache.org/keys/group/giraph.asc>
>>
>> The vote runs for 72 hours, until Wednesday 7:15pm PST.
>>
>> Thanks,
>>
>> Avery
>>
>> On 4/12/13 10:39 PM, Avery Ching wrote:
>>
>>> Thanks to the quick feedback from Roman and Lewis, we have cut a new RC1
>>> that addresses the following issues.
>>>
>>> * Got rid of .git repo in tarball
>>> * Fixed issue with not compiling without git repo (GIRAPH-628)
>>> * Used gnutar in OSX rather than tar to generate the tarball and get rid
>>> of warnings
>>> * Pushed GIRAPH-627 to support the yarn profile better
>>> * Tarball name changed to the final artifact name (giraph-1.0.tar.gz)
>>>
>>> Release notes:
>>> http://people.apache.org/~**aching/giraph-1.0-RC1/RELEASE_**NOTES.html<http://people.apache.org/~aching/giraph-1.0-RC1/RELEASE_NOTES.html>
>>>
>>> Release artifacts:
>>> http://people.apache.org/~**aching/giraph-1.0-RC1/<http://people.apache.org/~aching/giraph-1.0-RC1/>
>>>
>>> Corresponding git tag:
>>> https://git-wip-us.apache.org/**repos/asf?p=giraph.git;a=**
>>> shortlog;h=refs/tags/release-**1.0-RC1<https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0-RC1>
>>>
>>> Signing keys:
>>> http://people.apache.org/keys/**group/giraph.asc<http://people.apache.org/keys/group/giraph.asc>
>>>
>>> The vote runs for 72 hours, until Monday 11pm PST.
>>>
>>> Thanks,
>>>
>>> Avery
>>>
>>> Original message below regarding rc0:
>>>
>>> ------------------------------**-
>>>
>>> Fellow Giraphers,
>>>
>>> We have a our first release candidate since graduating from incubation.
>>> This is a source release, primarily due to the different versions of
>>> Hadoop we support with munge (similar to the 0.1 release). Since 0.1,
>>> we've made A TON of progress on overall performance, optimizing memory use,
>>> split vertex/edge inputs, easy interoperability with Apache Hive, and a
>>> bunch of other areas. In many ways, this is an almost totally different
>>> codebase. Thanks everyone for your hard work!
>>>
>>> Apache Giraph has been running in production at Facebook (against
>>> Facebook's Corona implementation of Hadoop -
>>> https://github.com/facebook/**hadoop-20/tree/master/src/**contrib/corona<https://github.com/facebook/hadoop-20/tree/master/src/contrib/corona>)
>>> since around last December. It has proven to be very scalable, performant,
>>> and enables a bunch of new applications. Based on the drastic improvements
>>> and the use of Giraph in production, it seems appropriate to bump up our
>>> version to 1.0.
>>>
>>> While anyone can vote, the ASF requires majority approval from the PMC
>>> -- i.e., at least three PMC members must vote affirmatively for release,
>>> and there must be more positive than negative votes. Releases may not be
>>> vetoed. Before voting +1 PMC members are required to download the signed
>>> source code package, compile it as provided, and test the resulting
>>> executable on their own platform, along with also verifying that the
>>> package meets the requirements of the ASF policy on releases.
>>>
>>> Please test this against many other Hadoop versions and let us know how
>>> this goes!
>>>
>>> Release notes:
>>> http://people.apache.org/~**aching/giraph-1.0-RC0/RELEASE_**NOTES.html<http://people.apache.org/~aching/giraph-1.0-RC0/RELEASE_NOTES.html>
>>>
>>> Release artifacts:
>>> http://people.apache.org/~**aching/giraph-1.0-RC0/<http://people.apache.org/~aching/giraph-1.0-RC0/>
>>>
>>> Corresponding git tag:
>>> https://git-wip-us.apache.org/**repos/asf?p=giraph.git;a=**
>>> shortlog;h=refs/tags/release-**1.0-RC0<https://git-wip-us.apache.org/repos/asf?p=giraph.git;a=shortlog;h=refs/tags/release-1.0-RC0>
>>>
>>> Signing keys:
>>> http://people.apache.org/keys/**group/giraph.asc<http://people.apache.org/keys/group/giraph.asc>
>>>
>>> The vote runs for 72 hours, until Monday 4pm PST.
>>>
>>> Thanks everyone for your patience with this release!
>>>
>>> Avery
>>>
>>
>>
>