Bruno Postle <[EMAIL PROTECTED]> (21/07/2008): > That's a problem, you would need to roll hugin back nearly a year to > avoid using these enblend-3.1 features and still have something > reasonably 'stable' - But the hugin 0.7.0 release will be quite a > different thing from hugin as it was last July.
As pointed out in further replies, it doesn't make sense to roll back. > enblend CVS is actually very stable and still supports everything that > enblend-3.0 did. Would it help if enblend-3.1 was released soon? I've asked my comaintainers' (Cc'd) opinion, and I'm still waiting for Sebastian's answer (enblend maintainer). It'd at least make hugin more usable for unstable users, assuming it'd be released and uploaded soon. And maybe, if release managers accept it, enblend 3.1 could be granted a freeze exception, which would mean that hugin eventually has a chance to migrate as well to testing, and then to be released with lenny. Summarizing, releasing enblend 3.1 those very days would: - put a bit of pressure on Sebastian's shoulders; - probably make enblend users happy; - grant hugin (snapshot) users a better hugin experiences; - eventually, and I insist on this *eventually* make it possible for enblend 3.1 and hugin to be shipped in the next stable release; if release managers don't accept the freeze exception, enblend 3.0 will be shipped, hugin not at all, and eventually made available through backports.org (but that's an additional step/repositories for stable users, which everyone tries to avoid). I really hope it'll be possible for hugin to make it in time, but there are a lot of dependencies here: upstreams, maintainers, release team. No room for certainty here. :) Mraw, KiBi.
signature.asc
Description: Digital signature
_______________________________________________ Pkg-phototools-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-phototools-devel
