On Jun 1, 3:49 pm, Bruno Postle <[email protected]> wrote: > Regarding the next release: the current HG default 'tip' has more than > enough features to be branched for release, and seems stable enough, > but I'm really not keen to drive this process again as I wasn't able > to give it the attention it deserved last time.
same here - I won't have time or resources to dedicate to driving a release process in the foreseeable future. I can answer questions about the process and help somebody who's new at running it, but my answers are likely to be delayed. I agree with you that the current hg default 'tip' has more than enough features to be branched for release, and from the chatter on this mailing list I have the impression that binary builders and users are of the same opinion. I see more attention being given to 2010.1 (development) builds than to 2010.0.0, even though the released tarball have not yet been used to produce a useful Windows 2010.0.0 release (or at least nobody has offered such binaries to be tested and uploaded to the Hugin homepage). Branching out 2010.2.0 is a piece of cake with Mercurial, even more than it was with Subversion. I am not sure how much effort will be required to clean it up for release. Does anybody have a list of what bugs are critical? I have seen much bug fixing activity in the repository (thanks Thomas!) but I have no clue how much additional effort is still necessary. 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
