Note, let me know if we need to release '3.4.6' or '4.0.2'!
I see many changes since last stable releases.
I am using 3.4.6-SVN (day use) and sometimes I am looking at 4.0.2-SVN
Otherwise, maybe I will go to the 'PyconFR', next month.
I am not a python dev (occupation) and I am not confortable for making
a conference about gramps, but it could be interesting to get new
stable releases before.
eg, conference schedule on 2012
Le mer. 11 sept. 2013 at 18:18,Paul Franklin <pf.98052@...> a
> Since we are getting near the end of the year, which
> causes some people to think about doing a gramps
> release in the Spring, I want to raise the topic of what
> gets done when, and why.
> As everybody knows, we all decided that gramps40
> was so "bleeding edge" that we would extend the life
> of the gramps34 branch.
> I would like to argue that since (IMHO) most of our
> users are Windows users, and that since there is no
> gramps40 for Windows yet, that we should NOT do a
> release as normal, next year.
> I feel that we should wait until gramps40 has been
> available on Windows for a /year/ -- fixing all the bugs
> which arise in the process -- before we "decommission"
> the gramps34 branch.
> So I don't think that "trunk" should turn into gramps41
> next year, the same way I don't think gramps34 should
> be stopped then either.
> I realize this is a major change from the way we do
> things, but especially given what a drastic change the
> gramps40 branch was, and how so very few distributions
> are offering it yet (thus making it available to the general
> linux user), I think we should seriously consider it.
> My own Fedora distribution is schedule to release the
> Fedora 20 version in November and only then will a
> gramps 4.0.x be in Fedora. And while I have not checked
> recently, I am not aware that Debian (and thus Ubuntu,
> etc.) are offering it in their repos yet, either.
> I just think that the gramps40 branch has not been
> adopted very widely, and so we should not think of
> stopping the gramps34 branch until it has been -- in
> Windows and linux both.
> I realize this will disappoint some people but I still
> think it is a wise course of action.
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> Gramps-devel mailing list