From: jerome <rom...@ya...> - 2012-12-21 15:03:23
|
The file is available under the 'unstable' section of the sourceforge hosting. http://sourceforge.net/projects/gramps/files/Unstable/ Nick, Thank you. In fact, it was to know the file format (default for UNIX or default for Windows OS?, both?) > There is a version string in setup.py as well as const.py.in - do we need to change both? Yes, I made the change on setup.py, 'versionstring' will be used into const.py.in/const.py. I just noted that webapp folder(s) is/are currently ignored. Should we think on add them for next alpha/beta release(s) or to wait ? > The .in files are still used by the substitution script in the setup.py file. Maybe we could 'spare' some code, there ! i.e, by using .rst template for man files, we can build/maintain/update/generate 'gramps.1' file. Do not need to keep makefile and .in extension if we can make the previous action without make. There is maybe one variable with Gramps VERSION and TODAY, but it seems to be also handled via .rst files: 'gramps.1.in' files could be 'gramps.1' into SVN. Same way for 'Gnome/linux/desktop' files: to check 'in.h' extension or '.h' for translations (C header) is the same if we do not use 'intltool'! gramps/data/tips.xml.in.h gramps/plugins/lib/holidays.xml.in.h data/gramps.xml.in.h data/gramps.desktop.in.h data/gramps.keys.in.h --- En date de : Ven 21.12.12, Nick Hall <nic...@ho...> a écrit : De: Nick Hall <nic...@ho...> Objet: Re: [Gramps-devel] Re : Re : release ? À: gra...@li... Date: Vendredi 21 décembre 2012, 15h22 Jérôme, You can create a source distribution with: python setup.py sdist to specify formats use: python setup.py sdist --formats=gztar,zip There is a version string in setup.py as well as const.py.in - do we need to change both? Users should extract the source distribution and then build or install it: python setup.py build sudo python setup.py install I would expect the installation to work with Linux distributions. The resource files will need to be copied to different locations for Mac and Windows, so I expect some issues with the installation on these platforms. We don't use distutils2 (packaging) so we don't use a setup.cfg file. The .in files are still used by the substitution script in the setup.py file. Nick. On 21/12/12 10:49, jerome wrote: In the past, I have tested something like: [sdist] formats = gztar zip into a simple setup.cfg file! Otherwise, should we keep some .in extensions related to configure/makefile? const.py.in, data/man/gramps.1.in, etc ... --- En date de : Ven 21.12.12, jerome <rom...@ya...> a écrit : De: jerome <rom...@ya...> Objet: [Gramps-devel] Re : release ? À: "Benny Malengier" <ben...@gm...> Cc: "Gramps Development List" <gra...@li...> Date: Vendredi 21 décembre 2012, 11h24 I will try ! Note, at a glance we need to set the 'UNSTABLE Gramps 4.0.0 Alpha' label into gramps/gen/const.py.in Is there any options for tarball file format? http://docs.python.org/2/distutils/sourcedist.html Some months ago, I used a setup.cfg file. http://www.gramps-project.org/bugs/view.php?id=2621#c10824 http://www.gramps-project.org/bugs/view.php?id=5743 --- En date de : Ven 21.12.12, Benny Malengier <ben...@gm...> a écrit : De: Benny Malengier <ben...@gm...> Objet: release ? À: "Jérôme" <rom...@ya...> Cc: "Gramps Development List" <gra...@li...> Date: Vendredi 21 décembre 2012, 9h51 Jerome, Can you do the release of 4.0.0-alpha1? The idea is: 1. we create a 4.0.0 release 2. we call the tar.gz 4.0.0-alpha1.tar.gz 3. on sourceforge it must be with UNSTABLE release 3. in _all_ our communication we mention: "UNSTABLE Gramps 4.0.0 Alpha release. This is a technology preview to allow plugin writers and packagers-installer writers to update their plugins and scripts. This release is not production ready, so use for testing!" ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Gramps-devel mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-devel > ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Gramps-devel mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-devel -----La pièce jointe associée suit----- ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d -----La pièce jointe associée suit----- _______________________________________________ Gramps-devel mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-devel |
From: Doug B. <dou...@gm...> - 2012-12-21 15:17:42
|
On Fri, Dec 21, 2012 at 10:03 AM, jerome <rom...@ya...> wrote: > The file is available under the 'unstable' section of the sourceforge > hosting. > > http://sourceforge.net/projects/gramps/files/Unstable/ > > > Nick, > > Thank you. > > In fact, it was to know the file format (default for UNIX or default for > Windows OS?, both?) > > > There is a version string in setup.py as well as const.py.in - do we > need to change both? > > Yes, I made the change on setup.py, 'versionstring' will be used into > const.py.in/const.py. > > I just noted that webapp folder(s) is/are currently ignored. > Should we think on add them for next alpha/beta release(s) or to wait ? > Would it make sense to make a separate "package" for the webapp? The Python could get installed under gramps, it the webapp directory. There are additional files (the templates from gramps/data/templates) that could be installed somewhere else (share). If you wanted to look into making a separate package that would be great. For example, could we "python setup.py build webapp" or something? We might also think about breaking the current package into base/core/gen and everything else needed to run the gtk code. In that way, a webserver sysadmin could just install gramps-core and gramps-webapp without having to install all of the gtk-oriented code. (Not sure if webapp trunk can run completely without gtk... there was a dependency on gtk for some report document functionality before... I will check). -Doug > > > The .in files are still used by the substitution script in the setup.py > file. > > Maybe we could 'spare' some code, there ! > i.e, by using .rst template for man files, we can > build/maintain/update/generate 'gramps.1' file. Do not need to keep > makefile and .in extension if we can make the previous action without make. > There is maybe one variable with Gramps VERSION and TODAY, but it seems to > be also handled via .rst files: 'gramps.1.in' files could be 'gramps.1' > into SVN. > > Same way for 'Gnome/linux/desktop' files: > to check 'in.h' extension or '.h' for translations (C header) is the > same if we do not use 'intltool'! > > gramps/data/tips.xml.in.h > gramps/plugins/lib/holidays.xml.in.h > data/gramps.xml.in.h > data/gramps.desktop.in.h > data/gramps.keys.in.h > > > --- En date de : Ven 21.12.12, Nick Hall <nic...@ho...> a > écrit : > > De: Nick Hall <nic...@ho...> > Objet: Re: [Gramps-devel] Re : Re : release ? > À: gra...@li... > Date: Vendredi 21 décembre 2012, 15h22 > > > Jérôme, > > > > You can create a source distribution with: > > > > python setup.py sdist > > > > to specify formats use: > > > > python setup.py sdist --formats=gztar,zip > > > > There is a version string in setup.py as well as const.py.in - do > we need to change both? > > > > Users should extract the source distribution and then build or > install it: > > > > python setup.py build > > > > sudo python setup.py install > > > > I would expect the installation to work with Linux distributions. > The resource files will need to be copied to different locations > for Mac and Windows, so I expect some issues with the installation > on these platforms. > > > > We don't use distutils2 (packaging) so we don't use a setup.cfg > file. The .in files are still used by the substitution script in > the setup.py file. > > > > Nick. > > > > > > On 21/12/12 10:49, jerome wrote: > > > > In the past, I have tested something like: > > [sdist] > formats = gztar zip > > into a simple setup.cfg file! > > Otherwise, should we keep some .in extensions related to > configure/makefile? const.py.in, data/man/gramps.1.in, etc ... > > > > --- En date de : Ven 21.12.12, jerome <rom...@ya...> a écrit : > > > > De: jerome <rom...@ya...> > Objet: [Gramps-devel] Re : release ? > À: "Benny Malengier" <ben...@gm...> > Cc: "Gramps Development List" <gra...@li...> > Date: Vendredi 21 décembre 2012, 11h24 > I will try ! > > Note, at a glance we need to set the 'UNSTABLE Gramps 4.0.0 > Alpha' label into gramps/gen/const.py.in > > Is there any options for tarball file format? > http://docs.python.org/2/distutils/sourcedist.html > > Some months ago, I used a setup.cfg file. > http://www.gramps-project.org/bugs/view.php?id=2621#c10824 > http://www.gramps-project.org/bugs/view.php?id=5743 > > > --- En date de : Ven 21.12.12, Benny Malengier <ben...@gm...> > a écrit : > > De: Benny Malengier <ben...@gm...> > Objet: release ? > À: "Jérôme" <rom...@ya...> > Cc: "Gramps Development List" <gra...@li...> > Date: Vendredi 21 décembre 2012, 9h51 > > Jerome, > > Can you do the release of 4.0.0-alpha1? > > The idea is: > 1. we create a 4.0.0 release > 2. we call the tar.gz 4.0.0-alpha1.tar.gz > > 3. on sourceforge it must be with UNSTABLE release > 3. in _all_ our communication we mention: > > "UNSTABLE Gramps 4.0.0 Alpha release. This is a technology > preview to allow plugin writers and packagers-installer > writers to update their plugins and scripts. This release is > not production ready, so use for testing!" > > > > > > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. > Free Trial > Remotely access PCs and mobile devices and provide instant > support > Improve your efficiency, and focus on delivering more > value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > > > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > > > > > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > > > -----La pièce jointe associée suit----- > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > -----La pièce jointe associée suit----- > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Benny M. <ben...@gm...> - 2012-12-21 17:06:03
|
2012/12/21 Doug Blank <dou...@gm...> > On Fri, Dec 21, 2012 at 10:03 AM, jerome <rom...@ya...> wrote: > >> The file is available under the 'unstable' section of the sourceforge >> hosting. >> >> http://sourceforge.net/projects/gramps/files/Unstable/ >> >> >> Nick, >> >> Thank you. >> >> In fact, it was to know the file format (default for UNIX or default for >> Windows OS?, both?) >> >> > There is a version string in setup.py as well as const.py.in - do we >> need to change both? >> >> Yes, I made the change on setup.py, 'versionstring' will be used into >> const.py.in/const.py. >> >> I just noted that webapp folder(s) is/are currently ignored. >> Should we think on add them for next alpha/beta release(s) or to wait ? >> > > Would it make sense to make a separate "package" for the webapp? The > Python could get installed under gramps, it the webapp directory. There are > additional files (the templates from gramps/data/templates) that could be > installed somewhere else (share). > > > If you wanted to look into making a separate package that would be great. > For example, could we "python setup.py build webapp" or something? > > We might also think about breaking the current package into base/core/gen > and everything else needed to run the gtk code. In that way, a webserver > sysadmin could just install gramps-core and gramps-webapp without having to > install all of the gtk-oriented code. (Not sure if webapp trunk can run > completely without gtk... there was a dependency on gtk for some report > document functionality before... I will check). > > > Nick looked into than when investigating distutils. I don't remember the conclusion :-) I think it was that it would be difficult with one setup.py. You probably could make a setupwebapp.py to install only the webapp and non-gtk, but then you need to split out gtk and non-gtk, while for the normal gramps releases we want to keep that together to avoid confusion with the users (so a single tar.gz). Hence, I would suggest: a server flag to the setup.py script. WIthout the flag, everything is installed, while for the server flag, the gtk things are removed. We then offer a gramps package with everything and a gramps-server package for server install. Both packages would contain the core gramps code. Benny |
From: Benny M. <ben...@gm...> - 2012-12-21 17:01:51
|
2012/12/21 jerome <rom...@ya...> > The file is available under the 'unstable' section of the sourceforge > hosting. > > http://sourceforge.net/projects/gramps/files/Unstable/ > > Ok Thanks! That seemed easier than expected :-) Did you forget to tag the release: http://sourceforge.net/p/gramps/code/20810/tree/tags/ It should be 4.0.0 Also, after a release, should you not change in setup.py in branch gramps40 the version to 4.0.1? Or do we not do that. Will you write on the announce mailing list, or me? Benny |
From: Jérôme <rom...@ya...> - 2012-12-21 19:02:13
|
> Did you forget to tag the release: > http://sourceforge.net/p/gramps/code/20810/tree/tags/ > It should be 4.0.0 4.0.0? I made 'gramps-4.0.0-alpha1'... http://sourceforge.net/p/gramps/code/20811/tree/tags/ There was 'gramps-3.2.0-beta1/2' before. > Also, after a release, should you not change in setup.py in branch > gramps40 the version to 4.0.1? Or do we not do that. Does it mean that there is no need an '4.0.0-alpha2'? And '4.0.0-alpha1' is like a 4.0.0 release??? http://www.gramps-project.org/bugs/roadmap_page.php?version_id=34 http://www.gramps-project.org/bugs/changelog_page.php?version_id=34 > That seemed easier than expected :-) Yes, we can easily put a '4.0.0-alpha2' release and replace '4.0.0-alpha1'!!! And/or to make it as official 'UNSTABLE' 4.0.0. Note, the changelog file generated from SVN was not added to '4.0.0-apha1' release... > Will you write on the announce mailing list, or me? I copied/pasted your text as NEWS on wiki and blog! :-[ http://www.gramps-project.org/wiki/index.php?title=Template:Releases/4.0.0alpha1 http://gramps-project.org/2012/12/gramps-4-0-0-alpha1-released/ I can do the same on announce mailing list? Jérôme Le 21/12/2012 18:01, Benny Malengier a écrit : > > > 2012/12/21 jerome <rom...@ya... <mailto:rom...@ya...>> > > The file is available under the 'unstable' section of the > sourceforge hosting. > > http://sourceforge.net/projects/gramps/files/Unstable/ > > > Ok Thanks! That seemed easier than expected :-) > > Did you forget to tag the release: > http://sourceforge.net/p/gramps/code/20810/tree/tags/ > It should be 4.0.0 > > Also, after a release, should you not change in setup.py in branch > gramps40 the version to 4.0.1? Or do we not do that. > > Will you write on the announce mailing list, or me? > > Benny > > |
From: Benny M. <ben...@gm...> - 2012-12-21 19:09:13
|
2012/12/21 Jérôme <rom...@ya...> > Did you forget to tag the release: >> http://sourceforge.net/p/**gramps/code/20810/tree/tags/<http://sourceforge.net/p/gramps/code/20810/tree/tags/> >> It should be 4.0.0 >> > > 4.0.0? > > I made 'gramps-4.0.0-alpha1'... > http://sourceforge.net/p/**gramps/code/20811/tree/tags/<http://sourceforge.net/p/gramps/code/20811/tree/tags/> > > There was 'gramps-3.2.0-beta1/2' before. > > > Also, after a release, should you not change in setup.py in branch >> gramps40 the version to 4.0.1? Or do we not do that. >> > > Does it mean that there is no need an '4.0.0-alpha2'? > And '4.0.0-alpha1' is like a 4.0.0 release??? > > http://www.gramps-project.org/**bugs/roadmap_page.php?version_**id=34<http://www.gramps-project.org/bugs/roadmap_page.php?version_id=34> > http://www.gramps-project.org/**bugs/changelog_page.php?**version_id=34<http://www.gramps-project.org/bugs/changelog_page.php?version_id=34> > > > As you want. For me 4.0.1 after this is ok, but 4.0.0-alpha2 or -beta1 is also good for me. You are release manager :-) > That seemed easier than expected :-) >> > > Yes, we can easily put a '4.0.0-alpha2' release and replace > '4.0.0-alpha1'!!! And/or to make it as official 'UNSTABLE' 4.0.0. > > Note, the changelog file generated from SVN was not added to '4.0.0-apha1' > release... no problem > > > Will you write on the announce mailing list, or me? >> > > I copied/pasted your text as NEWS on wiki and blog! :-[ > > http://www.gramps-project.org/**wiki/index.php?title=Template:** > Releases/4.0.0alpha1<http://www.gramps-project.org/wiki/index.php?title=Template:Releases/4.0.0alpha1> > > http://gramps-project.org/**2012/12/gramps-4-0-0-alpha1-**released/<http://gramps-project.org/2012/12/gramps-4-0-0-alpha1-released/> > > I can do the same on announce mailing list? > Yes, this is good. Write to announce, gramps-devel and gramps-user, so as to attract extra testers. Benny > > Jérôme > > > Le 21/12/2012 18:01, Benny Malengier a écrit : > >> >> >> 2012/12/21 jerome <rom...@ya... <mailto:rom...@ya...>> >> >> >> The file is available under the 'unstable' section of the >> sourceforge hosting. >> >> http://sourceforge.net/**projects/gramps/files/**Unstable/<http://sourceforge.net/projects/gramps/files/Unstable/> >> >> >> Ok Thanks! That seemed easier than expected :-) >> >> Did you forget to tag the release: >> http://sourceforge.net/p/**gramps/code/20810/tree/tags/<http://sourceforge.net/p/gramps/code/20810/tree/tags/> >> It should be 4.0.0 >> >> Also, after a release, should you not change in setup.py in branch >> gramps40 the version to 4.0.1? Or do we not do that. >> >> Will you write on the announce mailing list, or me? >> >> Benny >> >> >> > |
From: Benny M. <ben...@gm...> - 2012-12-21 19:20:57
|
John, I hope you can do a Mac package of this before Christmas :-) James, It would be great if you could update the debian folder, so we can make a general deb. I don't think doing the large change needed for Gramps 4.0 is something Jerome has experience with. Windows packagers, Any idea if a windows package is possible? I actually don't even know if GTK 3 is available. Inkscape and gimp are still GTK2 I think, working on GTK3 conversion... Benny 2012/12/21 Benny Malengier <ben...@gm...> > > > > 2012/12/21 Jérôme <rom...@ya...> > >> Did you forget to tag the release: >>> http://sourceforge.net/p/**gramps/code/20810/tree/tags/<http://sourceforge.net/p/gramps/code/20810/tree/tags/> >>> It should be 4.0.0 >>> >> >> 4.0.0? >> >> I made 'gramps-4.0.0-alpha1'... >> http://sourceforge.net/p/**gramps/code/20811/tree/tags/<http://sourceforge.net/p/gramps/code/20811/tree/tags/> >> >> There was 'gramps-3.2.0-beta1/2' before. >> >> >> Also, after a release, should you not change in setup.py in branch >>> gramps40 the version to 4.0.1? Or do we not do that. >>> >> >> Does it mean that there is no need an '4.0.0-alpha2'? >> And '4.0.0-alpha1' is like a 4.0.0 release??? >> >> http://www.gramps-project.org/**bugs/roadmap_page.php?version_**id=34<http://www.gramps-project.org/bugs/roadmap_page.php?version_id=34> >> http://www.gramps-project.org/**bugs/changelog_page.php?**version_id=34<http://www.gramps-project.org/bugs/changelog_page.php?version_id=34> >> >> >> > As you want. For me 4.0.1 after this is ok, but 4.0.0-alpha2 or -beta1 is > also good for me. You are release manager :-) > > >> That seemed easier than expected :-) >>> >> >> Yes, we can easily put a '4.0.0-alpha2' release and replace >> '4.0.0-alpha1'!!! And/or to make it as official 'UNSTABLE' 4.0.0. >> >> Note, the changelog file generated from SVN was not added to >> '4.0.0-apha1' release... > > > no problem > >> >> >> Will you write on the announce mailing list, or me? >>> >> >> I copied/pasted your text as NEWS on wiki and blog! :-[ >> >> http://www.gramps-project.org/**wiki/index.php?title=Template:** >> Releases/4.0.0alpha1<http://www.gramps-project.org/wiki/index.php?title=Template:Releases/4.0.0alpha1> >> >> http://gramps-project.org/**2012/12/gramps-4-0-0-alpha1-**released/<http://gramps-project.org/2012/12/gramps-4-0-0-alpha1-released/> >> >> I can do the same on announce mailing list? >> > > Yes, this is good. Write to announce, gramps-devel and gramps-user, so as > to attract extra testers. > > Benny > > >> >> Jérôme >> >> >> Le 21/12/2012 18:01, Benny Malengier a écrit : >> >>> >>> >>> 2012/12/21 jerome <rom...@ya... <mailto:rom...@ya...>> >>> >>> >>> The file is available under the 'unstable' section of the >>> sourceforge hosting. >>> >>> http://sourceforge.net/**projects/gramps/files/**Unstable/<http://sourceforge.net/projects/gramps/files/Unstable/> >>> >>> >>> Ok Thanks! That seemed easier than expected :-) >>> >>> Did you forget to tag the release: >>> http://sourceforge.net/p/**gramps/code/20810/tree/tags/<http://sourceforge.net/p/gramps/code/20810/tree/tags/> >>> It should be 4.0.0 >>> >>> Also, after a release, should you not change in setup.py in branch >>> gramps40 the version to 4.0.1? Or do we not do that. >>> >>> Will you write on the announce mailing list, or me? >>> >>> Benny >>> >>> >>> >> > |
From: Jérôme <rom...@ya...> - 2012-12-21 19:37:44
|
> Any idea if a windows package is possible? I actually don't even know if > GTK 3 is available. Inkscape and gimp are still GTK2 I think, working on > GTK3 conversion... If this could help: http://opensourcepack.blogspot.fr/p/pygobject-pygi-aio.html http://www.tarnyko.net/?q=node/1 source: ('gramps 35' on devel mailing list - 2012-09-12) Le 21/12/2012 20:20, Benny Malengier a écrit : > John, > > I hope you can do a Mac package of this before Christmas :-) > > James, > > It would be great if you could update the debian folder, so we can make > a general deb. I don't think doing the large change needed for Gramps > 4.0 is something Jerome has experience with. > > Windows packagers, > > Any idea if a windows package is possible? I actually don't even know if > GTK 3 is available. Inkscape and gimp are still GTK2 I think, working on > GTK3 conversion... > > Benny > > > 2012/12/21 Benny Malengier <ben...@gm... > <mailto:ben...@gm...>> > > > > > 2012/12/21 Jérôme <rom...@ya... <mailto:rom...@ya...>> > > Did you forget to tag the release: > http://sourceforge.net/p/__gramps/code/20810/tree/tags/ > <http://sourceforge.net/p/gramps/code/20810/tree/tags/> > It should be 4.0.0 > > > 4.0.0? > > I made 'gramps-4.0.0-alpha1'... > http://sourceforge.net/p/__gramps/code/20811/tree/tags/ > <http://sourceforge.net/p/gramps/code/20811/tree/tags/> > > There was 'gramps-3.2.0-beta1/2' before. > > > Also, after a release, should you not change in setup.py in > branch > gramps40 the version to 4.0.1? Or do we not do that. > > > Does it mean that there is no need an '4.0.0-alpha2'? > And '4.0.0-alpha1' is like a 4.0.0 release??? > > http://www.gramps-project.org/__bugs/roadmap_page.php?version___id=34 > <http://www.gramps-project.org/bugs/roadmap_page.php?version_id=34> > http://www.gramps-project.org/__bugs/changelog_page.php?__version_id=34 > <http://www.gramps-project.org/bugs/changelog_page.php?version_id=34> > > > > As you want. For me 4.0.1 after this is ok, but 4.0.0-alpha2 or > -beta1 is also good for me. You are release manager :-) > > That seemed easier than expected :-) > > > Yes, we can easily put a '4.0.0-alpha2' release and replace > '4.0.0-alpha1'!!! And/or to make it as official 'UNSTABLE' 4.0.0. > > Note, the changelog file generated from SVN was not added to > '4.0.0-apha1' release... > > > no problem > > > > Will you write on the announce mailing list, or me? > > > I copied/pasted your text as NEWS on wiki and blog! :-[ > > http://www.gramps-project.org/__wiki/index.php?title=Template:__Releases/4.0.0alpha1 > <http://www.gramps-project.org/wiki/index.php?title=Template:Releases/4.0.0alpha1> > > http://gramps-project.org/__2012/12/gramps-4-0-0-alpha1-__released/ > <http://gramps-project.org/2012/12/gramps-4-0-0-alpha1-released/> > > I can do the same on announce mailing list? > > > Yes, this is good. Write to announce, gramps-devel and gramps-user, > so as to attract extra testers. > > Benny > > > > Jérôme > > > Le 21/12/2012 18:01, Benny Malengier a écrit : > > > > 2012/12/21 jerome <rom...@ya... > <mailto:rom...@ya...> <mailto:rom...@ya... > <mailto:rom...@ya...>>> > > > The file is available under the 'unstable' section of the > sourceforge hosting. > > http://sourceforge.net/__projects/gramps/files/__Unstable/ > <http://sourceforge.net/projects/gramps/files/Unstable/> > > > Ok Thanks! That seemed easier than expected :-) > > Did you forget to tag the release: > http://sourceforge.net/p/__gramps/code/20810/tree/tags/ > <http://sourceforge.net/p/gramps/code/20810/tree/tags/> > It should be 4.0.0 > > Also, after a release, should you not change in setup.py in > branch > gramps40 the version to 4.0.1? Or do we not do that. > > Will you write on the announce mailing list, or me? > > Benny > > > > > > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > > > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Jérôme <rom...@ya...> - 2012-12-21 19:47:46
|
> http://www.tarnyko.net/?q=node/1 Rather http://www.tarnyko.net/en/ Le 21/12/2012 20:37, Jérôme a écrit : >> Any idea if a windows package is possible? I actually don't even know if >> GTK 3 is available. Inkscape and gimp are still GTK2 I think, working on >> GTK3 conversion... > > If this could help: > > http://opensourcepack.blogspot.fr/p/pygobject-pygi-aio.html > http://www.tarnyko.net/?q=node/1 > > source: ('gramps 35' on devel mailing list - 2012-09-12) > > Le 21/12/2012 20:20, Benny Malengier a écrit : >> John, >> >> I hope you can do a Mac package of this before Christmas :-) >> >> James, >> >> It would be great if you could update the debian folder, so we can make >> a general deb. I don't think doing the large change needed for Gramps >> 4.0 is something Jerome has experience with. >> >> Windows packagers, >> >> Any idea if a windows package is possible? I actually don't even know if >> GTK 3 is available. Inkscape and gimp are still GTK2 I think, working on >> GTK3 conversion... >> >> Benny >> >> >> 2012/12/21 Benny Malengier <ben...@gm... >> <mailto:ben...@gm...>> >> >> >> >> >> 2012/12/21 Jérôme <rom...@ya... <mailto:rom...@ya...>> >> >> Did you forget to tag the release: >> http://sourceforge.net/p/__gramps/code/20810/tree/tags/ >> <http://sourceforge.net/p/gramps/code/20810/tree/tags/> >> It should be 4.0.0 >> >> >> 4.0.0? >> >> I made 'gramps-4.0.0-alpha1'... >> http://sourceforge.net/p/__gramps/code/20811/tree/tags/ >> <http://sourceforge.net/p/gramps/code/20811/tree/tags/> >> >> There was 'gramps-3.2.0-beta1/2' before. >> >> >> Also, after a release, should you not change in setup.py in >> branch >> gramps40 the version to 4.0.1? Or do we not do that. >> >> >> Does it mean that there is no need an '4.0.0-alpha2'? >> And '4.0.0-alpha1' is like a 4.0.0 release??? >> >> >> http://www.gramps-project.org/__bugs/roadmap_page.php?version___id=34 >> >> <http://www.gramps-project.org/bugs/roadmap_page.php?version_id=34> >> >> http://www.gramps-project.org/__bugs/changelog_page.php?__version_id=34 >> >> <http://www.gramps-project.org/bugs/changelog_page.php?version_id=34> >> >> >> >> As you want. For me 4.0.1 after this is ok, but 4.0.0-alpha2 or >> -beta1 is also good for me. You are release manager :-) >> >> That seemed easier than expected :-) >> >> >> Yes, we can easily put a '4.0.0-alpha2' release and replace >> '4.0.0-alpha1'!!! And/or to make it as official 'UNSTABLE' 4.0.0. >> >> Note, the changelog file generated from SVN was not added to >> '4.0.0-apha1' release... >> >> >> no problem >> >> >> >> Will you write on the announce mailing list, or me? >> >> >> I copied/pasted your text as NEWS on wiki and blog! :-[ >> >> >> http://www.gramps-project.org/__wiki/index.php?title=Template:__Releases/4.0.0alpha1 >> >> >> <http://www.gramps-project.org/wiki/index.php?title=Template:Releases/4.0.0alpha1> >> >> >> >> http://gramps-project.org/__2012/12/gramps-4-0-0-alpha1-__released/ >> <http://gramps-project.org/2012/12/gramps-4-0-0-alpha1-released/> >> >> I can do the same on announce mailing list? >> >> >> Yes, this is good. Write to announce, gramps-devel and gramps-user, >> so as to attract extra testers. >> >> Benny >> >> >> >> Jérôme >> >> >> Le 21/12/2012 18:01, Benny Malengier a écrit : >> >> >> >> 2012/12/21 jerome <rom...@ya... >> <mailto:rom...@ya...> <mailto:rom...@ya... >> <mailto:rom...@ya...>>> >> >> >> The file is available under the 'unstable' section of >> the >> sourceforge hosting. >> >> http://sourceforge.net/__projects/gramps/files/__Unstable/ >> <http://sourceforge.net/projects/gramps/files/Unstable/> >> >> >> Ok Thanks! That seemed easier than expected :-) >> >> Did you forget to tag the release: >> http://sourceforge.net/p/__gramps/code/20810/tree/tags/ >> <http://sourceforge.net/p/gramps/code/20810/tree/tags/> >> It should be 4.0.0 >> >> Also, after a release, should you not change in setup.py in >> branch >> gramps40 the version to 4.0.1? Or do we not do that. >> >> Will you write on the announce mailing list, or me? >> >> Benny >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >> Remotely access PCs and mobile devices and provide instant support >> Improve your efficiency, and focus on delivering more value-add services >> Discover what IT Professionals Know. Rescue delivers >> http://p.sf.net/sfu/logmein_12329d2d >> >> >> >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > |
From: John R. <jr...@ce...> - 2012-12-21 20:26:57
|
On Dec 21, 2012, at 11:20 AM, Benny Malengier <ben...@gm...> wrote: > John, > > I hope you can do a Mac package of this before Christmas :-) > Me, too. ;-) I'm running into some issues building the stack with Python-3. If I can't get that working today I'll go with Python-2 until I can get all of the dependent packages sorted out. > Windows packagers, > > Any idea if a windows package is possible? I actually don't even know if GTK 3 is available. Inkscape and gimp are still GTK2 I think, working on GTK3 conversion... Looks like Dieter has stopped building gtk+ (the last one he did was 2.24.10 in February, but the current is 2.24.13) and never got around to building Gtk3. That means that for windows the packager will have to build the stack from source. JHBuild doesn't work on MSWin, but someone mentioned Gub [1] on another list and said that it worked for him on Windows. I haven't had a chance to try it yet. Note that the gtk module in their repo [2] is still at 2.17, so there might be a bit of work to get everything current. Not a novice project. ;-) Regards, John Ralls [1] http://lilypond.org/gub/ [2] https://github.com/janneke/gub/blob/master/gub/specs/gtk%2B.py |
From: John R. <jr...@ce...> - 2012-12-21 23:33:07
|
On Dec 21, 2012, at 12:26 PM, John Ralls <jr...@ce...> wrote: > > On Dec 21, 2012, at 11:20 AM, Benny Malengier <ben...@gm...> wrote: > >> John, >> >> I hope you can do a Mac package of this before Christmas :-) >> > > Me, too. ;-) > > I'm running into some issues building the stack with Python-3. If I can't get that working today I'll go with Python-2 until I can get all of the dependent packages sorted out. Nope, not happening. Building gobject-introspection is stuck on Python2. Once built, it might work with Python3, but that's going to take some hoop-jumping. Probably better to put that effort into fixing it. In the meantime, I'll make a bundle with Python2.7 for this (and probably the next few) release(s). Regards, John Ralls |
From: Benny M. <ben...@gm...> - 2012-12-22 08:28:01
|
2012/12/22 John Ralls <jr...@ce...> > > On Dec 21, 2012, at 12:26 PM, John Ralls <jr...@ce...> wrote: > > > > > On Dec 21, 2012, at 11:20 AM, Benny Malengier <ben...@gm...> > wrote: > > > >> John, > >> > >> I hope you can do a Mac package of this before Christmas :-) > >> > > > > Me, too. ;-) > > > > I'm running into some issues building the stack with Python-3. If I > can't get that working today I'll go with Python-2 until I can get all of > the dependent packages sorted out. > > Nope, not happening. Building gobject-introspection is stuck on Python2. > Once built, it might work with Python3, but that's going to take some > hoop-jumping. Probably better to put that effort into fixing it. In the > meantime, I'll make a bundle with Python2.7 for this (and probably the next > few) release(s). > > Python 2.7 is as good as python 3. Some minor things might be slower, as for convenience we changed some iteriterms() into items(), so some things which were iterators have become in 2.7 non-iterators. If that is noticeable will depend on the user data. Benny > Regards, > John Ralls |