Hi,
Does anyone have any opinions about me putting GeanyPy into geany-plugins SVN and trying to get it included in the next plugins release?
Also, roughly what is the release date of Geany-Plugins?
Cheers, Matthew Brush
On 18 September 2011 12:55, Matthew Brush mbrush@codebrainz.ca wrote:
Hi,
Does anyone have any opinions about me putting GeanyPy into geany-plugins SVN and trying to get it included in the next plugins release?
Also, roughly what is the release date of Geany-Plugins?
Since ABI hasn't changed old plugins should still work (check before release?) so it doesn't have to be concurrent.
Should be reasonably soon though to try to get it into the same round of distro releases if possible.
I think someone mentioned about a month later.
Cheers Lex
Cheers, Matthew Brush _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Sun, 18 Sep 2011 13:35:13 +1000 Lex Trotman elextr@gmail.com wrote:
I think someone mentioned about a month later.
Goal is weekend around Oct, 15th.
Cheers, Frank
On 18 September 2011 12:55, Matthew Brush mbrush@codebrainz.ca wrote:
Hi,
Does anyone have any opinions about me putting GeanyPy into geany-plugins SVN and trying to get it included in the next plugins release?
Also, roughly what is the release date of Geany-Plugins?
Since ABI hasn't changed old plugins should still work (check before release?) so it doesn't have to be concurrent.
Should be reasonably soon though to try to get it into the same round of distro releases if possible.
I think someone mentioned about a month later.
Cheers Lex
Cheers, Matthew Brush _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Le 18/09/2011 04:55, Matthew Brush a écrit :
Hi,
Hey,
Does anyone have any opinions about me putting GeanyPy into geany-plugins SVN and trying to get it included in the next plugins release?
It depends on whether GeanPy can be/is considered stable or not. If it is, I see no reason why it couldn't be in geany-plugins; but if it isn't I better wait until it becomes before releasing it as part of GP (GP-released plugins are supposed to be production-ready).
My POV *as somebody that never actually tried it* is that GeanyPy is still a bit young and that it's likely to need some incompatible changes for it to evolve. But again, I haven't developed it, and I haven't even tried to write a plugin using it yet, I only seen examples and discussions.
So... my 2¢, use them the best you can ;)
Cheers, Colomban
On 20 September 2011 00:19, Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 18/09/2011 04:55, Matthew Brush a écrit :
Hi,
Hey,
Does anyone have any opinions about me putting GeanyPy into geany-plugins SVN and trying to get it included in the next plugins release?
Hmmm, by next I thought you meant 0.22 which would be fine, but it shouldn't be added just weeks before the 0.21 release.
Add it after the 0.21 plugins release when there is plenty of time to settle it in.
Cheers Lex
On 09/19/2011 03:23 PM, Lex Trotman wrote:
On 20 September 2011 00:19, Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 18/09/2011 04:55, Matthew Brush a écrit :
Hi,
Hey,
Does anyone have any opinions about me putting GeanyPy into geany-plugins SVN and trying to get it included in the next plugins release?
Hmmm, by next I thought you meant 0.22 which would be fine, but it shouldn't be added just weeks before the 0.21 release.
Add it after the 0.21 plugins release when there is plenty of time to settle it in.
Well, what I really meant was copy the "stable" (heh) code from my Git repo to geany-plugins SVN for release. Like geany-themes which I've been waiting until this release to patch Geany, will now not get in because it's too late.
Unlike geany-themes, which is quite widely used and ready for release (IMO), I'm not 100% sure about GeanyPy, so I will not even attempt to make it "releasable" just yet.
I keep these things in Git because SVN sucks and I don't have commit access to geany core (for geany-themes). If I sent a patch for geany-themes earlier, I would have to maintain it in two places.
Cheers, Matthew Brush
On 20 September 2011 09:07, Matthew Brush mbrush@codebrainz.ca wrote:
On 09/19/2011 03:23 PM, Lex Trotman wrote:
On 20 September 2011 00:19, Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 18/09/2011 04:55, Matthew Brush a écrit :
Hi,
Hey,
Does anyone have any opinions about me putting GeanyPy into geany-plugins SVN and trying to get it included in the next plugins release?
Hmmm, by next I thought you meant 0.22 which would be fine, but it shouldn't be added just weeks before the 0.21 release.
Add it after the 0.21 plugins release when there is plenty of time to settle it in.
Well, what I really meant was copy the "stable" (heh) code from my Git repo to geany-plugins SVN for release. Like geany-themes which I've been waiting until this release to patch Geany, will now not get in because it's too late.
Unlike geany-themes, which is quite widely used and ready for release (IMO),
I don't know anybody disagreed about themes, why havn't you sent them (or a pull request)?
I'm not 100% sure about GeanyPy, so I will not even attempt to make it "releasable" just yet.
Yeah, add it immediately after 0.21 plugins release then lots of people can break (erm I mean test) it for you before the next release.
I keep these things in Git because SVN sucks and I don't have commit access to geany core (for geany-themes). If I sent a patch for geany-themes earlier, I would have to maintain it in two places.
Yes, well that is always going to be a problem for anyone without commit access, maybe themes need to be in a separate place like geany-plugins so multiple people can maintain them but they still get included in the release?
Cheers Lex
On 09/19/2011 04:38 PM, Lex Trotman wrote:
On 20 September 2011 09:07, Matthew Brushmbrush@codebrainz.ca wrote:
I keep these things in Git because SVN sucks and I don't have commit access to geany core (for geany-themes). If I sent a patch for geany-themes earlier, I would have to maintain it in two places.
Yes, well that is always going to be a problem for anyone without commit access, maybe themes need to be in a separate place like geany-plugins so multiple people can maintain them but they still get included in the release?
Github works pretty well for this, I'm not stingy with commit access and I'll add anyone as a contributor, or the Pull Requests works quite easily.
IMO geany-themes doesn't really belong in geany-plugins. The filedefs belong in Geany like Nick asked for some time ago. IMO they should be in the next release so people can sanely write colour schemes using the features that were previously implemented but the filedefs were never updated. The colour schemes themselves (besides maybe a few "core" ones), belong in a separate project (ie. geany-themes on GitHub) or on gnome-look or some such site.
Cheers, Matthew Brush
On Mon, 19 Sep 2011 17:03:10 -0700 Matthew Brush mbrush@codebrainz.ca wrote:
Github works pretty well for this, I'm not stingy with commit access and I'll add anyone as a contributor, or the Pull Requests works quite easily.
After 0.21 there will be some changes on both side, Geany as well as Geany-plugins. I will send a mail how I can imagine on how the plugins flow will work after 0.21 later.
On Mon, 19 Sep 2011 16:19:30 +0200 Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 18/09/2011 04:55, Matthew Brush a écrit :
Hi,
Hey,
Does anyone have any opinions about me putting GeanyPy into geany-plugins SVN and trying to get it included in the next plugins release?
It depends on whether GeanPy can be/is considered stable or not. If it is, I see no reason why it couldn't be in geany-plugins; but if it isn't I better wait until it becomes before releasing it as part of GP (GP-released plugins are supposed to be production-ready).
My POV *as somebody that never actually tried it* is that GeanyPy is still a bit young and that it's likely to need some incompatible changes for it to evolve. But again, I haven't developed it, and I haven't even tried to write a plugin using it yet, I only seen examples and discussions.
In difference I gave it a try and I liked it, but I would disagree to put it into geany-plugins 0.21 as it will be feature/string freeze upcoming week and time to get it settled is a bit low IMHO.
Cheers, Frank