Re: Glade branches glade-3-10
On Wed, 2011-04-13 at 03:56 +0900, Tristan Van Berkom wrote: > On Wed, 2011-04-13 at 08:45 +0200, Claude Paroz wrote: > > Le mercredi 13 avril 2011 à 01:26 +0900, Tristan Van Berkom a écrit : > > > Hi, > > >I've set up the glade-3-10 stable branch of Glade for GTK+3 > > > based on today's git master. > > > > > > FWIW, the other stable branch glade-3-8 (for GTK+2) is not dead > > > yet and will surely see some bugfix releases. > > > > Hi Tristan, > > > > Is there a reason you don't follow "gnome-..." naming scheme like you > > did until gnome-2-28 ? > > We don't number our releases after gnome release numbers (and I never > did tag any 'gnome-' tags with Glade). Actually sorry, I do recall having tagged 'gnome-' a couple times (when I had in mind that 'this glade' was targeting 'this gnome') In any case I don't think it makes much sense, as the numbering scheme is different and already, we have 2 branches that are potentially targeting the same gnome release. > > Cheers, > -Tristan > > > > > Claude > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Glade branches glade-3-10
On Wed, 2011-04-13 at 08:45 +0200, Claude Paroz wrote: > Le mercredi 13 avril 2011 à 01:26 +0900, Tristan Van Berkom a écrit : > > Hi, > >I've set up the glade-3-10 stable branch of Glade for GTK+3 > > based on today's git master. > > > > FWIW, the other stable branch glade-3-8 (for GTK+2) is not dead > > yet and will surely see some bugfix releases. > > Hi Tristan, > > Is there a reason you don't follow "gnome-..." naming scheme like you > did until gnome-2-28 ? We don't number our releases after gnome release numbers (and I never did tag any 'gnome-' tags with Glade). Cheers, -Tristan > > Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Glade branches glade-3-10
Hi, I've set up the glade-3-10 stable branch of Glade for GTK+3 based on today's git master. FWIW, the other stable branch glade-3-8 (for GTK+2) is not dead yet and will surely see some bugfix releases. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'glade.master'
On Tue, Apr 5, 2011 at 4:30 PM, Johannes Schmid wrote: > Hi Tristan! > > Do you have a general hard-code freeze exception for glade? You made > more than 20 commits in the last 24 hours, none seemed to by signed off > by the release-team and two broke string freeze. All the commits yesterday were necessary, without them there would be no release of Glade... which is thankfully tagged and ready now. As far as I know strings were removed from glade-3-8 branch for the sake of backing out the preview feature that did not belong in 3.8. For what it's worth, we held back: - Support for editing GtkSwitch - Support for editing GtkInfoBar - Support for setup up renderers in GtkEntryCompletion - Spelling mistake fixes (3 spelling mistake bugs I believe) ... for the sake of not breaking strings in this release. > > Please follow the GNOME release rules! Not breaking a hard-code freeze would simply make this release impossible, I'm not sure which you would prefer. We've done a great deal to comply as much as possible, following releases should not have this problem, there have just been tons of changes this cycle. I should also point out that the information I have at hand concerning this says I did not break any rules: "Precise rules are yet to be defined." http://live.gnome.org/TwoPointNinetyone/FeaturedApps In any case, what was done last night was the bare minimum to get Glade releases out of the door on time (or maybe late even), sorry for any inconvenience this may have caused. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Please use 'gnome-2-28' branch for Glade
Hi all, There have been no significant developments this year in Glade. Please refer to the 'gnome-2-28' branch of the glade3 module when considering Glade for a release of GNOME 2.30 (or 3.0 or whatever it will be...). This is just a symbolic email to free up activity in git master (the fact that I have not been working actively on Glade; and not sending this message out sooner; caused me to hit a string freeze break this morning, sorry for any confusion that may have caused), for clarification; there is no planned new release off of branch gnome-2-28. Thanks for bearing with me. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'glade3.master'
Sorry for the confusion. There have been no significant developments in Glade in this release cycle. The active branch should still be 'gnome-2-28', while there is still not much new to release except for some added GTK+ widgets and an updated catalog, I'm going to release master with a bumped unstable version number in the hope that this will help avoid confusion. A general clarification email will follow. Cheers, -Tristan On Wed, Mar 10, 2010 at 5:45 AM, Andre Klapper wrote: > Hi Tristan, > > Am Mittwoch, den 10.03.2010, 00:19 + schrieb GNOME Status Pages: >> There have been following string additions to module 'glade3.master': >> >> + "Entry Buffer" >> + "Spinner Renderer" >> + "Spinner" >> >> Note that this doesn't directly indicate a string freeze break, but it >> might be worth investigating. > > > Your commit 1b750f3d5d41bc159dfc6cd5e3d799838d88d7ca broke the string > freeze. Please either revert, or elaborate here why it is important and > ask for approvals. > > andre > -- > mailto:ak...@gmx.net | failed > http://www.iomc.de/ | http://blogs.gnome.org/aklapper > > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Glade re-branched stable as gnome-2-28
After a moments pause, I decided this year was a good time to go with the GNOME branching scheme. It will make more sense if Glade does not see a major point release for quite some time to just branch with the gnome version numbers (will be easier for me to handle patches which break freezes etc.). So sorry for the confusion there, the good branch for releasable Glade with no unexpected freeze breaks for GNOME 2.28 is the 'gnome-2-28' branch. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[glade3] Created branch gnome-2-28
The branch 'gnome-2-28' was created pointing to: a518019... Updated British English translation ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Branching Glade 3.6 line
Created a stable branch for Glade 3.6 today, the branch is called 'glade-3-6' I hope to make releases off the 3.6 branch for a while and only use master for some patches that are not release ready just yet, or patches which may break string/ui freezes. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Is glade (not glade3) obsolete?
On Fri, Dec 19, 2008 at 1:08 PM, Leonardo F. Fontenelle wrote: > I see the glade-not-3 module wasn't touched in 12 months, except for > translations. If there will be no more glade 2.x releases, please inform > svnmaster, bugmaster, gnome-i18n and gnome-doc-l...@gnome.org that the > module is obsolete. Hi, we kept Glade 2 available in the first years of Glade 3 being stable yet immature, we are IMO definitly past that now. Its safe to say that Glade-2 development is closed (although Damon was the one maintaining that module, not me). I am CCing him here in case he may have any kind of objection, otherwise please discontinue Glade-2. What are the emails of svnmaster and bugmaster ? > BTW, will glade3 trunk be stable for GNOME 2.26? Damned Lies (i18n > infra-structure) is tracking glade3 trunk, and January 5 translators > will start working on it. Yes. Sorry I made you release 3.4.x last gnome release, I just couldnt bring gtkbuilder to the table that fast, now we are ready, if I dont get uimanager in time, I'm releasing 3.6 with native menu support (in gtk+ 2.16) stable for gnome 2.26 anyway. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME 2.24: Worst release cycle I have been a part of [l10n/i18n]
On Sun, Oct 12, 2008 at 3:12 PM, Claude Paroz <[EMAIL PROTECTED]> wrote: [...] >> Now, when it comes to someone packing a distro or preparing a flashy new >> "gnome release set", I can understand people liking that they can say its >> "100% translated", but personally, and I think from one maintainer to >> another, >> I could care less if its all translated on release date or not, we >> obviously dont >> have the resources for that final minute touch up so who are we trying to >> kid ? > > I'm not sure to understand what you're saying here, but I can say that > the aim of every translation team is to have most of strings translated > for a release, because that's what eventually matters for users. > What Im trying to say, is that me, with a few hands to help out can try to make a release on a given date; I even think we do pretty well in contrast with corporations I've worked for - but there will always be remaining unforseen bugs and tidying up to be done after the release, bottom line: if we barely have the resources to dish out a marginally complete release in 6 months - how can we expect translators to reach 100% in 20 days ? Then again, from my point of view gnome translations have always been a mysterious process - so if its comfortable for translators and release team then thats great. [...] > As Leonardo said, when GNOME is going forward fast, translators sweat. > In this perspective, I can only hope that we'll continue to have hard > times as translators :-) Very positive point :D Best regards, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME 2.24: Worst release cycle I have been a part of [l10n/i18n]
On Sun, Oct 12, 2008 at 1:07 PM, Kenneth Nielsen <[EMAIL PROTECTED]> wrote: [...] > A separate matter is: Why do we always have to be the ones that say > no? With any luck I might be a parent one day, so I really don't want > to have to get into that habit to early. I suppose one of the thing I > asking for, is a little more project (project as in module not GNOME > as a whole) leader responsibility as well, since probably some of > these thing should have been rejected already at that level, before > even reaching us. If you want an example of this, you can read the > thread from the gnome-i18n list from Sep 16 about a string addition to > glade3. I'm not sure whether it really ended up actually adding > strings, but it was clear enough that not many thoughts had been given > to the rest of the group from them. Dont worry, I'm not taking offense, I read your previous post and wanted to share my feelings already ;-) In this release cycle I've been a little less than communicative, and for that I apologize, I've been feeling my own brand of disgust, and thats completely my own fault. If its any consolation, I did send a call for aid email to d-d-l some months ago, stating that there was no way we could be ready for this release unless someone were to step in (it was kind of a heads up) but I should have sent an official email to i18n/release-team. [...] > I understand the predicament of the volunteer, especially when it > comes to time. But being a volunteer does not mean that you can ignore > your responsibilities once you are commited. Being a volunteer means > that you decide whether you perform the task or not, not that you can > decide to perform it any way or style you want to. >From that statement I can make an educated guess that you are severely underestimating our lack of resources. Lets take a look at the particular life a solo flying maintainer in gnome, myself. I worked alot on glade, and that is an understatement - I've brought it to its first release - I saw it through the creation of the devtools suite and advocated the new suite, on top of working on glade, I tried my damndest to help get gtkbuilder on the road for gtk+, since development roads in libglade were pretty much closed. This year was the dawn of 2008 and gtkbuilder was finally ready, and everyone's stuck using a conversion script for glade files - when it comes to free software, any maintainer will tell you that people are far quicker to criticize shortcommings than to contribute patches - this is the brand of disgust /we/ have to live with. Now I'm not pulling stats out of svn, but some estimations that may startle are that glade code base, on average in the last few years is probably made up of: 80% me 15% Juan Pablo Ugarte 5% Vincent Geddes, chpe and others and Im not even kidding, I actually consider that a generous estimation. This year we had an exceptional volunteer soc student that submitted many anjuta related patches - some of which were even remotely relavent to the gtkbuilder centric release I have no choice but to make (I'm over emphasizing here, so you get my drift..). Now, that was venting, but I think productive, I learned a few things from hearing you vent so I thought you should here my side, and now for something completely different: About translation teams in gnome, I dont know if were doing whats best, and I'm sure there is room for improvement on this front, let me share my pov being the CM of my own project, I have to manage branches and stuff when we make development spikes or stable releases - what is LOOKS like to me, is that we are WASTING the translations, I may be wrong, but this is how it usually goes: few weeks before freezes: were concentrating on bugfixes, and holding new stuff back a bit, planning the next release freeze comes: we generally branch here, as a small team we need to move fast to get new features in --> at this point translators are translating the stable branch, and they are translating ALOT at this time. release comes: more bug fixes, generally never any user visible changes in the stable branch at this point. Now, I asked the i18n team on more than one occasion, after release time, if I was expected to merge all the good work the translators are doing on the rotting old stale branch, into trunk (generally we backport some fixes to stable but never the other way around) - I dont want to sound rude but I never got a real answer, I got a "thanks for your consideration were working on it" something along those lines. Now, when it comes to someone packing a distro or preparing a flashy new "gnome release set", I can understand people liking that they can say its "100% translated", but personally, and I think from one maintainer to another, I could care less if its all translated on release date or not, we obviously dont have the resources for that final minute t
Re: String additions to 'glade3.HEAD'
On Wed, Sep 17, 2008 at 5:50 AM, Vincent Untz <[EMAIL PROTECTED]> wrote: > Le mardi 16 septembre 2008, à 16:51 -0400, Tristan Van Berkom a écrit : >> There are little or no string changes in gnome-2-22 branch, and no, I dont >> intend to release anything else off of that branch, so dont waste your time. > > So no new translations? We can handle the creation of a tarball for you > if it's a time issue. If you want to add new translations to gnome-2-22 branch and make a release from there thats fine with me, time is definitely an issue, if I mean to ever make a 3.6 release - this time I cant be bothered with the old branch. On the other hand, one release is just about all the mileage you'll get out of those translations, and I would obviously rather see useful new strings from trunk being translated... Cheers, -Tristan > > Vincent > > -- > Les gens heureux ne sont pas pressés. > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Glade 3 in 2.24 (was Re: String additions to 'glade3.HEAD')
On Tue, Sep 16, 2008 at 3:34 PM, Vincent Untz <[EMAIL PROTECTED]> wrote: > Le mardi 16 septembre 2008, à 15:13 -0400, Tristan Van Berkom a écrit : >> Sorry for not having sent anything official, but we are not going to >> have anything >> stable for gnome-2-24, we plan to release glade 3.6 from trunk as soon as >> possible, but dont expect to see that in gnome releases until next release. >> >> If you want a stable branch its gnome-2-22, but personally I'd rather >> let that rot. > > Hrm, what are we supposed to release with GNOME 2.24.0, then? The latest stable glade is 3.4.5 Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'glade3.HEAD'
There are little or no string changes in gnome-2-22 branch, and no, I dont intend to release anything else off of that branch, so dont waste your time. I guess the important thing here is, translation of glade trunk is what we need (i.e. translating glade trunk is not a waste of time) but if you have other priorities, stick to them, because were not part of this release plan, we have nothing stable and new to offer. Cheers, -Tristan On Tue, Sep 16, 2008 at 3:43 PM, Gil Forcada <[EMAIL PROTECTED]> wrote: > Hi! > > We (translators) need to know what we have to translate, GNOME is a huge > project with lots of strings to translate, so if you are saying to stick > with gnome-2-22 branch let us know, also a message from r-t would help > here. > > Cheers, > > > El dt 16 de 09 de 2008 a les 15:13 -0400, en/na Tristan Van Berkom va > escriure: >> Sorry for not having sent anything official, but we are not going to >> have anything >> stable for gnome-2-24, we plan to release glade 3.6 from trunk as soon as >> possible, but dont expect to see that in gnome releases until next release. >> >> If you want a stable branch its gnome-2-22, but personally I'd rather >> let that rot. >> >> Cheers, >> -Tristan >> >> On Tue, Sep 16, 2008 at 2:54 PM, Johannes Schmid <[EMAIL PROTECTED]> wrote: >> > Hi Tristan! >> > >> > I think you missed something here - we are already in string (and code >> > freeze). Or did you create a gnome-2-24 branch already? >> > >> > Regards, >> > Johannes >> > >> > On Di, 2008-09-16 at 18:26 +, GNOME Status Pages wrote: >> >> This is an automatic notification from status generation scripts on: >> >> http://l10n.gnome.org/. >> >> >> >> There have been following string additions to module 'glade3.HEAD': >> >> >> >> + "Add widget as _root" >> >> + "Adding parent %s for %s" >> >> + "Create root widget" >> >> + "_Add widget here" >> >> >> >> Note that this doesn't directly indicate a string freeze break, but it >> >> might be worth investigating. >> >> ___ >> >> gnome-i18n mailing list >> >> gnome-i18n@gnome.org >> >> http://mail.gnome.org/mailman/listinfo/gnome-i18n >> >> >> > >> ___ >> gnome-i18n mailing list >> gnome-i18n@gnome.org >> http://mail.gnome.org/mailman/listinfo/gnome-i18n > -- > gil forcada > > [ca] guifi.net - una xarxa lliure que no para de créixer > [en] guifi.net - a non-stopping free network > bloc: http://gil.badall.net > > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'glade3.HEAD'
Sorry for not having sent anything official, but we are not going to have anything stable for gnome-2-24, we plan to release glade 3.6 from trunk as soon as possible, but dont expect to see that in gnome releases until next release. If you want a stable branch its gnome-2-22, but personally I'd rather let that rot. Cheers, -Tristan On Tue, Sep 16, 2008 at 2:54 PM, Johannes Schmid <[EMAIL PROTECTED]> wrote: > Hi Tristan! > > I think you missed something here - we are already in string (and code > freeze). Or did you create a gnome-2-24 branch already? > > Regards, > Johannes > > On Di, 2008-09-16 at 18:26 +, GNOME Status Pages wrote: >> This is an automatic notification from status generation scripts on: >> http://l10n.gnome.org/. >> >> There have been following string additions to module 'glade3.HEAD': >> >> + "Add widget as _root" >> + "Adding parent %s for %s" >> + "Create root widget" >> + "_Add widget here" >> >> Note that this doesn't directly indicate a string freeze break, but it >> might be worth investigating. >> ___ >> gnome-i18n mailing list >> gnome-i18n@gnome.org >> http://mail.gnome.org/mailman/listinfo/gnome-i18n >> > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Glade 3 branched for 2.22
We've branched out stable development based on Glade 3.4.3 and development in trunk, for stable glade go to branches/gnome-2-22. We still have the same game plan for 3.6, builder file support is the main agenda. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: HTML tags in translatable strings - glade
On Jan 11, 2008 9:47 PM, Jonh Wendell <[EMAIL PROTECTED]> wrote: > Hi, folks. > > I'd like some help/direction on how to fix bug 498402 [1]. > It's about strings like 'Enter a name for this connection'. > > These strings come from glade, and are marked for translation. I know i > should cut the html tags, but is there a way to do this without need of > coding? Can glade/intltools strip those marks away automagically? There is an old debate I see you found here: http://bugzilla.gnome.org/show_bug.cgi?id=97061 My personal preference here would be to support the attributes property in glade, as proposed by Matthias. Then the preffered way of setting markup would simply be through a separate property. (the bug also mentions certain conflicts when setting "attributes" & "use_underline" and other auxiliary properties, these conflicts IMO should be dealt with in gtklabel.c). Cheers, -Tristan PS: Adding glade-devel to the CC list, hope thats ok. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Glade 3 branched
We finally got around to dumping the latest bug fixes into the glade 3.4.1 release and branched that out for gnome-2-20. so stable glade for now is comming from branches/gnome-2-20 For Glade 3.6, we will include a few minor user visible changes and would like to include support for builder files, but this is not up to speed since I've been traveling around the world and dont have a computer to work from yet. the tracker is here http://bugzilla.gnome.org/show_bug.cgi?id=490678 I honestly dont think its going to make 3.6 though. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Announcing string change in glade
We made a string change in glade. The "Select Widgets" button in the toolbar (src/glade-window.c:2503) became a "Select" button (as it was taking up alot of screen realestate on the toolbar). Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
glade string change
We changed strings in the signal editor today (details: http://bugzilla.gnome.org/show_bug.cgi?id=464505). Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Announcing strings/features
Announcing some new strings and a new feature here... just implemented "Add/Remove Parent widget" feature in glade 3.3.x... this bug describes it: http://bugzilla.gnome.org/show_bug.cgi?id=343786 Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Glade 3 - translations & ui/string change announcements
On Tue, 2007-07-17 at 12:16 +0200, Jorge González González wrote: > Hi, > > is: > msgid "No displayable values for %sproperty %s::%s" > > an error? Ummm, yes and no actually :) That message might end up reading: "No displayable values for property..." or it might read: "No displayable values for child property..." But console messages like that are not part of glade's feature set (they're just assertions/warnings), so they shouldnt be translated, so yes its an error thanks for pointing it out :) Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Glade 3 - translations & ui/string change announcements
Ok 2 things to announce, - gnome-2-18 branch closed, not planning on making any more glade 3.2.x releases, that means translators please go back to translating trunk for now. - Today we made a user visible change, the view menu now has "Dock Palette", "Dock Editor", "Dock Inspector" toggle menuitems (which have the predictable consequence of docking/undocking those tools from the main glade window). Question: At this point, should I overwrite glade3-trunk/po/*.po with glade3-gnome-2-18/po/*.po ? is there a standard merging proceedure or do I leave all that up to the translation teams when moving across branches ? Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Glade branched for gnome 2.18
On Wed, 2007-03-07 at 20:42 +0100, Claude Paroz wrote: > Le mardi 06 mars 2007 à 14:44 -0500, Tristan Van Berkom a écrit : > > As development for gnome 2.18 has frozen solid, we're obviously going > > to have to branch out. so I did that. > > > > translators, release-team and doc writers should know that the > > 2.18 branch can be found in the standard location: > > "svn.gnome.org/svn/glade3/branches/gnome-2-18" > > Thanks. l10n.gnome.org should be updated soon. Hi, This commit hit trunk this morning: 2007-03-07 Ani Peter <[EMAIL PROTECTED]> * ml.po: Added Malayalam Translation * LINGUAS: Added ml (Malayalam Translation) Its tedious, shall I go ahead and merge back the change into the 2.18 branch ? Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Glade branched for gnome 2.18
As development for gnome 2.18 has frozen solid, we're obviously going to have to branch out. so I did that. translators, release-team and doc writers should know that the 2.18 branch can be found in the standard location: "svn.gnome.org/svn/glade3/branches/gnome-2-18" I've already requested a string break for some important blockers (i.e. glade in 2.18 is feature incomplete without them)... and I'll be periodically requesting code freeze breaks for minor bug fixes on Glade 3.2.x (for instance I have a simple fix pending on: http://bugzilla.gnome.org/show_bug.cgi?id=396436 ). For those working on Glade, development will continue in 'trunk' and instead of how we worked for 3.0/3.1, we'll be committing bugfixes right onto trunk and porting them back into 'gnome-2-18' periodically upon approval from the release-team (we'll try to keep track of important bugfixes pending approval in the TODO file or something). There's a final release this week for 2.18, hopefully we'll get that string break in there by that time, and we'll be releasing that from the branch, the branch will at that point become 3.2.x, and I'll bump 'trunk' to be 3.3.x at that time. Alright I think thats it for now... I'll write up something more formal wrt bug 396436 once I get this show on the road. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Request for string break on Glade for 2.18
On Sun, 2007-03-04 at 12:25 +0100, Vincent Untz wrote: > Le samedi 03 mars 2007, à 13:58, Tristan Van Berkom a écrit : > > Hi all, > >I know its a little late in the game but I have a > > patch that I really consider a showstopper-fixer that > > will break string freeze in glade. > > > > In this development cycle there was a regression that > > made accelerator & atk relationset properties dissapear. > > my patch brings them back. > > How many strings does it bring back/add? All together 15 atk relation properties, thats 15 short names & 15 tooltips for a grand total of 30 strings - the revived accelerator property doesnt really bring in any new strings since those few strings were still laying dormant in the codebase. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Request for string break on Glade for 2.18
Hi all, I know its a little late in the game but I have a patch that I really consider a showstopper-fixer that will break string freeze in glade. In this development cycle there was a regression that made accelerator & atk relationset properties dissapear. my patch brings them back. Sorry for the inconvenience :( Cheers, -Tristan Note that all the strings added were already there at some point (with the exception of a correction on the node-child-of property and the newly added description-of/description-for properties), the es.po already contains translations for these strings. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Glade: closing stable branch
Hi, We released Glade 3.0.3 this morning with some final bugfixes and some updated and new translations, we dont plan on making any more releases in 3.0, so I'm closing the glade3-3-0-branch from development (I guess if people really wanted some kind of crucial bugfix that we missed, it would warrant a 3.0.4 release, but I'm not planning on it). Development will continue in HEAD and we are targeting gnome 2.18 for the next stable release of Glade (3.2). I guess the most important part of this email is for translation teams, please go back to translating HEAD (note that I have indeed ported all changes from the stable branch back into HEAD at this time, including translations, it should be safe ;-)). Cheers all, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Glade 3.0 stable branched
Leonardo Fontenelle wrote: > 2006/10/3, Abel Cheung <[EMAIL PROTECTED]>: > >> On 9/30/06, Tristan Van Berkom <[EMAIL PROTECTED]> wrote: >> > Hi all, >> > we've just branched stable development of Glade 3 into the >> > glade3-3-0-branch, >> > this branch is pretty much feature frozen and will only be updated with >> > bugfixes. >> >> A question for translators: does that mean translators should concentrate >> on this branch for now, unless explicitly told otherwise? [...] Sorry I think this email missed my inbox somehow... > This means there will be two Glades 3 to translate; the glade3-3-0 > branch and the HEAD branch. The former branch will have few changes, > while the second will change a lot. > > IMHO, it would interesting to translate it now because most of the > branch will be reused in HEAD, so it is easier to keep both coherent > now, and latter all you have to do is update the HEAD. Most Glade development will be done in HEAD - meaning HEAD will be more sporadic wrt strings especially, its also important to note that this particular release cycle will deal heavily with the user interface of glade proper, so there will be much UI prototyping and many strings will probably change multiple times before we reach a stable UI. I think its probably best to stay away from HEAD at least untill we iron out a UI, at which point I should probably call for a string freeze for 3.1 - as Leonardo suggests; the stable branch will have its changes and bugfixed pulled into HEAD regularly so for whichever strings /havent/ changed, thier translations wont be lost. Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Glade 3.0 stable branched
Hi all, we've just branched stable development of Glade 3 into the glade3-3-0-branch, this branch is pretty much feature frozen and will only be updated with bugfixes. In HEAD we will be focusing on the UI in this cycle, the embedded window UI that Vincent Geddes has been working on will apear in HEAD momentarily and that will allow us to address alot of bugs by takeing a completely different approach on handling events on widgets - we hope to get alot of feedback in this next cycle and adjust the UI so as to satisfy most - there will also be a significant rework wrt commands (undo/redo objects). I expect a 4 to 6 month development cycle for this release, after that we plan to rewrite the parser to support dual formats (i.e. gtkbuilder format) and implement all the dormant GObject's targetting a gtk+2.12-ish timeframe. I just wrote this mail up because I read http://live.gnome.org/MaintainersCorner and thought to notify all the relevent lists. Worthy of note is that I am writing d-d-l but glade is not part of the gnome desktop module group - while I do have some ideas on that matter I dont feel like writing up a 10 page essay on it so... suffice it to say "do we want glade as part of some gnome module set" ? any ideas on that ? Cheers, -Tristan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
