[Geany-devel] GeanyPy in next plugin release

Lex Trotman elextr at xxxxx
Mon Sep 19 23:38:26 UTC 2011

On 20 September 2011 09:07, Matthew Brush <mbrush at codebrainz.ca> wrote:
> On 09/19/2011 03:23 PM, Lex Trotman wrote:
>> On 20 September 2011 00:19, Colomban Wendling
>> <lists.ban at 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?


More information about the Devel mailing list