Re: [Geany-devel] How about calling the next release 1.0?
On Tue, Sep 20, 2011 at 13:02, Lex Trotman ele...@gmail.com wrote: On 20 September 2011 20:14, Jon Senior j...@restlesslemon.co.uk wrote: On Tue, 20 Sep 2011 12:07:23 +0200 Jiří Techet tec...@gmail.com wrote: Hi, just one very quick and possibly stupid idea. How about getting rid of the 0 version prefix and calling the next release 1.0? This would be just numbering change, not some milestone based on features that have to be implemented (similarly to renumbering linux kernel from 2.6.x to 3.0). Rationale: the 0.xx versioning scheme makes an impression that Geany is something very unstable that crashes every five minutes and whose first release was made a few months back. Instead, Geany is a very stable and reliable editor with lots of features and several years of history. I agree with this argument, I tend to introduce Geany anywhere I have a contract and one of the first reactions is always But its just a fractional version number. And I know when I am looking for software I want to use I tend to have the same reaction. Following the Kernels example and going to 1.0 or better yet 1.1 would be a good idea. And it is likely to attract more contributors since it doesn't look like the project is just starting. Or 1.21 - i.e. raise the stability flag in the first digit but continue with current numbering after the dot. The message would be we consider Geany stable but the current release is just an incremental release. Cheers, Jiri ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] How about calling the next release 1.0?
Le 20/09/2011 23:26, Enrico Tröger a écrit : On Tue, 20 Sep 2011 16:10:34 +0300, Yura wrote: Hi But why only 1.0? GNOME 3.* KDE 4.* Scite 2.* What about Geany 3000? Or some kind of other stupid release name like ''busel', 'verabei', 'krumkach' ... Heh, I like krumkach, sounds in German quite funny :). BTW, how are Geany codenames chosen? :-' More seriously, I personally don't mind much about version numbers. It's good to have some but the actual value doesn't mean much to me. But I realise other people take more care about this and 0.x might seem not that mature to many users. So, I'd say: why not. I'd say quite the same. I don't really mind, and it seems it's something important for many of you so... Regards, Colomban ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] How about calling the next release 1.0?
Am 22.09.2011 15:28, schrieb Colomban Wendling: Le 20/09/2011 23:26, Enrico Tröger a écrit : On Tue, 20 Sep 2011 16:10:34 +0300, Yura wrote: Hi But why only 1.0? GNOME 3.* KDE 4.* Scite 2.* What about Geany 3000? Or some kind of other stupid release name like ''busel', 'verabei', 'krumkach' ... Heh, I like krumkach, sounds in German quite funny :). BTW, how are Geany codenames chosen? :-' More seriously, I personally don't mind much about version numbers. It's good to have some but the actual value doesn't mean much to me. But I realise other people take more care about this and 0.x might seem not that mature to many users. So, I'd say: why not. I'd say quite the same. I don't really mind, and it seems it's something important for many of you so... But can we do it post 0.21? Only one week left and I want to concentrate on improving translation etc. instead of searchreplace version numbers. Cheers, Frank ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] How about calling the next release 1.0?
On Thu, 22 Sep 2011 15:28:21 +0200 Colomban Wendling lists@herbesfolles.org wrote: What about Geany 3000? Or some kind of other stupid release name like ''busel', 'verabei', 'krumkach' ... Heh, I like krumkach, sounds in German quite funny :). BTW, how are Geany codenames chosen? :-' My list just uses belarussian birds names: stork(busel), sparrow(verabei), raven(krumkach) -- Yura Siamashka yura...@gmail.com ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] TODO: update GTK+ version in Hacking
On 21/09/2011 23:06, Matthew Brush wrote: I noticed that this section[1] in the hacking manual mentions: This is because Geany depends on GTK 2.8. API symbols from newer GTK/GLib versions should be avoided to keep the source code building against GTK 2.8. Now fixed. I guess this should be updated to GTK+ 2.12 and to host that version of GTK+ API docs. [1] http://geany.org/manual/dev/hacking.html#gtk-api-documentation I'll leave this for Enrico. ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] editing big files can be too slow with tag reparsing
Hi, Whilst opening doc/geany.html I found it takes 5s on my machine to load. It's a big document though, still perhaps the HTML tag parser performance could be improved. But now we have tag reparsing, editing geany.html becomes painful. I know we can disable reparsing, but what else could we do to improve the situation? It's not urgent to solve this problem, unless we want to make reparsing off by default. ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] How about calling the next release 1.0?
On Thu, Sep 22, 2011 at 15:34, Frank Lanitz fr...@frank.uvena.de wrote: Am 22.09.2011 15:28, schrieb Colomban Wendling: Le 20/09/2011 23:26, Enrico Tröger a écrit : On Tue, 20 Sep 2011 16:10:34 +0300, Yura wrote: Hi But why only 1.0? GNOME 3.* KDE 4.* Scite 2.* What about Geany 3000? Or some kind of other stupid release name like ''busel', 'verabei', 'krumkach' ... Heh, I like krumkach, sounds in German quite funny :). BTW, how are Geany codenames chosen? :-' More seriously, I personally don't mind much about version numbers. It's good to have some but the actual value doesn't mean much to me. But I realise other people take more care about this and 0.x might seem not that mature to many users. So, I'd say: why not. I'd say quite the same. I don't really mind, and it seems it's something important for many of you so... But can we do it post 0.21? Only one week left and I want to concentrate on improving translation etc. instead of searchreplace version numbers. Hi Frank, if it should cause problems, of course it can wait, it was just a suggestion... ...on the other hand I've just tried to make the renaming from 0.21 to 1.21 and it isn't too hard to do and doesn't seem to be very intrusive - see the attached patches both for Geany and geany-plugins. The only missing things are: 1. The documentation should be regenerated 2. Version should be updated in *.po files (I didn't do it because you'll be receiving po files from translators with version 0.21 now and it will be easiest to update all of them at once before the release) 3. The version number change should be mentioned in ChangeLog/NEWS Cheers, Jiri geany_plugins_1_21.patch Description: Binary data geany_1_21.patch Description: Binary data ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] TODO: update GTK+ version in Hacking
On Thu, 22 Sep 2011 17:13:19 +0100, Nick wrote: On 21/09/2011 23:06, Matthew Brush wrote: I noticed that this section[1] in the hacking manual mentions: This is because Geany depends on GTK 2.8. API symbols from newer GTK/GLib versions should be avoided to keep the source code building against GTK 2.8. Now fixed. I guess this should be updated to GTK+ 2.12 and to host that version of GTK+ API docs. [1] http://geany.org/manual/dev/hacking.html#gtk-api-documentation I'll leave this for Enrico. Yup, will do soon. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc pgpk0yug44AKw.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] How about calling the next release 1.0?
On Thu, 22 Sep 2011 15:28:21 +0200, Colomban wrote: Le 20/09/2011 23:26, Enrico Tröger a écrit : On Tue, 20 Sep 2011 16:10:34 +0300, Yura wrote: Hi But why only 1.0? GNOME 3.* KDE 4.* Scite 2.* What about Geany 3000? Or some kind of other stupid release name like ''busel', 'verabei', 'krumkach' ... Heh, I like krumkach, sounds in German quite funny :). BTW, how are Geany codenames chosen? :-' If I tell you, I'll have to kill you... More seriously (though not much), the codenames are just taken from names of Moffs[1] and Grand Moffs from the Star Wars Universe :). [1] http://starwars.wikia.com/wiki/Moff Feel free to change the naming scheme for future releases or even drop the codenames. They have absolutely no relevance at all. So far, they only expressed my fondness for Star Wars :). Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc pgpS7zjSZfUbe.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] editing big files can be too slow with tag reparsing
On 09/22/2011 09:30 AM, Nick Treleaven wrote: Hi, Whilst opening doc/geany.html I found it takes 5s on my machine to load. It's a big document though, still perhaps the HTML tag parser performance could be improved. Well under 1 second to load geany.html here, and editing it is quite smooth as well. Myself, I've found the biggest slowdown is when having lots of tags files, say more than 10 maybe. If I have all my Vala tags (the ones on the Wiki) loaded, Geany basically becomes unusable. I didn't spend much time troubleshooting, but I suspect turning down the symbol update frequency might help. But now we have tag reparsing, editing geany.html becomes painful. I know we can disable reparsing, but what else could we do to improve the situation? It's not urgent to solve this problem, unless we want to make reparsing off by default. IMO it would be best not to disabling automatic updating of the symbols, it's a really good feature. Cheers, Matthew Brush ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] editing big files can be too slow with tag reparsing
On 23 September 2011 10:34, Matthew Brush mbr...@codebrainz.ca wrote: On 09/22/2011 09:30 AM, Nick Treleaven wrote: Hi, Whilst opening doc/geany.html I found it takes 5s on my machine to load. It's a big document though, still perhaps the HTML tag parser performance could be improved. Well under 1 second to load geany.html here, and editing it is quite smooth as well. Ditto, but of course it depends on the machine. Myself, I've found the biggest slowdown is when having lots of tags files, say more than 10 maybe. If I have all my Vala tags (the ones on the Wiki) loaded, Geany basically becomes unusable. IIUC the tags files are not re-loaded so the problem here suggests symbol lookup problems rather than parsing problems. I didn't spend much time troubleshooting, but I suspect turning down the symbol update frequency might help. If it is a parsing problem sure. But now we have tag reparsing, editing geany.html becomes painful. I know we can disable reparsing, but what else could we do to improve the situation? It's not urgent to solve this problem, unless we want to make reparsing off by default. Of course if we turn it off by default a lot of people won't turn it on and won't know about the feature. IMHO its better to have it on by default and field a few ML/IRC questions about it being slow for big files. Cheers Lex IMO it would be best not to disabling automatic updating of the symbols, it's a really good feature. Cheers, Matthew Brush ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] AUTHORS THANKS files
Hi, I was just looking at these files for some reason and a few things struck me as kind of odd. The header of the THANKS file says: This file lists all *external* people that have contributed to this project. (emphasis added) which sounds kind of odd. For example, it seems all of the core developers and regular contributors are listed here. I don't even think of myself as external, let alone Nick, Frank and Colomban and many others in the list. And then in AUTHORS, it lists the core developers, and then under Regular Contributors it lists only two people. I'm curious what the criteria for being a Regular Contributor is, since I've seen a bunch of regular contributions on the ML and patch tracker, many of which were made by people other than those two people. At first I thought it might be people who have SVN commit access, but then there's the COMMITTERS file, so that's not it I don't think. IMHO, anyone in the THANKS file that has actually authored any code or translations should be listed in AUTHORS. On a similar topic, I noticed in the source files, on top of the license in the comments, some files list Nick and Enrico as the copyright holders, some also have Frank, others Colomban, and yet others Lex (and maybe others still). It seems as though if you contribute significant portions of code to a file, you should add your own copyright blurb in the comments? Would it not make more sense to have a single copyright holder for all files in the project, be it a person (ie. the current lead/maintainer), or an organization (ie. The Geany Software Foundation :) Also, if someone contributes a significant amount of code to one or more files, does that mean they hand-over the copyright of that code to one (or maybe all?) of those people listed in the various file headers? The reason I ask about the copyright thing is that I'm currently working on something that basically adds entirely new files and I wasn't sure if I should add my own copyright blurb in the fileheader or that of someone else. It almost seems like currently the copyright blurbs in the file header comments are more like an Authorship or Attribution than copyright. I think it might be useful to put some information about this in the HACKING file so that contributors clearly know whether to put their own copyright in the header, or if not, who's name/info to pass the copyright on to. Also whether they should add their names to the AUTHORS file, or THANKS file, and whether they should update the ChangeLog (if that sticks around) and to update the documentation. It also wouldn't hurt to mention in there that all of the submitted code will become/has to be GPL, just in case that's not clear. We're coders after all, not law talkin guys. Cheers, Matthew Brush ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
