I can say from the list you have, GIRAPH-260 and GIRAPH-263 are not blockers as far as I can see. Some of the other JIRA issues on the list might be easily resolved one way or the other as well at this point. I think both can safely be resolved at this point (260 can be a "won't fix", and 263 "fixed" as far as i can tell?)
On Mon, Oct 22, 2012 at 4:28 PM, Roman Shaposhnik <[email protected]> wrote: > Hi! > > As was discussed on GIRAPH-285 it seems to be right time > to think about the release. It seems like Avery has agreed > to be an official RM and I'm volunteering for an RM sidekick > role ;-) > > My plan is pretty simple: I would like to start with JIRA triaging, > figure out which ones folks consider to be blockers for 0.2 and > then help Avery curate the release branch. I am also volunteering > to test RCs with Hadoop 2.0.2-alpha (as part of the Bigtop 0.5.0) > and also do some limited testing with Hadoop 1.1.0 and CDH3/4 > > If this sounds like a good plan, here's a couple of areas where > help would still be appreciated: > * if you can test RCs with different versions of Hadoop -- please > let me know. In fact, my most rigorous testing (to the extent > it can be called that way) will be focused on Hadoop 2.0.2-alpha > > * JIRA triage -- we've got 17 issues tagged with 0.2 > http://s.apache.org/qH > and 22 issues that are assigned to folks, but not to the > 0.2 release: > http://s.apache.org/zE > If you are an issue owner please let me know whether yours > could be considered a blocker for 0.2 > > Thanks, > Roman. >
