Hi all,
We're happy to announce a new release of Geany Plugins, 0.18. Below is a shortlog of all the changes since 0.17.1:-
eht16 (16): Attempt to fix crashes when quitting Geany from the system tray icon. ChangeLog updated :-) Fix wrong indentation level Avoid using GHashTable functions from newer GLib versions to fix compilation with GLib 2.8. Fix version number We need the dot for proper building (e.g. on Windows). Merge changes from trunk Merge changes from trunk: Allow setting a custom dictionary directory without reloading the plugin. Add an option to the preference dialog to select a custom directory to look for additional dictionary files. Minor fixes. Remove unused code. Use single header includes. Update NEWS Fix wrong cast for Geany 0.18 Add readme file for Windows mentioning the included binaries Update outdated information Update outdated information Install README.windows Beautify the filename Update for 0.18, install plugin dependencies as well
frlan (13): Backport bugfix for geanyLaTeX toolbar to 0.17.1 tree Update some of the documentation files to avoid empty files. Closes #2823235 Backport some of updated translation to 0.17.1 branch Create branch for 0.18 tree Update of version strings and set minimum depedency for Geany to 0.18 Update of documentation Update missed css file Update geanyvc to current devel version for 0.18 release Update NEWS file a bit GeanyVC: Fix a tooltip Set binary flag for geanyLaTeX's documentation PDF GeanyLaTeX: Also replace capital German Umlauts. Update/Backport of translations for 0.18 release
hyperair (14): Correct typo: COMMON_LIBS => COMMONLIBS Move ttyhelper to $libexecdir/geany-plugins/geanygdb Tag geany-plugins-0.17.1 release Bump version in configure.ac Bump version in configure.ac Bump versions in wscript and .nsi Create tag geany-plugins-0.17.1 Port build system updates from trunk Turn on automake silent rules if supported Correct typo geadydoc => geanydoc Include waf files into the tarball Add README for autotools Correct typo and spelling errors in README Add missing files to POTFILES.in
ntrel (4): Create 0.17.1 bugfix branch copied from the 0.17 release. Fixes from trunk. Add NEWS from trunk. Minor reformatting.
yurand (2): Added geanyprj and geanydoc plugins Don't use gettext for empty string
On Wed, 28 Oct 2009 08:10:00 +0800 Chow Loong Jin hyperair@gmail.com wrote:
Hi all,
We're happy to announce a new release of Geany Plugins, 0.18.
Great! Now we can release Geany 0.19 ;-) (SCNR)
Below is a shortlog of all the changes since 0.17.1:-
Hmm, it's a bit ugly and long, perhaps the NEWS file would be better. Only I'm not sure if all committers updated it...
If anyone who didn't update NEWS wants to reply with any short descriptions of their changes I'll update the website news entry.
Regards, Nick
P.S. Anyway thanks Chow, it's great we get combined plugins releases now :)
On Wednesday 28,October,2009 06:47 PM, Nick Treleaven wrote:
Great! Now we can release Geany 0.19 ;-) (SCNR)
Heheh yeah. ;-)
Below is a shortlog of all the changes since 0.17.1:-
Hmm, it's a bit ugly and long, perhaps the NEWS file would be better. Only I'm not sure if all committers updated it...
I fully agree. However, the NEWS wasn't completely updated when the branch was tagged (a fault on my part as well -- I forgot to set the date in the latest NEWS entry).
[...] P.S. Anyway thanks Chow, it's great we get combined plugins releases now :)
Pleasure's all mine. =)
Am Mittwoch, den 28.10.2009, 10:47 +0000 schrieb Nick Treleaven:
On Wed, 28 Oct 2009 08:10:00 +0800 Chow Loong Jin hyperair@gmail.com wrote:
Hi all,
We're happy to announce a new release of Geany Plugins, 0.18.
Great! Now we can release Geany 0.19 ;-) (SCNR)
Below is a shortlog of all the changes since 0.17.1:-
Hmm, it's a bit ugly and long, perhaps the NEWS file would be better. Only I'm not sure if all committers updated it...
If anyone who didn't update NEWS wants to reply with any short descriptions of their changes I'll update the website news entry.
Hi,
got some additional changes of GeanyGDB: * now remembers the path of the target binary within a session (it wouldn't remember if you restart Geany) * fixed handling of whitespaces in target path (closes #2883366)
Sorry I forgot to update the NEWS file.
Regards, Dominic
On Wed, 28 Oct 2009 18:03:28 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
We're happy to announce a new release of Geany Plugins, 0.18.
...
Hmm, it's a bit ugly and long, perhaps the NEWS file would be better. Only I'm not sure if all committers updated it...
If anyone who didn't update NEWS wants to reply with any short descriptions of their changes I'll update the website news entry.
Hi,
got some additional changes of GeanyGDB:
- now remembers the path of the target binary within a session (it
wouldn't remember if you restart Geany)
- fixed handling of whitespaces in target path (closes #2883366)
AFAICT these changes don't seem to be in the 0.18 release: http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/branches/geany...
The release wasn't made from trunk.
Sorry I forgot to update the NEWS file.
No problem, it's fairly recent, I probably should have reminded everyone.
Regards, Nick
On Wed, 28 Oct 2009 21:06:28 +0800 Chow Loong Jin hyperair@gmail.com wrote:
Below is a shortlog of all the changes since 0.17.1:-
Hmm, it's a bit ugly and long, perhaps the NEWS file would be better. Only I'm not sure if all committers updated it...
I fully agree. However, the NEWS wasn't completely updated when the branch was tagged (a fault on my part as well -- I forgot to set the date in the latest NEWS entry).
No problem, I should have reminded everyone to update it.
I just merged and edited the NEWS file in trunk and updated the website news item.
Regards, Nick
On Fri, 30 Oct 2009 12:25:08 +0000 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Wed, 28 Oct 2009 18:03:28 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
We're happy to announce a new release of Geany Plugins, 0.18.
...
Hmm, it's a bit ugly and long, perhaps the NEWS file would be better. Only I'm not sure if all committers updated it...
If anyone who didn't update NEWS wants to reply with any short descriptions of their changes I'll update the website news entry.
Hi,
got some additional changes of GeanyGDB:
- now remembers the path of the target binary within a session (it
wouldn't remember if you restart Geany)
- fixed handling of whitespaces in target path (closes #2883366)
AFAICT these changes don't seem to be in the 0.18 release: http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/branches/geany...
I think things like this are caused by the confusion with merging stuff here. I suggest to really use trunk in future as basis for a branch whenever a new release should be done.
Cheers, Frank
On Fri, 30 Oct 2009 13:51:18 +0100 Frank Lanitz frank@frank.uvena.de wrote:
I think things like this are caused by the confusion with merging stuff here. I suggest to really use trunk in future as basis for a branch whenever a new release should be done.
Only if the release is to be made at the same time as Geany, otherwise trunk may not be compatible with the most recent version of Geany. That would be worse than not having the latest changes.
Regards, Nick
Am Freitag, den 30.10.2009, 13:51 +0100 schrieb Frank Lanitz:
On Fri, 30 Oct 2009 12:25:08 +0000 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Wed, 28 Oct 2009 18:03:28 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
We're happy to announce a new release of Geany Plugins, 0.18.
...
Hmm, it's a bit ugly and long, perhaps the NEWS file would be better. Only I'm not sure if all committers updated it...
If anyone who didn't update NEWS wants to reply with any short descriptions of their changes I'll update the website news entry.
Hi,
got some additional changes of GeanyGDB:
- now remembers the path of the target binary within a session (it
wouldn't remember if you restart Geany)
- fixed handling of whitespaces in target path (closes #2883366)
AFAICT these changes don't seem to be in the 0.18 release: http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/branches/geany...
Thanks Frank. Concerning to this link the changes definitely are in Geany-Plugins 0.18. The last change I made concerning the mentioned issues above was revision 916. The branch was created from 929. So everything should be fine. :)
Regards, Dominic
On Sat, 31 Oct 2009 11:48:33 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
AFAICT these changes don't seem to be in the 0.18 release: http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/branches/geany...
Thanks Frank. Concerning to this link the changes definitely are in Geany-Plugins 0.18. The last change I made concerning the mentioned issues above was revision 916. The branch was created from 929. So everything should be fine. :)
OK, but there were no changes since 0.17.1, right?
Regards, Nick
Am Montag, den 02.11.2009, 11:48 +0000 schrieb Nick Treleaven:
On Sat, 31 Oct 2009 11:48:33 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
AFAICT these changes don't seem to be in the 0.18 release: http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/branches/geany...
Thanks Frank. Concerning to this link the changes definitely are in Geany-Plugins 0.18. The last change I made concerning the mentioned issues above was revision 916. The branch was created from 929. So everything should be fine. :)
OK, but there were no changes since 0.17.1, right?
Since the 0.17.1 release got tagged in revision 863 (at least if [1] is right) the above mentioned changes actually are changes between 0.17.1 and 0.18. Seems I've really missed to mention those changes somewhere else? :s
Regs, Dominic
[1] http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/tags/geany-plu...
On Mon, 02 Nov 2009 21:29:40 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
AFAICT these changes don't seem to be in the 0.18 release: http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/branches/geany...
Thanks Frank. Concerning to this link the changes definitely are in Geany-Plugins 0.18. The last change I made concerning the mentioned issues above was revision 916. The branch was created from 929. So everything should be fine. :)
OK, but there were no changes since 0.17.1, right?
Since the 0.17.1 release got tagged in revision 863 (at least if [1] is right) the above mentioned changes actually are changes between 0.17.1 and 0.18. Seems I've really missed to mention those changes somewhere else? :s
I may be being dumb, but I can't find these changes in the 0.18 release.
The 0.18 branch IIUC was not created from trunk, but just copied from the 0.17.1 tag.
Regards, Nick
On Wed, 4 Nov 2009 15:46:23 +0000, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Mon, 02 Nov 2009 21:29:40 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
AFAICT these changes don't seem to be in the 0.18 release:
http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/branches/geany...
Thanks Frank. Concerning to this link the changes definitely are in Geany-Plugins 0.18. The last change I made concerning the mentioned issues above was revision 916. The branch was created from 929. So everything should be fine. :)
OK, but there were no changes since 0.17.1, right?
Since the 0.17.1 release got tagged in revision 863 (at least if [1] is right) the above mentioned changes actually are changes between 0.17.1 and 0.18. Seems I've really missed to mention those changes somewhere else? :s
I may be being dumb, but I can't find these changes in the 0.18 release.
The 0.18 branch IIUC was not created from trunk, but just copied from the 0.17.1 tag.
100% correct, which was crap to be honest.
Cheers, FRank
Am Mittwoch, den 04.11.2009, 15:46 +0000 schrieb Nick Treleaven:
On Mon, 02 Nov 2009 21:29:40 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
AFAICT these changes don't seem to be in the 0.18 release: http://geany-plugins.svn.sourceforge.net/viewvc/geany-plugins/branches/geany...
Thanks Frank. Concerning to this link the changes definitely are in Geany-Plugins 0.18. The last change I made concerning the mentioned issues above was revision 916. The branch was created from 929. So everything should be fine. :)
OK, but there were no changes since 0.17.1, right?
Since the 0.17.1 release got tagged in revision 863 (at least if [1] is right) the above mentioned changes actually are changes between 0.17.1 and 0.18. Seems I've really missed to mention those changes somewhere else? :s
I may be being dumb, but I can't find these changes in the 0.18 release.
No, you aren't.
The 0.18 branch IIUC was not created from trunk, but just copied from the 0.17.1 tag.
This is exactly the point I didn't knew. I thought it was created from trunk and my changes were included. I've missed reading the mail were it was mentioned I would have to merge the changes myself into the branch. If this is the correct way for a releasing procedure is another question anyway.
You're right then, my changes are not included in the 0.18 release. I'm very sorry for the confusion.
Before doing the next release we should talk about the releasing procedure again and maybe write that down as some kind of releasing guidelines, so that confused guys like me won't miss those... ;)
Regards, Dominic
On Wed, 04 Nov 2009 17:08:03 +0100 Dominic Hopf dmaphy@googlemail.com wrote:
The 0.18 branch IIUC was not created from trunk, but just copied from the 0.17.1 tag.
This is exactly the point I didn't knew. I thought it was created from trunk and my changes were included. I've missed reading the mail were it was mentioned I would have to merge the changes myself into the branch. If this is the correct way for a releasing procedure is another question anyway.
You're right then, my changes are not included in the 0.18 release. I'm very sorry for the confusion.
No problem ;-)
Before doing the next release we should talk about the releasing procedure again and maybe write that down as some kind of releasing guidelines, so that confused guys like me won't miss those... ;)
OK, sorry we weren't clearer at the time. I hope we can synchronize releases with Geany in future then we could create the branch from/release trunk. This probably should be discussed.
Regards, Nick
Hi,
On Fri, 30 Oct 2009 12:52:30 +0000 Nick Treleaven nick.treleaven@btinternet.com wrote:
On Fri, 30 Oct 2009 13:51:18 +0100 Frank Lanitz frank@frank.uvena.de wrote:
I think things like this are caused by the confusion with merging stuff here. I suggest to really use trunk in future as basis for a branch whenever a new release should be done.
Only if the release is to be made at the same time as Geany, otherwise trunk may not be compatible with the most recent version of Geany. That would be worse than not having the latest changes.
I'm ot sure whether we should discuss all possibilities which might can happen, but of course you are 100% right here - creating release from trunk will not be possible easily in such cases anymore.
Cheers, Frank