trunk, i'd like to test it this afternoon
> Date: Sat, 24 Jan 2009 14:24:14 -0500 > From: goo...@levy.ch > To: hugin-ptx@googlegroups.com > Subject: [hugin-ptx] Re: vigra 1.6.0 patch > > > Thanks, Lukáš! > > Lukáš Jirkovský wrote: > > But I think it will need more testing before even thinking about > > moving it to the trunk, because of extensive usage of vigra in hugin > > so any small regression could cause big problems. > > I'm calling for anyone to test it. > > For those who want to test it in Ubuntu, this is what I did: > > I followed the instructions at > <http://wiki.panotools.org/Hugin_Compiling_Ubuntu> > > after checking Hugin from SVN and before building it: > - downloaded the patch to the same folder as hugin's source > - gunziped it with: gunzip vigra_1.6.0.diff.gz > - patched it with: patch -p1 < vigra_1.6.0.diff > - continued building according to the wiki's instructions. > > While this is not much work, still work it is that can be spared. I > think the right thing to do is to put it in a repository branch. The > question to the team is: which branch? > > Should we branch out a new "vigra1.6" branch and keep trunk for the > stable releases? or should we branch out a 0.8 branch and use trunk for > the bleeding edge? > > Practically, both solutions are equivalent. The only difference is that > trunk is a branch with a policy meaning as it is the natural branch on > which most work is focused. > > The choice will give a policy signal. > > I would be inclined to branch out 0.8 for those who do not want to take > risks and stick with the past, while including Lukáš's patch in trunk. > After all, trunk is meant to be the bleeding edge and a newer, better > vigra is just that. > > If trunks proves to have regressions or other instabilities, we can tag > and release 0.8.0 from the 0.8 branch. If the tests are positive, we can > close the 0.8 branch. > > In both cases there will be a little bit of maintenance work at keeping > changes such as bug fixes in sync. It is more efficient to do it once > in SVN and make life easy for everybody else who will just "svn up"; > than having everybody maitaining their own patched local install. > > so the question is: trunk, or new branch? > > Yuv > > > _________________________________________________________________ Windows Live™: E-mail. Chat. Share. Get more ways to connect. http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_012009 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
