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
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
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
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
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
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
