What does it take to make this happen in the next 'buntu release (Natty, if I am not mistaken)? I am volunteering if somebody can guide/mentor me.
We (the Hugin project) have also released Hugin-2010.2.0 recently and plan to release Hugin-2010.4.0 around the end of the year.
When is the cutoff to make it into Natty?
Hugin 2010.2.0 and later depends on the latest release of libpano13 (2.9.17).
Hugin-2010.4.0 represents a milestone because it is the first time that Hugin will ship with a full feature set. We are replacing our dependency on autopano-sift-C (encumbered by the SIFT patent in some jurisdictions) with a completely Free control point generator, thanks to Google Summer of Code sponsorships and a lively contributors community.
For the past two years we've been consistently releasing 2-3 times per year and there is more in the pipeline - every Google Summer of Code participation results in approximately 3 releases. Each release brings new and relevant features / significant changes from the previous ones. I'd like to contribute to make the 'buntu distributed packages of Hugin/Libpano/Enblend equally relevant and dynamic.
There is a 2.5.1 final https:/ /launchpad. net/~hugin/ +archive/ hugin-builds/ +packages
What does it take to make this happen in the next 'buntu release (Natty, if I am not mistaken)? I am volunteering if somebody can guide/mentor me.
We (the Hugin project) have also released Hugin-2010.2.0 recently and plan to release Hugin-2010.4.0 around the end of the year.
When is the cutoff to make it into Natty?
Hugin 2010.2.0 and later depends on the latest release of libpano13 (2.9.17).
Hugin-2010.4.0 represents a milestone because it is the first time that Hugin will ship with a full feature set. We are replacing our dependency on autopano-sift-C (encumbered by the SIFT patent in some jurisdictions) with a completely Free control point generator, thanks to Google Summer of Code sponsorships and a lively contributors community.
For the past two years we've been consistently releasing 2-3 times per year and there is more in the pipeline - every Google Summer of Code participation results in approximately 3 releases. Each release brings new and relevant features / significant changes from the previous ones. I'd like to contribute to make the 'buntu distributed packages of Hugin/Libpano/ Enblend equally relevant and dynamic.
Thank you for your help
Yuv