Hey Lewis, Sounds great to me dude. So you're saying:
* We need to update our release process before 0.2 based on Simone and Andy's comments - +1 * This will help build community - +1 * Henry and I released before (0.1 and 0.1.1) so (guessing here) you want to make the 0.2 release? - +1 Cheers, Chris On Apr 6, 2012, at 3:53 AM, Lewis John Mcgibbney wrote: > Hi Chris, > > I spoke with Simone Tripodi about automating the Gora build somewhat. I've > not witnessed it personally yet, but AFAIK some projects have it down to > three or so steps (Andy Seaborne also mentioned this regarding the process > for Apache Jena). Maybe it might be worth putting in a bit of time into > bringing the Gora release process up to date... my only justification > behind this is that it will make our release managers life a hellish lot > easier and also means that a release doesn't need to be a huge thing, we > can instead maybe have incremental releases within a 3-6 month time frame > rather than ~6 months... this is also an attempt to build community, by > displaying the project can manage releases and is actively working towards > them. I am very very keen to nail the release process and will put in the > time to do so. > > My guess is that 0.1 release was done similar to Nutch, with respect to > Ant/Ivy and the actual release candidate process. I'm also guessing that > 0.1.1-incubating was also done in this fashion... I vaguely remember > hearing that previous release managers were Henry and Chris respectively? > Is this correct. > > Does this sound reasonable? > > Thanks > > Lewis > > On Thu, Apr 5, 2012 at 11:14 PM, Mattmann, Chris A (388J) < > [email protected]> wrote: > >> Hey Lewis, >> >> I've got the following this weekend: >> >> Apache SIS 0.2 RC #2 >> Apache Nutch 1.5 RC #2 (and likely Nutchgora 2.0 after Gora) >> >> I can add Gora 0.2 RC to the list unless someone beats me to it >> this weekend, and if folks are +1. >> >> Cheers, >> Chris >> >> >> On Apr 5, 2012, at 12:44 PM, Lewis John Mcgibbney wrote: >> >>> Hi Guys, >>> >>> Since working with Ferdy to upgrade hadoop-core and tests deps, I thought >>> it might be best to raise this conversation again and see if it has any >>> traction. >>> >>> Regarding the remaining issues [0] >>> >>> GORA-76 - We committed this earlier. Tests pass successfully although >> there >>> are many dodgy stack traces in the log output. At first glance this looks >>> horrible, but upon some investigation I found that the HBase guys are >>> having problems of a similar nature [1] [2] which makes me think that we >>> are definitely not alone in this one, possibly bugs further upstream??? >> For >>> the time being, I have no issues here, and also would like to resolve and >>> close. >>> GORA-65 - I am extremely happy with Keith's datastore and pleased to see >> it >>> make its way into the 0.2 release. I have no issues here, and also would >>> like to resolve and close. >>> GORA-63 - I really don't know what's happening with this little gem, but >>> surely it's not a blocker for the release. I agree that it certainly >> should >>> be addressed in the future, but to date I've been unable to get things >>> working with it so can't confirm if it should be committed. If anyone >> else >>> would like to try Enis' patch then please do and try to compile the >>> examples... if they work great. >>> GORA-53 - I had marked this as critical. It has quite literally become >> the >>> thorn in my side of recent. I've made reasonable progress but there is a >>> final missing link which I can't seem to fix. As the community is more >>> HBase oriented, I suggest to bump this to 0.3 development and I will pick >>> it up then. If there are any objections then OK, but I hope I have >>> justified myself on this one. >>> >>> Looking forward to hearing your thoughts and opinions... and also looking >>> towards VOTE'ing on a 0.2 RC :0) >>> >>> Best >>> >>> Lewis >>> >>> [0] >>> >> https://issues.apache.org/jira/browse/GORA/fixforversion/12315541#atl_token=A5KQ-2QAV-T4JA-FDED|674efcd881a26e09b262373d1c2addb1762e06ea|lin&selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel<https://issues.apache.org/jira/browse/GORA/fixforversion/12315541#atl_token=A5KQ-2QAV-T4JA-FDED%7C674efcd881a26e09b262373d1c2addb1762e06ea%7Clin&selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel> >>> [1]https://issues.apache.org/jira/browse/HBASE-4709 >>> [2] https://issues.apache.org/jira/browse/HBASE-5711 >>> >>> -- >>> *Lewis* >> >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: [email protected] >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> > > > -- > *Lewis* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
