From: Doug B. <dou...@gm...> - 2010-01-18 04:30:03
|
Devs, I've committed some polish to the Plugin Status dialog: the Loaded tab now has the same buttons for the list items as does the Registered tab (Info, Hide, Edit, and Load). This makes it easy to edit or disable a badly behaving plugin. Before you'd have to go hunt for it in the Registered tab. Also, I added a new tab, "Install Addons" and renamed the dialog to "Plugin Manager". You can now get the addons from the wiki page by clicking on "Refresh Addon List" (which will save the list). You can install an addon in a .zip or .tgz file from your local file system, or from the web. Select an addon in the list, and click "Install Addon". The .zip or .tgz file is is opened and the complete contents are copied to your plugins directory. I also updated trunk to be using the latest wiki manual and related settings in const.py (so you should rerun ./autogen.sh and make). If you have an addon for 3.2, you should update the page: http://www.gramps-project.org/wiki/index.php?title=Plugins3.2 All addons must be in a .zip or .tgz file, along with its .gpr.py and translations (if you have those). Files from gramps-addons should work as is (if they have kept up with all of the changes in trunk). There are many things that we can do with this: - keep track of what is installed (by version number) - only show what can be updated (by version number) - be able to uninstall plugins I don't know how many of those I can get to before March, but feel free to work on that if you wish. Next I need to move the plugins to plugins32, but that should be simply changing the plugin dir entry in const.py (and making sure it upgrades correctly). Please let me know if you have any problems with this part, or if you have other ideas. -Doug |
From: Gary B. <bur...@ya...> - 2010-01-18 09:34:08
|
Hello Doug >Also, I added a new tab, "Install Addons" and renamed the dialog to "Plugin Manager". You can now get the addons from the wiki page by clicking on >"Refresh Addon List" (which will save the list). You can install an addon in a .zip or .tgz file from your local file system, or from the web. Select an addon in >the list, and click "Install Addon". The .zip or .tgz file is is opened and the complete contents are copied to your plugins directory. The gramps-addons svn repository does not currently have any ability to branch the code - the code effectively mirrors trunk in the gramps svn repository. I think it would be worthwhile to make a branch for 3.2.0 now and re-work the Plugin Manager so that it looks at addons in the branch appropriate for the Gramps version. Bye Gary |
From: Doug B. <dou...@gm...> - 2010-01-18 12:11:11
|
On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya...> wrote: > Hello Doug > > >Also, I added a new tab, "Install Addons" and renamed the dialog to > "Plugin Manager". You can now get the addons from the wiki page by clicking > on > >"Refresh Addon List" (which will save the list). You can install an addon > in a .zip or .tgz file from your local file system, or from the web. Select > an addon in > >the list, and click "Install Addon". The .zip or .tgz file is is opened > and the complete contents are copied to your plugins directory. > > The gramps-addons svn repository does not currently have any ability to > branch the code - the code effectively mirrors trunk in the gramps svn > repository. I think it would be worthwhile to make a branch for 3.2.0 now > and re-work the Plugin Manager so that it looks at addons in the branch > appropriate for the Gramps version. > > That's a great idea... can you do that? -Doug > Bye > > Gary > > > > > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Gary B. <bur...@ya...> - 2010-01-18 13:10:28
|
Hello Doug I have never tried to create a branch before, but it looks pretty simple using "svn copy" http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN If we are going to do this then I think we should also create a "trunk" and "tags" too so that it mirrors the main Gramps svn repository. Then we get: gramps-addons | +-----trunk | +-----branches | +-----tags This will allow bleeding edge development to continue in "trunk", bug fixes happen in "branches", and the Plugin Manager downloads addons from finished releases in "tags". Bye Gary > >From: Doug Blank <dou...@gm...> >To: Gary Burton <bur...@ya...> >Cc: gra...@li... >Sent: Mon, 18 January, 2010 12:11:03 >Subject: Re: [Gramps-devel] New Plugin Manager > > >On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya...> wrote: > >>>Hello Doug >> >> >>>>>Also, I added a new tab, "Install Addons" and renamed the dialog to "Plugin Manager". You can now get the addons from the wiki page by clicking on >>>>>"Refresh Addon List" (which will save the list). You can install an addon in a .zip or .tgz file from your local file system, or from the web. Select an addon in >>>>>the list, and click "Install Addon". The .zip or .tgz file is is opened and the complete contents are copied to your plugins directory. >> >>The gramps-addons svn repository does not currently have any ability to branch the code - the code effectively mirrors trunk in the gramps svn repository. I think it would be worthwhile to make a branch for 3.2.0 now and re-work the Plugin Manager so that it looks at addons in the branch appropriate for the Gramps version. >> >> > > >That's a great idea... can you do that? > > >-Doug |
From: Doug B. <dou...@gm...> - 2010-01-18 13:26:46
|
On Mon, Jan 18, 2010 at 8:10 AM, Gary Burton <bur...@ya...> wrote: > Hello Doug > > I have never tried to create a branch before, but it looks pretty simple > using "svn copy" > > > http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN > > If we are going to do this then I think we should also create a "trunk" and > "tags" too so that it mirrors the main Gramps svn repository. Then we get: > > gramps-addons > | > +-----trunk > | > +-----branches > | > +-----tags > > This will allow bleeding edge development to continue in "trunk", bug fixes > happen in "branches", and the Plugin Manager downloads addons from finished > releases in "tags". > > Yes, that sounds perfect. That way, downloads will continue to work, regardless of what is the current version. I made you an admin on gramps-addons, so if you (or someone) wanted to do this plan, they could. -Doug > Bye > > Gary > > > > >From: Doug Blank <dou...@gm...> > >To: Gary Burton <bur...@ya...> > >Cc: gra...@li... > >Sent: Mon, 18 January, 2010 12:11:03 > >Subject: Re: [Gramps-devel] New Plugin Manager > > > > > >On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya...> > wrote: > > > >>>Hello Doug > >> > >> > >>>>>Also, I added a new tab, "Install Addons" and renamed the dialog to > "Plugin Manager". You can now get the addons from the wiki page by clicking > on > >>>>>"Refresh Addon List" (which will save the list). You can install an > addon in a .zip or .tgz file from your local file system, or from the web. > Select an addon in > >>>>>the list, and click "Install Addon". The .zip or .tgz file is is > opened and the complete contents are copied to your plugins directory. > >> > >>The gramps-addons svn repository does not currently have any ability to > branch the code - the code effectively mirrors trunk in the gramps svn > repository. I think it would be worthwhile to make a branch for 3.2.0 now > and re-work the Plugin Manager so that it looks at addons in the branch > appropriate for the Gramps version. > >> > >> > > > > > >That's a great idea... can you do that? > > > > > >-Doug > > > > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Doug B. <dou...@gm...> - 2010-01-18 14:29:52
|
On Mon, Jan 18, 2010 at 8:26 AM, Doug Blank <dou...@gm...> wrote: > On Mon, Jan 18, 2010 at 8:10 AM, Gary Burton <bur...@ya...>wrote: > >> Hello Doug >> >> I have never tried to create a branch before, but it looks pretty simple >> using "svn copy" >> >> >> http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN >> >> If we are going to do this then I think we should also create a "trunk" >> and "tags" too so that it mirrors the main Gramps svn repository. Then we >> get: >> >> gramps-addons >> | >> +-----trunk >> | >> +-----branches >> | >> +-----tags >> >> This will allow bleeding edge development to continue in "trunk", bug >> fixes happen in "branches", and the Plugin Manager downloads addons from >> finished releases in "tags". >> >> > Yes, that sounds perfect. That way, downloads will continue to work, > regardless of what is the current version. > > Actually, I wonder if we even need a trunk... all code is always done for a branch. Perhaps we can just leave trunk out? -Doug > I made you an admin on gramps-addons, so if you (or someone) wanted to do > this plan, they could. > > -Doug > > >> Bye >> >> Gary >> >> > >> >From: Doug Blank <dou...@gm...> >> >To: Gary Burton <bur...@ya...> >> >Cc: gra...@li... >> >Sent: Mon, 18 January, 2010 12:11:03 >> >Subject: Re: [Gramps-devel] New Plugin Manager >> > >> > >> >On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya...> >> wrote: >> > >> >>>Hello Doug >> >> >> >> >> >>>>>Also, I added a new tab, "Install Addons" and renamed the dialog to >> "Plugin Manager". You can now get the addons from the wiki page by clicking >> on >> >>>>>"Refresh Addon List" (which will save the list). You can install an >> addon in a .zip or .tgz file from your local file system, or from the web. >> Select an addon in >> >>>>>the list, and click "Install Addon". The .zip or .tgz file is is >> opened and the complete contents are copied to your plugins directory. >> >> >> >>The gramps-addons svn repository does not currently have any ability to >> branch the code - the code effectively mirrors trunk in the gramps svn >> repository. I think it would be worthwhile to make a branch for 3.2.0 now >> and re-work the Plugin Manager so that it looks at addons in the branch >> appropriate for the Gramps version. >> >> >> >> >> > >> > >> >That's a great idea... can you do that? >> > >> > >> >-Doug >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Throughout its 18-year history, RSA Conference consistently attracts the >> world's best and brightest in the field, creating opportunities for >> Conference >> attendees to learn about information security's most important issues >> through >> interactions with peers, luminaries and emerging and established >> companies. >> http://p.sf.net/sfu/rsaconf-dev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > |
From: Benny M. <ben...@gm...> - 2010-01-18 14:33:34
|
2010/1/18 Doug Blank <dou...@gm...>: > On Mon, Jan 18, 2010 at 8:26 AM, Doug Blank <dou...@gm...> wrote: >> >> On Mon, Jan 18, 2010 at 8:10 AM, Gary Burton <bur...@ya...> >> wrote: >>> >>> Hello Doug >>> >>> I have never tried to create a branch before, but it looks pretty simple >>> using "svn copy" >>> >>> >>> http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN >>> >>> If we are going to do this then I think we should also create a "trunk" >>> and "tags" too so that it mirrors the main Gramps svn repository. Then we >>> get: >>> >>> gramps-addons >>> | >>> +-----trunk >>> | >>> +-----branches >>> | >>> +-----tags >>> >>> This will allow bleeding edge development to continue in "trunk", bug >>> fixes happen in "branches", and the Plugin Manager downloads addons from >>> finished releases in "tags". >>> >> >> Yes, that sounds perfect. That way, downloads will continue to work, >> regardless of what is the current version. > > Actually, I wonder if we even need a trunk... all code is always done for a > branch. Perhaps we can just leave trunk out? You might not know the name of the following branch before trunk is frozen and branched of. Eg, instead of 3.3 we might go to 4.0, who knows? Benny > > -Doug > > >> >> I made you an admin on gramps-addons, so if you (or someone) wanted to do >> this plan, they could. >> -Doug >> >>> >>> Bye >>> >>> Gary >>> >>> > >>> >From: Doug Blank <dou...@gm...> >>> >To: Gary Burton <bur...@ya...> >>> >Cc: gra...@li... >>> >Sent: Mon, 18 January, 2010 12:11:03 >>> >Subject: Re: [Gramps-devel] New Plugin Manager >>> > >>> > >>> >On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya...> >>> > wrote: >>> > >>> >>>Hello Doug >>> >> >>> >> >>> >>>>>Also, I added a new tab, "Install Addons" and renamed the dialog to >>> >>>>> "Plugin Manager". You can now get the addons from the wiki page by clicking >>> >>>>> on >>> >>>>>"Refresh Addon List" (which will save the list). You can install an >>> >>>>> addon in a .zip or .tgz file from your local file system, or from the web. >>> >>>>> Select an addon in >>> >>>>>the list, and click "Install Addon". The .zip or .tgz file is is >>> >>>>> opened and the complete contents are copied to your plugins directory. >>> >> >>> >>The gramps-addons svn repository does not currently have any ability to >>> >> branch the code - the code effectively mirrors trunk in the gramps svn >>> >> repository. I think it would be worthwhile to make a branch for 3.2.0 now >>> >> and re-work the Plugin Manager so that it looks at addons in the branch >>> >> appropriate for the Gramps version. >>> >> >>> >> >>> > >>> > >>> >That's a great idea... can you do that? >>> > >>> > >>> >-Doug >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Throughout its 18-year history, RSA Conference consistently attracts the >>> world's best and brightest in the field, creating opportunities for >>> Conference >>> attendees to learn about information security's most important issues >>> through >>> interactions with peers, luminaries and emerging and established >>> companies. >>> http://p.sf.net/sfu/rsaconf-dev2dev >>> _______________________________________________ >>> Gramps-devel mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |
From: Rob H. <rob...@gm...> - 2010-01-18 20:36:35
|
Good day to all: I was wondering if somewhere in the *.gpr.py file, that there be a variable to specify which version of Gramps it is built for? Then the plugins/ gramplet registration system could determine which plugins/gramplets to load for each version of Gramps/ Gramps-Connect.... Sincerely yours, Rob G. Healey On Mon, Jan 18, 2010 at 6:33 AM, Benny Malengier <ben...@gm...>wrote: > 2010/1/18 Doug Blank <dou...@gm...>: > > On Mon, Jan 18, 2010 at 8:26 AM, Doug Blank <dou...@gm...> > wrote: > >> > >> On Mon, Jan 18, 2010 at 8:10 AM, Gary Burton <bur...@ya...> > >> wrote: > >>> > >>> Hello Doug > >>> > >>> I have never tried to create a branch before, but it looks pretty > simple > >>> using "svn copy" > >>> > >>> > >>> > http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN > >>> > >>> If we are going to do this then I think we should also create a "trunk" > >>> and "tags" too so that it mirrors the main Gramps svn repository. Then > we > >>> get: > >>> > >>> gramps-addons > >>> | > >>> +-----trunk > >>> | > >>> +-----branches > >>> | > >>> +-----tags > >>> > >>> This will allow bleeding edge development to continue in "trunk", bug > >>> fixes happen in "branches", and the Plugin Manager downloads addons > from > >>> finished releases in "tags". > >>> > >> > >> Yes, that sounds perfect. That way, downloads will continue to work, > >> regardless of what is the current version. > > > > Actually, I wonder if we even need a trunk... all code is always done for > a > > branch. Perhaps we can just leave trunk out? > > You might not know the name of the following branch before trunk is > frozen and branched of. Eg, instead of 3.3 we might go to 4.0, who > knows? > > Benny > > > > > -Doug > > > > > >> > >> I made you an admin on gramps-addons, so if you (or someone) wanted to > do > >> this plan, they could. > >> -Doug > >> > >>> > >>> Bye > >>> > >>> Gary > >>> > >>> > > >>> >From: Doug Blank <dou...@gm...> > >>> >To: Gary Burton <bur...@ya...> > >>> >Cc: gra...@li... > >>> >Sent: Mon, 18 January, 2010 12:11:03 > >>> >Subject: Re: [Gramps-devel] New Plugin Manager > >>> > > >>> > > >>> >On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya...> > >>> > wrote: > >>> > > >>> >>>Hello Doug > >>> >> > >>> >> > >>> >>>>>Also, I added a new tab, "Install Addons" and renamed the dialog > to > >>> >>>>> "Plugin Manager". You can now get the addons from the wiki page > by clicking > >>> >>>>> on > >>> >>>>>"Refresh Addon List" (which will save the list). You can install > an > >>> >>>>> addon in a .zip or .tgz file from your local file system, or from > the web. > >>> >>>>> Select an addon in > >>> >>>>>the list, and click "Install Addon". The .zip or .tgz file is is > >>> >>>>> opened and the complete contents are copied to your plugins > directory. > >>> >> > >>> >>The gramps-addons svn repository does not currently have any ability > to > >>> >> branch the code - the code effectively mirrors trunk in the gramps > svn > >>> >> repository. I think it would be worthwhile to make a branch for > 3.2.0 now > >>> >> and re-work the Plugin Manager so that it looks at addons in the > branch > >>> >> appropriate for the Gramps version. > >>> >> > >>> >> > >>> > > >>> > > >>> >That's a great idea... can you do that? > >>> > > >>> > > >>> >-Doug > >>> > >>> > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> Throughout its 18-year history, RSA Conference consistently attracts > the > >>> world's best and brightest in the field, creating opportunities for > >>> Conference > >>> attendees to learn about information security's most important issues > >>> through > >>> interactions with peers, luminaries and emerging and established > >>> companies. > >>> http://p.sf.net/sfu/rsaconf-dev2dev > >>> _______________________________________________ > >>> Gramps-devel mailing list > >>> Gra...@li... > >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel > >> > > > > > > > ------------------------------------------------------------------------------ > > Throughout its 18-year history, RSA Conference consistently attracts the > > world's best and brightest in the field, creating opportunities for > > Conference > > attendees to learn about information security's most important issues > > through > > interactions with peers, luminaries and emerging and established > companies. > > http://p.sf.net/sfu/rsaconf-dev2dev > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Doug B. <dou...@gm...> - 2010-01-19 14:10:03
|
On Mon, Jan 18, 2010 at 3:36 PM, Rob Healey <rob...@gm...> wrote: > Good day to all: > > I was wondering if somewhere in the *.gpr.py file, that there be a variable > to specify which version of Gramps it is built for? > > Then the plugins/ gramplet registration system could determine which > plugins/gramplets to load for each version of Gramps/ Gramps-Connect.... > > Yep, that's something to be considered... That would at least give users a clue about what they are trying to do, a la: http://www.gramps-project.org/bugs/view.php?id=3522 Gramplets did have this before the reorg. Also, plugins need to have a version themselves. Hope to get to these before Feb. -Doug > > Sincerely yours, > Rob G. Healey > > > On Mon, Jan 18, 2010 at 6:33 AM, Benny Malengier < > ben...@gm...> wrote: > >> 2010/1/18 Doug Blank <dou...@gm...>: >> > On Mon, Jan 18, 2010 at 8:26 AM, Doug Blank <dou...@gm...> >> wrote: >> >> >> >> On Mon, Jan 18, 2010 at 8:10 AM, Gary Burton <bur...@ya...> >> >> wrote: >> >>> >> >>> Hello Doug >> >>> >> >>> I have never tried to create a branch before, but it looks pretty >> simple >> >>> using "svn copy" >> >>> >> >>> >> >>> >> http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN >> >>> >> >>> If we are going to do this then I think we should also create a >> "trunk" >> >>> and "tags" too so that it mirrors the main Gramps svn repository. Then >> we >> >>> get: >> >>> >> >>> gramps-addons >> >>> | >> >>> +-----trunk >> >>> | >> >>> +-----branches >> >>> | >> >>> +-----tags >> >>> >> >>> This will allow bleeding edge development to continue in "trunk", bug >> >>> fixes happen in "branches", and the Plugin Manager downloads addons >> from >> >>> finished releases in "tags". >> >>> >> >> >> >> Yes, that sounds perfect. That way, downloads will continue to work, >> >> regardless of what is the current version. >> > >> > Actually, I wonder if we even need a trunk... all code is always done >> for a >> > branch. Perhaps we can just leave trunk out? >> >> You might not know the name of the following branch before trunk is >> frozen and branched of. Eg, instead of 3.3 we might go to 4.0, who >> knows? >> >> Benny >> >> > >> > -Doug >> > >> > >> >> >> >> I made you an admin on gramps-addons, so if you (or someone) wanted to >> do >> >> this plan, they could. >> >> -Doug >> >> >> >>> >> >>> Bye >> >>> >> >>> Gary >> >>> >> >>> > >> >>> >From: Doug Blank <dou...@gm...> >> >>> >To: Gary Burton <bur...@ya...> >> >>> >Cc: gra...@li... >> >>> >Sent: Mon, 18 January, 2010 12:11:03 >> >>> >Subject: Re: [Gramps-devel] New Plugin Manager >> >>> > >> >>> > >> >>> >On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya... >> > >> >>> > wrote: >> >>> > >> >>> >>>Hello Doug >> >>> >> >> >>> >> >> >>> >>>>>Also, I added a new tab, "Install Addons" and renamed the dialog >> to >> >>> >>>>> "Plugin Manager". You can now get the addons from the wiki page >> by clicking >> >>> >>>>> on >> >>> >>>>>"Refresh Addon List" (which will save the list). You can install >> an >> >>> >>>>> addon in a .zip or .tgz file from your local file system, or >> from the web. >> >>> >>>>> Select an addon in >> >>> >>>>>the list, and click "Install Addon". The .zip or .tgz file is is >> >>> >>>>> opened and the complete contents are copied to your plugins >> directory. >> >>> >> >> >>> >>The gramps-addons svn repository does not currently have any ability >> to >> >>> >> branch the code - the code effectively mirrors trunk in the gramps >> svn >> >>> >> repository. I think it would be worthwhile to make a branch for >> 3.2.0 now >> >>> >> and re-work the Plugin Manager so that it looks at addons in the >> branch >> >>> >> appropriate for the Gramps version. >> >>> >> >> >>> >> >> >>> > >> >>> > >> >>> >That's a great idea... can you do that? >> >>> > >> >>> > >> >>> >-Doug >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> ------------------------------------------------------------------------------ >> >>> Throughout its 18-year history, RSA Conference consistently attracts >> the >> >>> world's best and brightest in the field, creating opportunities for >> >>> Conference >> >>> attendees to learn about information security's most important issues >> >>> through >> >>> interactions with peers, luminaries and emerging and established >> >>> companies. >> >>> http://p.sf.net/sfu/rsaconf-dev2dev >> >>> _______________________________________________ >> >>> Gramps-devel mailing list >> >>> Gra...@li... >> >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> >> >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Throughout its 18-year history, RSA Conference consistently attracts the >> > world's best and brightest in the field, creating opportunities for >> > Conference >> > attendees to learn about information security's most important issues >> > through >> > interactions with peers, luminaries and emerging and established >> companies. >> > http://p.sf.net/sfu/rsaconf-dev2dev >> > _______________________________________________ >> > Gramps-devel mailing list >> > Gra...@li... >> > https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > >> > >> >> >> ------------------------------------------------------------------------------ >> Throughout its 18-year history, RSA Conference consistently attracts the >> world's best and brightest in the field, creating opportunities for >> Conference >> attendees to learn about information security's most important issues >> through >> interactions with peers, luminaries and emerging and established >> companies. >> http://p.sf.net/sfu/rsaconf-dev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |
From: Doug B. <dou...@gm...> - 2010-02-10 02:44:00
|
I'm planning on creating the trunk and branch versions of gramps-addons in a few hours... -Doug On Mon, Jan 18, 2010 at 8:10 AM, Gary Burton <bur...@ya...> wrote: > Hello Doug > > I have never tried to create a branch before, but it looks pretty simple using "svn copy" > > http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN > > If we are going to do this then I think we should also create a "trunk" and "tags" too so that it mirrors the main Gramps svn repository. Then we get: > > gramps-addons > | > +-----trunk > | > +-----branches > | > +-----tags > > This will allow bleeding edge development to continue in "trunk", bug fixes happen in "branches", and the Plugin Manager downloads addons from finished releases in "tags". > > Bye > > Gary > >> >>From: Doug Blank <dou...@gm...> >>To: Gary Burton <bur...@ya...> >>Cc: gra...@li... >>Sent: Mon, 18 January, 2010 12:11:03 >>Subject: Re: [Gramps-devel] New Plugin Manager >> >> >>On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya...> wrote: >> >>>>Hello Doug >>> >>> >>>>>>Also, I added a new tab, "Install Addons" and renamed the dialog to "Plugin Manager". You can now get the addons from the wiki page by clicking on >>>>>>"Refresh Addon List" (which will save the list). You can install an addon in a .zip or .tgz file from your local file system, or from the web. Select an addon in >>>>>>the list, and click "Install Addon". The .zip or .tgz file is is opened and the complete contents are copied to your plugins directory. >>> >>>The gramps-addons svn repository does not currently have any ability to branch the code - the code effectively mirrors trunk in the gramps svn repository. I think it would be worthwhile to make a branch for 3.2.0 now and re-work the Plugin Manager so that it looks at addons in the branch appropriate for the Gramps version. >>> >>> >> >> >>That's a great idea... can you do that? >> >> >>-Doug > > > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Rob H. <rob...@gm...> - 2010-02-10 06:05:55
|
Dear Doug: Will you respond here once it has been done? Please also give links for all new items.... Sincerely yours, Rob G. Healey On Tue, Feb 9, 2010 at 6:43 PM, Doug Blank <dou...@gm...> wrote: > I'm planning on creating the trunk and branch versions of > gramps-addons in a few hours... > > -Doug > > > On Mon, Jan 18, 2010 at 8:10 AM, Gary Burton <bur...@ya...> > wrote: > > Hello Doug > > > > I have never tried to create a branch before, but it looks pretty simple > using "svn copy" > > > > > http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN > > > > If we are going to do this then I think we should also create a "trunk" > and "tags" too so that it mirrors the main Gramps svn repository. Then we > get: > > > > gramps-addons > > | > > +-----trunk > > | > > +-----branches > > | > > +-----tags > > > > This will allow bleeding edge development to continue in "trunk", bug > fixes happen in "branches", and the Plugin Manager downloads addons from > finished releases in "tags". > > > > Bye > > > > Gary > > > >> > >>From: Doug Blank <dou...@gm...> > >>To: Gary Burton <bur...@ya...> > >>Cc: gra...@li... > >>Sent: Mon, 18 January, 2010 12:11:03 > >>Subject: Re: [Gramps-devel] New Plugin Manager > >> > >> > >>On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya...> > wrote: > >> > >>>>Hello Doug > >>> > >>> > >>>>>>Also, I added a new tab, "Install Addons" and renamed the dialog to > "Plugin Manager". You can now get the addons from the wiki page by clicking > on > >>>>>>"Refresh Addon List" (which will save the list). You can install an > addon in a .zip or .tgz file from your local file system, or from the web. > Select an addon in > >>>>>>the list, and click "Install Addon". The .zip or .tgz file is is > opened and the complete contents are copied to your plugins directory. > >>> > >>>The gramps-addons svn repository does not currently have any ability to > branch the code - the code effectively mirrors trunk in the gramps svn > repository. I think it would be worthwhile to make a branch for 3.2.0 now > and re-work the Plugin Manager so that it looks at addons in the branch > appropriate for the Gramps version. > >>> > >>> > >> > >> > >>That's a great idea... can you do that? > >> > >> > >>-Doug > > > > > > > > > > > ------------------------------------------------------------------------------ > > Throughout its 18-year history, RSA Conference consistently attracts the > > world's best and brightest in the field, creating opportunities for > Conference > > attendees to learn about information security's most important issues > through > > interactions with peers, luminaries and emerging and established > companies. > > http://p.sf.net/sfu/rsaconf-dev2dev > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Doug B. <dou...@gm...> - 2010-02-10 12:50:32
|
On Tue, Feb 9, 2010 at 9:43 PM, Doug Blank <dou...@gm...> wrote: > I'm planning on creating the trunk and branch versions of > gramps-addons in a few hours... Ok, I've moved gramps-addons/* to gramps-addons/trunk/* and made a copy to gramps-addons/branches/gramps32/ If you are working on an addon for gramps32, then you should do your work in gramps-addons/branches/gramps32/contrib Once you are done with it, you can bring trunk up to date with "svn merge" and then begin developing for the next version of gramps. For more on svn, see: http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN I've also added a check in the plugin registration code to make sure that a plugin is targeted to the correct version of gramps (ie, "3.2"). If a plugin does not have gramps_target_version == '3.2', then it won't load. I also moved Rob's ImageMetadata versions (version 1 to gramps-addons/branches/gramps32/contrib, and version 2 to gramps-addons/trunk/contrib). If this is not correct, please let me know. (BTW, version 1 does not run as there is a missing ImageMetadata function). Finally, I've updated the addon documentation to reflect these changes: http://www.gramps-project.org/wiki/index.php?title=Addons_Development If you see something wrong, please let me know. -Doug > -Doug > > > On Mon, Jan 18, 2010 at 8:10 AM, Gary Burton <bur...@ya...> wrote: >> Hello Doug >> >> I have never tried to create a branch before, but it looks pretty simple using "svn copy" >> >> http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN >> >> If we are going to do this then I think we should also create a "trunk" and "tags" too so that it mirrors the main Gramps svn repository. Then we get: >> >> gramps-addons >> | >> +-----trunk >> | >> +-----branches >> | >> +-----tags >> >> This will allow bleeding edge development to continue in "trunk", bug fixes happen in "branches", and the Plugin Manager downloads addons from finished releases in "tags". >> >> Bye >> >> Gary >> >>> >>>From: Doug Blank <dou...@gm...> >>>To: Gary Burton <bur...@ya...> >>>Cc: gra...@li... >>>Sent: Mon, 18 January, 2010 12:11:03 >>>Subject: Re: [Gramps-devel] New Plugin Manager >>> >>> >>>On Mon, Jan 18, 2010 at 4:33 AM, Gary Burton <bur...@ya...> wrote: >>> >>>>>Hello Doug >>>> >>>> >>>>>>>Also, I added a new tab, "Install Addons" and renamed the dialog to "Plugin Manager". You can now get the addons from the wiki page by clicking on >>>>>>>"Refresh Addon List" (which will save the list). You can install an addon in a .zip or .tgz file from your local file system, or from the web. Select an addon in >>>>>>>the list, and click "Install Addon". The .zip or .tgz file is is opened and the complete contents are copied to your plugins directory. >>>> >>>>The gramps-addons svn repository does not currently have any ability to branch the code - the code effectively mirrors trunk in the gramps svn repository. I think it would be worthwhile to make a branch for 3.2.0 now and re-work the Plugin Manager so that it looks at addons in the branch appropriate for the Gramps version. >>>> >>>> >>> >>> >>>That's a great idea... can you do that? >>> >>> >>>-Doug >> >> >> >> >> ------------------------------------------------------------------------------ >> Throughout its 18-year history, RSA Conference consistently attracts the >> world's best and brightest in the field, creating opportunities for Conference >> attendees to learn about information security's most important issues through >> interactions with peers, luminaries and emerging and established companies. >> http://p.sf.net/sfu/rsaconf-dev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > |
From: Gary B. <bur...@ya...> - 2010-02-10 14:05:47
|
Hello Doug, > I've also added a check in the plugin registration code to make sure > that a plugin is targeted to the correct version of gramps (ie, > "3.2"). If a plugin does not have gramps_target_version == '3.2', then > it won't load. Thanks for doing this, it will make addon development a bit more convenient. I will test it out tonight and see if there are any issues. An open question: are we going to tag branches to make maintenance releases like we do in the rest of Gramps? If we do then Gramps needs to be looking at the appropriate tagged Download directory to get a copy of the .tar.gz file for an addon. I guess right now that Gramps is looking at the Download directory in the branch and so will only pick up the latest revision of an addon for that branch. This might be a problem if the addon has a dependency on some functionality that only exists in a particular tagged version of Gramps. Bye Gary |
From: Doug B. <dou...@gm...> - 2010-02-10 15:00:07
|
On Wed, Feb 10, 2010 at 8:38 AM, Gary Burton <bur...@ya...> wrote: > Hello Doug, > > > >> I've also added a check in the plugin registration code to make sure >> that a plugin is targeted to the correct version of gramps (ie, >> "3.2"). If a plugin does not have gramps_target_version == '3.2', then >> it won't load. > > Thanks for doing this, it will make addon development a bit more convenient. I will test it out tonight and see if there are any issues. > No problem. > An open question: are we going to tag branches to make maintenance releases like we do in the rest of Gramps? If we do then Gramps needs to be looking at the appropriate tagged Download directory to get a copy of the .tar.gz file for an addon. I guess right now that Gramps is looking at the Download directory in the branch and so will only pick up the latest revision of an addon for that branch. This might be a problem if the addon has a dependency on some functionality that only exists in a particular tagged version of Gramps. I must admit that I don't fully understand the implications of what you describe. But I'm very happy to leave these decisions to you and those that have a feeling of what the right thing to do is. Thanks! -Doug > > Bye > > Gary > > > > > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Gary B. <bur...@ya...> - 2010-02-10 16:31:45
|
Hello Doug, > > An open question: are we going to tag branches to make maintenance releases > like we do in the rest of Gramps? If we do then Gramps needs to be looking at > the appropriate tagged Download directory to get a copy of the .tar.gz file for > an addon. I guess right now that Gramps is looking at the Download directory in > the branch and so will only pick up the latest revision of an addon for that > branch. This might be a problem if the addon has a dependency on some > functionality that only exists in a particular tagged version of Gramps. > > I must admit that I don't fully understand the implications of what > you describe. But I'm very happy to leave these decisions to you and > those that have a feeling of what the right thing to do is. Perhaps I should give some background. Gramps has two streams of development. Trunk, where we do the new development, and the branches, where we fix bugs. We make releases from a branch by tagging it. So taking the gramps31 branch as an example, the 3.1.3 release was done by tagging the latest version of each file in the branch with the 3.1.3 tag. The 3.1.2 release would have tagged a completely different set of earlier revisions of each file. I haven't looked yet but I bet the plugin download manager in Gramps will download the latest .tar.gz file for an addon by getting the latest version from the branch rather than getting it from a tagged release of the addon. So when we make a Gramps release from the gramps32, for example version 3.2.1, then we should extend the tagging process to gramps-addons so that we have a 3.2.1 version for each addon too which should be used with Gramps 3.2.1. Otherwise if we don't tag the addons, the concern is for a user who remains on Gramps 3.2.1 who might not be able to use the latest version of an addon because the addon depends on a bug fix that comes along in Gramps 3.2.5. Bye Gary |
From: Doug B. <dou...@gm...> - 2010-02-10 17:03:40
|
On Wed, Feb 10, 2010 at 11:31 AM, Gary Burton <bur...@ya...> wrote: > Hello Doug, > > >> > An open question: are we going to tag branches to make maintenance releases > >> like we do in the rest of Gramps? If we do then Gramps needs to be looking at >> the appropriate tagged Download directory to get a copy of the .tar.gz file for >> an addon. I guess right now that Gramps is looking at the Download directory in >> the branch and so will only pick up the latest revision of an addon for that >> branch. This might be a problem if the addon has a dependency on some >> functionality that only exists in a particular tagged version of Gramps. >> >> I must admit that I don't fully understand the implications of what >> you describe. But I'm very happy to leave these decisions to you and >> those that have a feeling of what the right thing to do is. > > Perhaps I should give some background. > > Gramps has two streams of development. Trunk, where we do the new development, and the branches, where we fix bugs. > > We make releases from a branch by tagging it. So taking the gramps31 branch as an example, the 3.1.3 release was done by tagging the latest version of each file in the branch with the 3.1.3 tag. The 3.1.2 release would have tagged a completely different set of earlier revisions of each file. > > I haven't looked yet but I bet the plugin download manager in Gramps will download the latest .tar.gz file for an addon by getting the latest version from the branch rather than getting it from a tagged release of the addon. So when we make a Gramps release from the gramps32, for example version 3.2.1, then we should extend the tagging process to gramps-addons so that we have a 3.2.1 version for each addon too which should be used with Gramps 3.2.1. > > Otherwise if we don't tag the addons, the concern is for a user who remains on Gramps 3.2.1 who might not be able to use the latest version of an addon because the addon depends on a bug fix that comes along in Gramps 3.2.5. > Gary, That helps; thanks! I'm not sure we will need this, nor do I know exactly how it would work if we could. Here is some background on the gramps-addons: All plugins are now tagged with plugin.gramps_target_version = "3.2". If that version number doesn't match const.VERSION_TUPLE[:2], then the plugin won't load. The idea is that this should help in making sure that plugins are matched with their right version of gramps over time. It may be that a plugin just needs to change the target version to "3.3" to allow it to work, but the assumption is that something will need to be updated. The page http://www.gramps-project.org/wiki/index.php?title=Plugins3.2 will have direct links to the tgz files, which the Plugin Manager reads from the wiki (currently, all in English---not sure what to do about that). So, I guess we may only need a subset of the features of SVN, but if it makes sense to use tags somehow, please feel free to adjust this process. Thanks again, -Doug > Bye > > Gary > > > > > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Benny M. <ben...@gm...> - 2010-02-11 09:08:56
|
2010/2/10 Doug Blank <dou...@gm...>: > On Wed, Feb 10, 2010 at 11:31 AM, Gary Burton <bur...@ya...> wrote: >> Hello Doug, >> >> >>> > An open question: are we going to tag branches to make maintenance releases >> >>> like we do in the rest of Gramps? If we do then Gramps needs to be looking at >>> the appropriate tagged Download directory to get a copy of the .tar.gz file for >>> an addon. I guess right now that Gramps is looking at the Download directory in >>> the branch and so will only pick up the latest revision of an addon for that >>> branch. This might be a problem if the addon has a dependency on some >>> functionality that only exists in a particular tagged version of Gramps. >>> >>> I must admit that I don't fully understand the implications of what >>> you describe. But I'm very happy to leave these decisions to you and >>> those that have a feeling of what the right thing to do is. >> >> Perhaps I should give some background. >> >> Gramps has two streams of development. Trunk, where we do the new development, and the branches, where we fix bugs. >> >> We make releases from a branch by tagging it. So taking the gramps31 branch as an example, the 3.1.3 release was done by tagging the latest version of each file in the branch with the 3.1.3 tag. The 3.1.2 release would have tagged a completely different set of earlier revisions of each file. >> >> I haven't looked yet but I bet the plugin download manager in Gramps will download the latest .tar.gz file for an addon by getting the latest version from the branch rather than getting it from a tagged release of the addon. So when we make a Gramps release from the gramps32, for example version 3.2.1, then we should extend the tagging process to gramps-addons so that we have a 3.2.1 version for each addon too which should be used with Gramps 3.2.1. >> >> Otherwise if we don't tag the addons, the concern is for a user who remains on Gramps 3.2.1 who might not be able to use the latest version of an addon because the addon depends on a bug fix that comes along in Gramps 3.2.5. >> > > Gary, > > That helps; thanks! I'm not sure we will need this, nor do I know > exactly how it would work if we could. Here is some background on the > gramps-addons: > > All plugins are now tagged with plugin.gramps_target_version = "3.2". > If that version number doesn't match const.VERSION_TUPLE[:2], then the > plugin won't load. The idea is that this should help in making sure > that plugins are matched with their right version of gramps over time. > It may be that a plugin just needs to change the target version to > "3.3" to allow it to work, but the assumption is that something will > need to be updated. > > The page http://www.gramps-project.org/wiki/index.php?title=Plugins3.2 > will have direct links to the tgz files, which the Plugin Manager > reads from the wiki (currently, all in English---not sure what to do > about that). > > So, I guess we may only need a subset of the features of SVN, but if > it makes sense to use tags somehow, please feel free to adjust this > process. > Yes, we should aim at plugins for 3.2.x series, not a specific point release. So all 3.2 plugins from latest plugins in 3.2 branch, not from the tag. It nevertheless might be usefull to be sure it is possible to have a plugin that works only with 3.2.5+, but then not by using tags in svn, but by using the mechanism in the gpr.py Doug describes. Doug, would it be possible to extend the version check to block 3.2.5 plugins in 3.2.4, or is this already present? Benny > Thanks again, > > -Doug > >> Bye >> >> Gary >> >> >> >> >> >> ------------------------------------------------------------------------------ >> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, >> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW >> http://p.sf.net/sfu/solaris-dev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Doug B. <dou...@gm...> - 2010-02-11 11:35:18
|
On Thu, Feb 11, 2010 at 4:08 AM, Benny Malengier <ben...@gm...> wrote: > 2010/2/10 Doug Blank <dou...@gm...>: >> On Wed, Feb 10, 2010 at 11:31 AM, Gary Burton <bur...@ya...> wrote: >>> Hello Doug, >>> >>> >>>> > An open question: are we going to tag branches to make maintenance releases >>> >>>> like we do in the rest of Gramps? If we do then Gramps needs to be looking at >>>> the appropriate tagged Download directory to get a copy of the .tar.gz file for >>>> an addon. I guess right now that Gramps is looking at the Download directory in >>>> the branch and so will only pick up the latest revision of an addon for that >>>> branch. This might be a problem if the addon has a dependency on some >>>> functionality that only exists in a particular tagged version of Gramps. >>>> >>>> I must admit that I don't fully understand the implications of what >>>> you describe. But I'm very happy to leave these decisions to you and >>>> those that have a feeling of what the right thing to do is. >>> >>> Perhaps I should give some background. >>> >>> Gramps has two streams of development. Trunk, where we do the new development, and the branches, where we fix bugs. >>> >>> We make releases from a branch by tagging it. So taking the gramps31 branch as an example, the 3.1.3 release was done by tagging the latest version of each file in the branch with the 3.1.3 tag. The 3.1.2 release would have tagged a completely different set of earlier revisions of each file. >>> >>> I haven't looked yet but I bet the plugin download manager in Gramps will download the latest .tar.gz file for an addon by getting the latest version from the branch rather than getting it from a tagged release of the addon. So when we make a Gramps release from the gramps32, for example version 3.2.1, then we should extend the tagging process to gramps-addons so that we have a 3.2.1 version for each addon too which should be used with Gramps 3.2.1. >>> >>> Otherwise if we don't tag the addons, the concern is for a user who remains on Gramps 3.2.1 who might not be able to use the latest version of an addon because the addon depends on a bug fix that comes along in Gramps 3.2.5. >>> >> >> Gary, >> >> That helps; thanks! I'm not sure we will need this, nor do I know >> exactly how it would work if we could. Here is some background on the >> gramps-addons: >> >> All plugins are now tagged with plugin.gramps_target_version = "3.2". >> If that version number doesn't match const.VERSION_TUPLE[:2], then the >> plugin won't load. The idea is that this should help in making sure >> that plugins are matched with their right version of gramps over time. >> It may be that a plugin just needs to change the target version to >> "3.3" to allow it to work, but the assumption is that something will >> need to be updated. >> >> The page http://www.gramps-project.org/wiki/index.php?title=Plugins3.2 >> will have direct links to the tgz files, which the Plugin Manager >> reads from the wiki (currently, all in English---not sure what to do >> about that). >> >> So, I guess we may only need a subset of the features of SVN, but if >> it makes sense to use tags somehow, please feel free to adjust this >> process. >> > > Yes, we should aim at plugins for 3.2.x series, not a specific point > release. So all 3.2 plugins from latest plugins in 3.2 branch, not > from the tag. > It nevertheless might be usefull to be sure it is possible to have a > plugin that works only with 3.2.5+, but then not by using tags in svn, > but by using the mechanism in the gpr.py Doug describes. > Doug, would it be possible to extend the version check to block 3.2.5 > plugins in 3.2.4, or is this already present? No, it doesn't currently work that way, but we could make it so that gramps_target_version = "3.2.5" would make sure that Gramps was 3.2.5 or higher. I'll add that to my list. -Doug > > Benny > >> Thanks again, >> >> -Doug >> >>> Bye >>> >>> Gary >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, >>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW >>> http://p.sf.net/sfu/solaris-dev2dev >>> _______________________________________________ >>> Gramps-devel mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>> >> >> ------------------------------------------------------------------------------ >> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, >> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW >> http://p.sf.net/sfu/solaris-dev2dev >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > |
From: Doug B. <dou...@gm...> - 2010-02-11 14:15:55
|
On Thu, Feb 11, 2010 at 6:35 AM, Doug Blank <dou...@gm...> wrote: > On Thu, Feb 11, 2010 at 4:08 AM, Benny Malengier > <ben...@gm...> wrote: >> 2010/2/10 Doug Blank <dou...@gm...>: >>> On Wed, Feb 10, 2010 at 11:31 AM, Gary Burton <bur...@ya...> wrote: >>>> Hello Doug, >>>> >>>> >>>>> > An open question: are we going to tag branches to make maintenance releases >>>> >>>>> like we do in the rest of Gramps? If we do then Gramps needs to be looking at >>>>> the appropriate tagged Download directory to get a copy of the .tar.gz file for >>>>> an addon. I guess right now that Gramps is looking at the Download directory in >>>>> the branch and so will only pick up the latest revision of an addon for that >>>>> branch. This might be a problem if the addon has a dependency on some >>>>> functionality that only exists in a particular tagged version of Gramps. >>>>> >>>>> I must admit that I don't fully understand the implications of what >>>>> you describe. But I'm very happy to leave these decisions to you and >>>>> those that have a feeling of what the right thing to do is. >>>> >>>> Perhaps I should give some background. >>>> >>>> Gramps has two streams of development. Trunk, where we do the new development, and the branches, where we fix bugs. >>>> >>>> We make releases from a branch by tagging it. So taking the gramps31 branch as an example, the 3.1.3 release was done by tagging the latest version of each file in the branch with the 3.1.3 tag. The 3.1.2 release would have tagged a completely different set of earlier revisions of each file. >>>> >>>> I haven't looked yet but I bet the plugin download manager in Gramps will download the latest .tar.gz file for an addon by getting the latest version from the branch rather than getting it from a tagged release of the addon. So when we make a Gramps release from the gramps32, for example version 3.2.1, then we should extend the tagging process to gramps-addons so that we have a 3.2.1 version for each addon too which should be used with Gramps 3.2.1. >>>> >>>> Otherwise if we don't tag the addons, the concern is for a user who remains on Gramps 3.2.1 who might not be able to use the latest version of an addon because the addon depends on a bug fix that comes along in Gramps 3.2.5. >>>> >>> >>> Gary, >>> >>> That helps; thanks! I'm not sure we will need this, nor do I know >>> exactly how it would work if we could. Here is some background on the >>> gramps-addons: >>> >>> All plugins are now tagged with plugin.gramps_target_version = "3.2". >>> If that version number doesn't match const.VERSION_TUPLE[:2], then the >>> plugin won't load. The idea is that this should help in making sure >>> that plugins are matched with their right version of gramps over time. >>> It may be that a plugin just needs to change the target version to >>> "3.3" to allow it to work, but the assumption is that something will >>> need to be updated. >>> >>> The page http://www.gramps-project.org/wiki/index.php?title=Plugins3.2 >>> will have direct links to the tgz files, which the Plugin Manager >>> reads from the wiki (currently, all in English---not sure what to do >>> about that). >>> >>> So, I guess we may only need a subset of the features of SVN, but if >>> it makes sense to use tags somehow, please feel free to adjust this >>> process. >>> >> >> Yes, we should aim at plugins for 3.2.x series, not a specific point >> release. So all 3.2 plugins from latest plugins in 3.2 branch, not >> from the tag. >> It nevertheless might be usefull to be sure it is possible to have a >> plugin that works only with 3.2.5+, but then not by using tags in svn, >> but by using the mechanism in the gpr.py Doug describes. >> Doug, would it be possible to extend the version check to block 3.2.5 >> plugins in 3.2.4, or is this already present? > > No, it doesn't currently work that way, but we could make it so that > gramps_target_version = "3.2.5" would make sure that Gramps was 3.2.5 > or higher. I'll add that to my list. Done. 1-point target version numbers (eg, "3.2") must match the corresponding gramps 1-point version exactly. That is, a plugin with gramps_target_version of "3.2" will not run under Gramps 3.3. On the other hand, 2-point target version numbers must be equal or less than the gramps version number. A plugin with gramps_target_version of "3.2.1" will work with Gramps 3.2.1, 3.2.2, on up (but not with Gramps 3.2.0 or 3.3.x). -Doug > > -Doug > >> >> Benny >> >>> Thanks again, >>> >>> -Doug >>> >>>> Bye >>>> >>>> Gary >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, >>>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW >>>> http://p.sf.net/sfu/solaris-dev2dev >>>> _______________________________________________ >>>> Gramps-devel mailing list >>>> Gra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>>> >>> >>> ------------------------------------------------------------------------------ >>> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, >>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW >>> http://p.sf.net/sfu/solaris-dev2dev >>> _______________________________________________ >>> Gramps-devel mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>> >> > |