2010/4/22 Doug Blank <email@example.com>
2010/4/22 Stéphane Charette <firstname.lastname@example.org>:
No. I haven't run gramps since I noticed the issue early this morning
> So I believe we need to start co-ordinating the Gramps 3.2.2 release.
> We have a NarrativeWeb and/or a python problem introduced in 3.2.1.
> I'm being vague on purpose because I've just skimmed the e-mails and I
> actually don't know exactly what has broken.
> I did login to Mantis today to try and clear out and manage the 3.2.2
> roadmap, but I've never done that before and couldn't figure out how
> to even mark the 3.2.1 release as being shipped.
> What I would love to have is a very clear and precise way to tell when
> it is safe to build 3.2.2 again. This can be done by e-mail, or using
> the roadmap.
> How urgent is this release? If we want it very quickly, then we don't
> want a dozen things in this release. I'm guessing all these items
> were assigned to 3.2.2 a while ago, and should be pushed out:
> - 0003878: [Search/Filtering] Pivate option and filter on Exporter - new.
> - 0003640: [File Formats] Truncated FILE media path on Gedcom export - new.
> - 0003735: [Interface] Undo History window crashed - new.
> - 0003786: [Interface] TypeError: unsupported operand type(s) for -:
> 'NoneType' and 'int' - new.
> - 0003782: [Reports] Cannot set max generation on Ancestors Report
> (Ahnentafel) - new.
> - 0003785: [Interface] Unhandled exception - Undo History -
> ValueError: invalid tree path - new.
> - 0003877: [File Formats] "alive" and incomplet date - feedback.
> - 0002402: [Reports] Line spacing for text not correct in CairoDoc - feedback.
> - 0003400: [Search/Filtering] Media Files associated to living persons
> are not blacklisted - feedback.
> - 0003614: [Interface] undo gives wrong text in menu of what it will
> do - feedback.
> - 0002059: [Other] need a way to compare and merge notes - acknowledged.
> If no-one replies by the time I get back to it in about 8 hours, I'll
> move all these items out of 3.2.2 and into a future project.
> The next question is...do we have the necessary bug(s) created to
> track what we need fixed asap?
(and I just happened to not be able to sleep for a couple of hours and
was poking around sourceforge svn browser).
I want to repair narweb ASAP as I spent many hours last week fixing so
many things. But, please give a couple of days to let things settle,
and then a couple more to test.
I already reverted the change in branch32, so that should be ok at the moment.
James said he will use the branch32 version of nar web for Debian, not the one in the 3.2.1 package, other packagers might do the same. In that case, those users will not be hit by the issue. If Stephen does the same for the windows installer, then that is covered too.
So, I think we should ship a 3.2.2 quite quickly, but I don't think it must be this week.
I'll make a 3.2.3 in the bugtracker now, so we can set up the roadmap.