On Oct 2, 2012, at 9:53 AM, Tim Lyons <guy.linton@...> wrote:
> Benny Malengier wrote
>> I would like to suggest a release plan, and hope people can work towards
>> 1. To aim for a 3.4.2 mid October, so in two weeks time.
>> 2. To aim for a 4.0.0 Beta development release mid November.
>> 4.0.0 could be followed by 4.0.1, ... but all would be beta releases.
>> Then 4.1 would be the next stable release, hopefully in spring 2013. I
>> we need to push out 4.0 so that developers on windows, Mac, ..., and
>> packagers, and plugin writers, can have all the problems worked out before
>> a stable 4.1 release.
> I think that is an overly aggressive schedule!
> There are two problems:
> (1) how can "casual" gramps developers/translators/testers continue to
> up-port gramps34 patches to trunk?
> (2) can you commit to not releasing trunk until the dependencies are at
> least in stable versions of the various linux builds (and hopefully in
> Windows build and MacPorts build)?
I can't think of any good reason to wait for MacPorts. In fact, they seem not to have a port for pygobject, so the wait might be forever.
> In July, there were comments like:
>> 2012/7/24 John Ralls <[hidden email]>
>>> It occurs to me that we're being a bit aggressive in migrating to pygi:
>>> Thanks to Bug 679654  (and maybe others), Gramps won't actually run on
>>> any current released Gtk. That means that even after the next release
>>> it's only going to work on bleeding-edge distros like Ubuntu and Debian
>>> Unstable. That's going to freeze out a lot of users.
> Yes, I feel the pain, but understand the motivation. The problem area
> is for all of those "casual" gramps developers/translators/testers
> that help because they are willing, can, and it isn't too much of a
> burden. Well, this first step (like any first steps) is harder than it
> should be. What can we do to make this easier for everyone?
> I understand your arguments, but can you help people like ma a "casual"
> gramps developers/translators/testers?
> What new dependencies need to be installed to run trunk?
> I seem to remember reading that just installing a stable version of
> dependencies was not enough, and you need to install the bleeding edge from
> the latest git hub or something. Is that still the case? what does need to
> be installed?
That bug is fixed, and Gnome has just done their fall releases -- Gtk 3.6, Pango 1.32, and PyGObject 3.4 -- so the comment about not running in a stable Gtk is no longer true. They'll be in Ubuntu 12.10 and Fedora 18, so Linux users on the edge will be able to run Gramps (mostly, see below) by the time of the beta release. Non-bleeding-edge Linux users will have to wait, perhaps for a couple of years. That's not unusual.
I said that I was using git master the Gtk3 stack because Gramps was turning up some quartz bugs and its easiest for me to commit the fixes that way. Gnome has just gone through a commit cycle, so Gtk+-3.6.0 and Pango 1.32.1 have all of those changes, and Gramps seems to be mostly happy. Those changes are of no interest to Linux distros, though, so that's not an issue for them. It might be for MacPorts, but they don't seem to support PyGObject anyway, so perhaps that's moot.
There are, however, two dependencies that aren't going to be in any distro. They're optional, meaning that you can run Gramps without them, but they're really nice to have:
For Navigation view, you need Serge's updates to osm-gps-maps . (Aside: Serge, you really should generate a pull request back to John Stowers (nzjrs) so that he can integrate your changes.) It seems unlikely that this will be available in distros anytime soon, never mind MacPorts.
GtkSpell3 is in really good shape, but Sandro has been doing all of the work in his Github repo  instead of on Sourceforge, so we still need him to merge his changes back into the main branch, commit them to the Hg repo on SF, and do a release.
I don't know what MacPorts's plans are for any of this, but if you switch to Gtk-OSX, you can just use trunk/mac/gramps.modules for your moduleset and jhbuild will get all of the right stuff.
Once the beta is released, you can just download it and work inside the app bundle after you set $PYTHON, $PYTHONHOME, and $PYTHONPATH to point inside it. (I think with everything in python2.7/site-packages we don't need $GRAMPSHOME any more. Is that right?)
 git://github.com/SNoiraud/osm-gps-map.git, gtk3 branch
 git://github.com/manisandro/gtkspell3.git, changes branch