Hi all,
>From discussions elsewhere, such as [1], it sounds like one of the
things holding back Geany development right now is a need for more
testing.
I have some spare time that I can dedicate to exploratory testing of
PRs to Geany and Geany-Plugins. I'm not a QA professional, but I am a
programmer, I use a range of Geany features daily, and I understand
Geany's code.
How can I test PRs in a way that would really help them get merged?
In particular:
1. How can I determine that a PR is mostly blocked on testing, and is
likely to be merged when positive testing results come in? Some PRs
are marked as "approved" in GitHub yet are not merged -- is that it?
2. How can I communicate my results to the satisfaction of Geany
committers? For example, I could write up some kind of a report: an
outline of what I tried, with screenshots of what I got -- would that
help?
Thank you.
[1] https://github.com/geany/geany/pull/1246#issuecomment-290047712
--
Vasiliy
I forward this mail to the devs list since nobody is accepting me for the
users one :(
---------- Forwarded message ----------
From: Abel <akronix5(a)gmail.com>
Date: 23 June 2017 at 11:20
Subject: Updating Geany doesn't update user's filetypes files
To: Geany general discussion list <users(a)lists.geany.org>
Hi.
I've recently updated Geany from 1.29 to 1.30.1 through the unofficial ppa
<https://launchpad.net/%7Egeany-dev/+archive/ubuntu/ppa>, Geany seems to be
updated correctly but the filetypes configuration files located in
~/.config/geany/filedefs haven't got updated whereas
/usr/share/geany/filedefs has.
How can I get my local user config files updated as well when updating
Geany? Is there any automatic way?
*Greetings,*
* Abel.*
Hi translators,
You know it: As Geany is getting a new major release, the plugins are
getting updated too. This time: 1.31.
In preparation I have updated the po-files for Geany-Plugins at github
and asking you whether you could update translations, review them or
maybe add new languages.
As on Geany core, I'd be very happy if you could send a patch, a pull
request or single file with translation to either the geany-i18n mailing
list or direct to me within the next week so we can include it to
the next release. Deadline will be also 2017-07-07 CET.
To get most recent files you could just clone the repositories from
Geany: https://github.com/geany/geany-plugins
This can be done e.g. with
git clone https://github.com/geany/geany-plugins.git
Also at http://i18n.geany.org/plugins are statistics and daily updated
files available.
If you have any questions, don't hesitate to ping me directly via
IRC: geany @freenode (frlan)
Jabber/XMPP: frlan(a)jabber.ccc.de
or via Mail: look above or some of the mailing lists.
Happy translating!
Cheers,
Frank
Dear translators and friends of Geany,
We are on the final meters for Geany 1.31.
In preparation I've updated po-files for Geany core project
inside github repositories and asking you whether you could update
translations, review them or maybe add new languages.
I'd be very happy if you could send a patch, a pull request or single
file with translation to either the geany-i18n mailing list or direct
to me within the next week so we can include it to the next
release. Deadline will be 2017-07-07 24:00hCET.
To get most recent files you could just clone the repositories from
Geany: https://github.com/geany/geany
This can be done e.g. with
git clone https://github.com/geany/geany.git
You can find daily updated po files at http://i18n.geany.org too, which
includes some statistics.
If your language was translated by two or more in past, please double
check directly with them or by pinging me, so we don't need to
translate same things two or three times. Also please feel to ping me
for every question or if you like to start a new translation for an
unsupported language.
If you have any questions, don't hesitate to ping me directly via
IRC: geany @freenode
Jabber/XMPP: frlan(a)jabber.ccc.de
or via Mail: look above or some of the mailing lists.
Thanks and happy translating
Frank
Hi plugin maintainer, fans and users,
In about three weeks we are planning to release the next release of
Geany as well as the geany-plugins (2017-07-08). Now it's good time to
review open pr requests whether they can be merged into the release.
Please be so kind and check
https://github.com/geany/geany-plugins/pulls
for pull requests related to "your" plugin.
Of course, you can also have a look at
https://github.com/geany/geany-plugins/issues
whether there is some low hanging fruit last minute fix possible ;)
Schedule:
* Upcoming weekend (~2017-06-25) string freeze
* 2017-07-07 deadline for translations
* 2017-07-08 release
It would be awesome if we can build a new and again great release
together ;)
Cheers,
Frank
Hi all,
I got a simple question:
As I understood from the development manual plugins should use
geany_load_module()
<http://www.geany.org/manual/reference/plugindata_8h.html#ab164d92669f69e393…>
instead of plugin_init()...
Is that correct?
I am just wondering because it seems that 90% of the geany plugins use
plugin_init() and co.
Kind Regards,
Lars