Hi Dale,

Dale Beams wrote:
> I'm a little confused on what's going on with the Hugin section.
 > Looking at the directory there is hugin-2009.07.1 and also
 > hugin-2009.02.0_beta2 amongst others.

apology for the confusion. Hugin has been recently in transition. Ignore 
2009.07. The next release is 2009.2.0 (no leading 0 in front of the 2).

previously there was one single branch: trunk. Since some of the things 
happening there are inherently incompatible (notably development and 
release) we had to "time share". Sometimes trunk was used for 
development (adding new features); other times it was frozen and used to 
produce a release (fix bugs, translate, package and distribute).

this has changed. trunk is now the directory for development. releases 
are made separately inside the releases directory.


 >  Does Hugin have a svn directory "testing"
 > that mirros the current activity on the latest branch?

there is no "latest branch". we are moving forward in parallel. There 
are a few development branches, each of them in its own right the 
"latest". there is trunk, which is the main development branch. and 
release branches are branched out of trunk whenever we do a release.

so the question is: what do you mean by "testing"?

if you want to help test/bug fix the current release, the branch is the 
latest one in 
<http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/releases/> - you 
will recognize it by the higher version number.

if you want to play with the totally unsupported bleeding edge, the 
branch is trunk.

Yuv

--~--~---------~--~----~------------~-------~--~----~
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 [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

Reply via email to