Hi plugin developers,
Frank and I were discussing on #geany the other day about whether we should have an 0.18 release of geany-plugins soon (or wait for the next Geany). From what I see, there are some significant changes which would probably warrant a release, including the addition of two new plugins (codenav and pretty-print) and one existing plugin (geanydoc) to the common geany plugins project.
Some input from all plugin developers regarding this would be nice.
Another somewhat related issue is that if we do not release a new version, we're going to at least have to rebuild the Windows plugins so that they work with the new Geany.
On Fri, 04 Sep 2009 20:44:54 +0800, Chow wrote:
Hi plugin developers,
Frank and I were discussing on #geany the other day about whether we should have an 0.18 release of geany-plugins soon (or wait for the next Geany). From what I see, there are some significant changes which would probably warrant a release, including the addition of two new plugins (codenav and pretty-print) and one existing plugin (geanydoc) to the common geany plugins project.
Some input from all plugin developers regarding this would be nice.
Another somewhat related issue is that if we do not release a new version, we're going to at least have to rebuild the Windows plugins so that they work with the new Geany.
I'd vote for a new geany-plugins 0.18 release.
Could you open a new branch for the 0.18 release, then I could apply Eugene's whitespace patch to trunk which will require Geany 0.19 as it depends on some API additions.
Regards, Enrico
On Sun, 6 Sep 2009 14:44:25 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
Frank and I were discussing on #geany the other day about whether we should have an 0.18 release of geany-plugins soon (or wait for the next Geany). From what I see, there are some significant changes which would probably warrant a release, including the addition of two new plugins (codenav and pretty-print) and one existing plugin (geanydoc) to the common geany plugins project.
...
I'd vote for a new geany-plugins 0.18 release.
Yep, sounds good.
Could you open a new branch for the 0.18 release, then I could apply Eugene's whitespace patch to trunk which will require Geany 0.19 as it depends on some API additions.
I think the branch will have to be created from an older version of trunk anyway as geanylua uses the 0.19 API already.
Regards, Nick
On Mon, 7 Sep 2009 12:51:25 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Could you open a new branch for the 0.18 release, then I could apply Eugene's whitespace patch to trunk which will require Geany 0.19 as it depends on some API additions.
I think the branch will have to be created from an older version of trunk anyway as geanylua uses the 0.19 API already.
One option would be to just copy the 0.17.1 branch to an 0.18 branch (the 0.18 API *should* be compatible with 0.17). Then plugin authors can merge any updated code they want for 0.18, and it avoids any problems with 0.19-dependent code (although maybe there's not much of that).
Regards, Nick
On Mon, 7 Sep 2009 13:00:58 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Mon, 7 Sep 2009 12:51:25 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Could you open a new branch for the 0.18 release, then I could apply Eugene's whitespace patch to trunk which will require Geany 0.19 as it depends on some API additions.
I think the branch will have to be created from an older version of trunk anyway as geanylua uses the 0.19 API already.
One option would be to just copy the 0.17.1 branch to an 0.18 branch (the 0.18 API *should* be compatible with 0.17). Then plugin authors can merge any updated code they want for 0.18, and it avoids any problems with 0.19-dependent code (although maybe there's not much of that).
I think this should work.
Cheers, Frank
On Mon, 7 Sep 2009 13:00:58 +0100, Nick wrote:
On Mon, 7 Sep 2009 12:51:25 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Could you open a new branch for the 0.18 release, then I could apply Eugene's whitespace patch to trunk which will require Geany 0.19 as it depends on some API additions.
I think the branch will have to be created from an older version of trunk anyway as geanylua uses the 0.19 API already.
One option would be to just copy the 0.17.1 branch to an 0.18 branch (the 0.18 API *should* be compatible with 0.17). Then plugin authors can merge any updated code they want for 0.18, and it avoids any problems with 0.19-dependent code (although maybe there's not much of that).
Sounds like a plan. Chow, do you agree?
Regards, Enrico
On Tue, 08 Sep 2009 08:15:41 +0800 Chow Loong Jin hyperair@gmail.com wrote:
Sounds like a plan. Chow, do you agree?
It sounds good to me. Who's creating the branch then? :-)
Please go ahead, I'm planning on not creating any branches other than for my own work because I have an old svn version ;-)
Regards, Nick
On Tue, 08 Sep 2009 08:15:41 +0800 Chow Loong Jin hyperair@gmail.com wrote:
On Tuesday 08,September,2009 05:49 AM, Enrico Tröger wrote:
Sounds like a plan. Chow, do you agree?
It sounds good to me. Who's creating the branch then? :-)
As there was nothing happening, I created it with svn r929.
Happy merging.
Cheers, Frank