Re: [hugin-ptx] Re: Integration Queue - current status
On Sun 26-Sep-2010 at 10:58 +, Andreas Metzler wrote: Pablo d'Angelo pablo.dangelo at web.de wrote on 2009-09-20: 6. vigra-1.6 (Lukáš): it has been decided to push the changes upstream; wait for vigra-1.7 with the changes; then make Hugin work with [vigra]-1.7. @Lukáš and @Pablo: what does it take to prepare Lukáš' work to go into vigra; and how do we make it available to vigra? I'll make a patch that fits the current vigra development version (They now have an mercurial repository) and submit it to the vigra developers. Vigra 1.7 has been released in April 2010, are hugin's changes already included in this version? I don't think anything has been submitted upstream, this still needs to be done. There are some other libraries that should be removed from Hugin: as far as I can tell ANN and levmar are the same as the resepctive upstream versions. -- Beuno -- 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
[hugin-ptx] Re: Integration Queue - current status
Pablo d'Angelo pablo.dangelo at web.de wrote on 2009-09-20: [...] 6. vigra-1.6 (Lukáš): it has been decided to push the changes upstream; wait for vigra-1.7 with the changes; then make Hugin work with [vigra]-1.7. @Lukáš and @Pablo: what does it take to prepare Lukáš' work to go into vigra; and how do we make it available to vigra? I'll make a patch that fits the current vigra development version (They now have an mercurial repository) and submit it to the vigra developers. [...] Hello, Vigra 1.7 has been released in April 2010, are hugin's changes already included in this version? thanks, cu andreas -- 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
[hugin-ptx] Re: Integration Queue - current status
Hi Yuv 2009/9/20 Yuval Levy goo...@levy.ch: Thanks to everybody who contributed to the [discussion] about the integration queue. I have summarized the [maturity] criteria in the wiki, and the status of the different future changes below. What we need next is to prioritize - make an ordered list of the integration queue. The following is *my* expressed preference. If you have a different preference for the order, please voice it here. This is a collective decision by consensus of the developers, not my call. Silence = consent. The list is not set in stone: a change in the maturity status of a feature in waiting is good reason to review/change the ordered list. 1. control-point [cleaning] (Thomas). Passed all maturity tests and ready for trunk. I've already responded in the other thread. I'd like to see it in 2009.4.0. 2. gsoc_2009_[deghosting] (Lukáš). Passed maturity b-c, being tested for maturity a. 3. autocrop (Gary). Needs some GUI work. Functionality tested to work on Linux (Gary, Bruno, Yuv) 4. gsoc_2009_[layout] (James). Needs some work 5. gsoc_2008_[masking] (Fahim). Needs work. Gerry has contacted Fahim and is now working on it. 6. vigra-1.6 (Lukáš): it has been decided to push the changes upstream; wait for vigra-1.7 with the changes; then make Hugin work with [vigra]-1.7. @Lukáš and @Pablo: what does it take to prepare Lukáš' work to go into vigra; and how do we make it available to vigra? The work in VIGRA is by Pablo. I still think it would be nice to allow loading EXR as RGB (discarding alpha channel). I think that current support only for RGBA is quite limiting. I've not yet have the time to look at the EXR spec and the possibility to write RGBA2RGBAccessor as Pablo suggested. 7. gsoc_2008_feature_[matching] (Onur). Needs a lot of work and is unlikely to get to a higher maturity level before the other changes in the queue. please express your opinions. Yuv [discussion] http://groups.google.com/group/hugin-ptx/browse_thread/thread/2476b7bcac92fa75 [maturity] http://wiki.panotools.org/Development_of_Open_Source_tools#Maturity_Criteria [cleaning] https://sourceforge.net/tracker/?func=detailaid=2862192group_id=77506atid=550443 [deghosting] http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/branches/gsoc2009_deghosting/ [autocrop] http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/branches/autocrop/ [layout] http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/branches/gsoc2009_layout/ [masking] http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/branches/gsoc2008_masking/ [vigra] http://groups.google.com/group/hugin-ptx/msg/f6b40a16ccf40dfd [matching] http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/branches/gsoc2008_feature_matching/ have a nice day, Lukáš --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[hugin-ptx] Re: Integration Queue - current status
Hi Yuv, 6. vigra-1.6 (Lukáš): it has been decided to push the changes upstream; wait for vigra-1.7 with the changes; then make Hugin work with [vigra]-1.7. @Lukáš and @Pablo: what does it take to prepare Lukáš' work to go into vigra; and how do we make it available to vigra? I'll make a patch that fits the current vigra development version (They now have an mercurial repository) and submit it to the vigra developers. ciao Pablo --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[hugin-ptx] Re: Integration Queue - current status
The order seems fine, though obviously it can change as soon as the first one goes in. I think in general if there is nothing major broken in the trunk, and a stable release branch is still going through the beta/rc steps, then this is an indication that something new should go into the trunk. i.e if after adding cpclean, the branch is still not released and the trunk is still ok then we should think about adding deghosting or autocrop. On Sun 20-Sep-2009 at 09:52 -0400, Yuval Levy wrote: 1. control-point [cleaning] (Thomas). Passed all maturity tests and ready for trunk. 2. gsoc_2009_[deghosting] (Lukáš). Passed maturity b-c, being tested for maturity a. 3. autocrop (Gary). Needs some GUI work. Functionality tested to work on Linux (Gary, Bruno, Yuv) 4. gsoc_2009_[layout] (James). Needs some work 5. gsoc_2008_[masking] (Fahim). Needs work. Gerry has contacted Fahim and is now working on it. 6. vigra-1.6 (Lukáš): it has been decided to push the changes upstream; wait for vigra-1.7 with the changes; then make Hugin work with [vigra]-1.7. @Lukáš and @Pablo: what does it take to prepare Lukáš' work to go into vigra; and how do we make it available to vigra? 7. gsoc_2008_feature_[matching] (Onur). Needs a lot of work and is unlikely to get to a higher maturity level before the other changes in the queue. -- Bruno --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[hugin-ptx] Re: Integration Queue - current status
Bruno Postle wrote: I think in general if there is nothing major broken in the trunk, and a stable release branch is still going through the beta/rc steps, then this is an indication that something new should go into the trunk. this is so obvious I have not even thought of it. Shouldn't it be an impossible situation? if nothing major is broken in the trunk, then nothing major should be broken in the release, the RC can be declared final; trunk branched out again for the next release, and then something new can go into the 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 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 -~--~~~~--~~--~--~---
