This is great Lewis! Just quick silly question here mate, is this for all GORA-174 related patches? or is this only for the GORA-174 patch?
Renato M. 2013/3/11 Henry Saputra <[email protected]>: > Thanks for making this happen Lewis. > > - Henry > > > On Sat, Mar 9, 2013 at 9:11 PM, Lewis John Mcgibbney < > [email protected]> wrote: > >> Our build is here >> >> https://builds.apache.org/view/G-L/view/Gora/job/GORA_174/ >> >> Time for (a several beers on the way) home >> >> Later >> >> On Sat, Mar 9, 2013 at 9:05 PM, Lewis John Mcgibbney < >> [email protected]> wrote: >> >> > Hi All, >> > I feel we are struggling somewhat to co-ordinate and address GORA-174. >> > It is by no means an easy issue, and it has flagged up a lot more than I >> > think most of us originally anticipated... >> > Although this is a pain, it is also a major benefit for us as there is >> now >> > motivation to address the issues and make Gora better in the process. >> > The branch of trunk can be found at [0]. >> > As Renato and myself did with the goraamazon branch, I think this will be >> > a case of setting up the build on Jenkins, and plugging away until we get >> > it stable and then we merge it back into trunk. >> > I would ask that ANYONE that makes changes to trunk, also merges the >> > changes into the GORA_174 branch. This means that we keep them both in >> sync >> > and when we eventually come to merging both branches, we can do so in a >> > timely and stress free manner. >> > It is OK for us to commit GORA-174 on the GORA_174 branch, then address >> > the individual failing tests... this is the purpose of this exercise. >> > >> > Thanks all, have a great weekend. >> > >> > Lewis >> > >> > [0] http://svn.apache.org/repos/asf/gora/branches/GORA_174/ >> > >> > -- >> > *Lewis* >> > >> >> >> >> -- >> *Lewis* >>
