2010/4/23 Doug Blank <doug.blank@gmail.com>
I've tested gramps 3.2.2 in SVN (and will continue to do so) but it
looks good. Everything appears to be in the state it was in as of a
couple of days ago.

I encourage everyone to give it a thorough going over (especially the
webreports). Non-critical issues (formatting, colors, minor missing
items) can go into the bug tracker for 3.2.3. Critical issues should
be put in the tracker, and also sent to this list.

There are a few items targeting 3.2.2 in the Roadmap:

http://www.gramps-project.org/bugs/roadmap_page.php

Should those be bumped to 3.2.3 and we release 3.2.2 soon? Or address
those issues and release 3.2.2 in a week or two?

I think they are best bumped to 3.2.3, and only fix in 3.2.2 depending on when Stephane can do the 3.2.2 release.
We need to take into account that testing branch32 is not the same as testing the 3.2.1 release, so current branch32 is what we would like the users to have.

Benny
 

-Doug

On Fri, Apr 23, 2010 at 3:18 AM, Jérôme <romjerome@yahoo.fr> wrote:
>> 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.
>
> + WebCal.py
>
>
> Benny Malengier a écrit :
>>
>>
>> 2010/4/22 Doug Blank <doug.blank@gmail.com <mailto:doug.blank@gmail.com>>
>>
>>    2010/4/22 Stéphane Charette <stephanecharette@gmail.com
>>    <mailto:stephanecharette@gmail.com>>:
>>     > 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?
>>
>>    No. I haven't run gramps since I noticed the issue early this morning
>>    (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.
>>
>> Benny
>>
>>    -Doug
>>
>>     >
>>     > Stéphane
>>     >
>>     >
>>
>>  ------------------------------------------------------------------------------
>>     > _______________________________________________
>>     > Gramps-devel mailing list
>>     > Gramps-devel@lists.sourceforge.net
>>    <mailto:Gramps-devel@lists.sourceforge.net>
>>     > https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>     >
>>
>>
>>  ------------------------------------------------------------------------------
>>    _______________________________________________
>>    Gramps-devel mailing list
>>    Gramps-devel@lists.sourceforge.net
>>    <mailto:Gramps-devel@lists.sourceforge.net>
>>    https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Gramps-devel mailing list
>> Gramps-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>
>