Hi Thomas, T. Modes wrote: > I would wait a couple of day. Maybe someone could fix some of the big > problems in nona-gpu (e. g. your incomplete framebuffer problem, or my > padding problem).
I am not sure if the incomplete framebuffer is really a bug in the nona-gpu code; or if it is the result of some combination of hardware, driver, and software. The only way to find out is to release and get a wider set of reports. > I think we should not release a version, where the > first point of the change list has an comment of "reported not to work > in most cases" (see your release notes for beta). IMHO it should work > in some more cases before we release. I disagree with you. I have stated at the beginning of the release cycle what the conditions are for release: - the package builds on the major supported platforms (Ubuntu, Fedora, OSX, Windows) - there is no (unintentional) regression / breakage of functionality. 2009.2.0 ships with GPU-stitching disabled by default. The functionality of nona when GPU-stitching is disable is exactly equal to 0.8.0. No regression, no show stopper. > Also the translation for the release of 2009.2 are behind the stand of > 0.8 How can the translations be behind? all strings that were translated in 0.8 are still translated in 2009.2.0, so there can only be improvements? again: no regression, no show stopper. > We should give the translators some more time, to get a similar > coverage of translation as 0.8 (Currently there are some untranslated > strings in the main interface, which looks not so professional for an > release.) translators can work any time. If the translations are so important, they will come, and we have an option of issuing a patch release (e.g. 2009.2.1). the whole point of this new process is *not* to wait, nor to put pressure on volunteers to deliver. What comes comes, what does not come will come for the next release. waiting is the problem, not "looking unprofessional". nona-gpu has been waiting for too long before trunk was ready for a merge. now lens calibration has just been merged into trunk and is also waiting for a release. after lens calibration there are other major changes that need to be merged and released - one by one: deghosting; new layout; vigra1.6. I don't want get stuck with the problem that we had for 0.8.0: too much stuff was added to trunk before releasing and it has taken so long to fix it for release. trunk is always open for small incremental changes, and if we release frequently, those small incremental changes, including the fixes for 8 pixel padding; framebuffer; translations, etc.) will just be released as they go. Yuv 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 -~----------~----~----~----~------~----~------~--~---
