Re: [Evolution-hackers] Testing Evolution 3.x
2011/2/8 Matthew Barnes mbar...@redhat.com: On Tue, 2011-02-08 at 14:23 +0100, Onyeibo Oku wrote: The Help-About on my Evolution mail menu still reads 'Evolution 2.32.1' but I see Development is now at 3.x. Is there anyway I can experience the future Evolution Mail Client while you guys do your thing? Is the risk of test-running still high? I'm presently test-running Gnome-shell (jhbuild) but I'm running Fedora 14. I might be able to chip in one or two after experiencing status-quo. I suspect that would be helpful. If you're already using jhbuild and it's still building 2.32 apps, make sure you're using the GNOME 3 module sets listed here: http://git.gnome.org/browse/jhbuild/tree/modulesets I don't use jhbuild myself or I'd tell you more about how to set that up, but I'm sure Google can answer that. Here's another, perhaps more convenient option: Fedora desktop team just conducted a GNOME 3 test day and the live image they produced for it includes GNOME Shell and Evolution 2.91.6: https://fedoraproject.org/wiki/Test_Day:2011-02-03_GNOME3_Alpha#Live_image If you have a spare USB stick or blank DVD, make yourself a live image, boot it, and you can play around in GNOME 3 with no risk to your system. Or you can also use GNOME3 live image : http://gnome3.org/tryit.html :) -- Frederic Crozat ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Testing Evolution 3.x
2011/2/8 Onyeibo Oku two...@fedoraproject.org: On Tue, 2011-02-08 at 15:21 +0100, Frederic Crozat wrote: Or you can also use GNOME3 live image : http://gnome3.org/tryit.html :) BLUNDER 101: I know this might upset the geeks but I screwed up big time. The Gnome-3 ISO wasn't cooperating when burnt so I decided to use the USB option (was giving me similar errors as with the fedora test ISOs). So what is the big blunder, you may ask? Everything was going fine until the usb-image-writer stopped at 100% for a few minutes. It appeared to have hanged so I quit the terminal and pulled the drive. I now have a stick with CD-ROM partition having incomplete data and I don't know how to revert to the beginning. Hope someone here can give me an idea how to remove the CD-ROM partition so I can exercise 'patience' in full and get the desired results This depends on kernel buffering and usb stick write speed. You shouldn't have removed the key. Just re-run the tool and really wait until it is complete and everything will be fine. If you want to reset it for another use, run dd if=/dev/zero of=/dev/sdX bs=1M count=10 (where X is the letter corresponding to the stick, you can check with the tool) and you should be able to repartition it (after unplugging and replugging it). -- Frederic Crozat ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] bug fixing in stable 2.22.x branch
Le mardi 02 septembre 2008 à 14:43 +0530, Srinivasa Ragavan a écrit : On Tue, 2008-09-02 at 09:23 +0200, Frederic Crozat wrote: Le lundi 01 septembre 2008 à 19:55 +0200, Patrick Ohly a écrit : On Thu, 2008-08-21 at 12:37 +0530, Chenthill wrote: Thanks, I will send out a mail to the list mentioning the critical fixes which have gone in recently in the stable branch which needs to be taken into the distro's. Bug #548268 is in trunk (thanks Chenthill!) and tested automatically now. The test showed that the time zones in South America and Australia were also affected. I think we should send out that bug list to the distributors ASAP. Debian Etch is already frozen. Chenthill, do you have the list ready and can you send it both to this list and the distributor list? My own proposal for inclusion are * 548268: time zone conversion incorrect * 546934: [Exchange Connector] contact change tracking is broken (required by SyncEvolution) * 499932: [Bug 499932] Not deleting from e-mail server after specified time Frankly, I think it would be much better to do a 2.22.x release for the needed fix : you'll get updated translations as a bonus and distributions might be more willing to push it, rather than try to apply a list of patches. I think this should be discussed at d-d-l/release-team than lowering it to Evolution/any-other-project. We currently follow GNOME cycle, as you know. Unless we hit to a serious issue, you will be always be the waiting for a release, where as developers would waiting for a more better time to do it. I was just talking for this particular list of bugs, not in general. Eog or gthumb have been doing additional releases after the .3 release for quite some time. You could also delegate the release process to other people who would be willing to take care of it. -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Exchange MAPI Connector
Le mardi 23 octobre 2007 à 12:07 +0530, Srinivasa Ragavan a écrit : Hello everyone, For Evolution 2.22 we should be having MAPI based Exchange connector which developed in parallel with Openchange based libmapi. The team is currently working on that and the code is currently maintianed at GNOME SVN in EXCHANGE_MAPI_BRANCH (both for evolution and evolution-data-server) http://svn.gnome.org/viewvc/evolution/branches/EXCHANGE_MAPI_BRANCH/ http://svn.gnome.org/viewvc/evolution-data-server/branches/EXCHANGE_MAPI_BRANCH/ I created the branch yesterday and we committed our week long effort there. We now have a working account setup plugin, base camel/calendar code and a partially working addressbook impl. Things should get to a working shape in another week or two. I hope that soon, Johnny would be able to create a OpenSUSE Build Service repository (rpms for OpenSUSE, Fedora, Ubuntu and few more) for Evolution and its dependencies so that users can install the rpms and get a feel of it even before the release. Please, remember to notify release-team and everybody else on desktop-devel about the new introduced external dependency for evolution-data-server and evolution. Thanks you. -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] [Evolution] Exchange MAPI Connector
Le mardi 23 octobre 2007 à 12:58 +0530, Srinivasa Ragavan a écrit : On Tue, 2007-10-23 at 09:16 +0200, Frederic Crozat wrote: Le mardi 23 octobre 2007 à 12:07 +0530, Srinivasa Ragavan a écrit : Hello everyone, For Evolution 2.22 we should be having MAPI based Exchange connector which developed in parallel with Openchange based libmapi. The team is currently working on that and the code is currently maintianed at GNOME SVN in EXCHANGE_MAPI_BRANCH (both for evolution and evolution-data-server) http://svn.gnome.org/viewvc/evolution/branches/EXCHANGE_MAPI_BRANCH/ http://svn.gnome.org/viewvc/evolution-data-server/branches/EXCHANGE_MAPI_BRANCH/ I created the branch yesterday and we committed our week long effort there. We now have a working account setup plugin, base camel/calendar code and a partially working addressbook impl. Things should get to a working shape in another week or two. I hope that soon, Johnny would be able to create a OpenSUSE Build Service repository (rpms for OpenSUSE, Fedora, Ubuntu and few more) for Evolution and its dependencies so that users can install the rpms and get a feel of it even before the release. Please, remember to notify release-team and everybody else on desktop-devel about the new introduced external dependency for evolution-data-server and evolution. Frederic, I dont think we can take it as a enforced dependency right away as libmapi depends on Samba4 which is just in aplha1 now. It might take a while before Samba4 releases and we take that and libmapi as external dependencies. Im not sure if we can make/ask those alpha versions as external dependencies. Anyways thanks for the information and the trigger :) Well, even if it is a optional external dependencies, it should be announced, moreover because of the samba 4 implied dependency and the GPLv3 compatibility issue it brings. There is never too much information to announce ;) -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Exchange MAPI Connector
Le mardi 23 octobre 2007 à 13:01 +0530, Srinivasa Ragavan a écrit : On Tue, 2007-10-23 at 09:19 +0200, Jules Colding wrote: On Tue, 2007-10-23 at 12:07 +0530, Srinivasa Ragavan wrote: Hello everyone, For Evolution 2.22 we should be having MAPI based Exchange connector which developed in parallel with Openchange based libmapi. The team is currently working on that and the code is currently maintianed at GNOME SVN in EXCHANGE_MAPI_BRANCH (both for evolution and evolution-data-server) http://svn.gnome.org/viewvc/evolution/branches/EXCHANGE_MAPI_BRANCH/ http://svn.gnome.org/viewvc/evolution-data-server/branches/EXCHANGE_MAPI_BRANCH/ I created the branch yesterday and we committed our week long effort there. We now have a working account setup plugin, base camel/calendar code and a partially working addressbook impl. Things should get to a working shape in another week or two. I hope that soon, Johnny would be able to create a OpenSUSE Build Service repository (rpms for OpenSUSE, Fedora, Ubuntu and few more) for Evolution and its dependencies so that users can install the rpms and get a feel of it even before the release. Does this mean that evo + e-d-s will go GPLv3? Jules, as I replied in a previous email thread, Im working with Novell legal team to modify the license to either GPLV2 or later or dual-license Evolution/EDS under GPLv2 and GPLv3. I dont have yet received the final nod. But the mapi providers/plugins are developed under GPLv3 which can be a issue now, but may not be after the license change. Well, it will be also a problem for other applications linking with e-d-s libraries. -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Exchange MAPI Connector
Le mardi 23 octobre 2007 à 13:55 +0530, Srinivasa Ragavan a écrit : On Tue, 2007-10-23 at 09:53 +0200, Frederic Crozat wrote: Le mardi 23 octobre 2007 à 13:01 +0530, Srinivasa Ragavan a écrit : On Tue, 2007-10-23 at 09:19 +0200, Jules Colding wrote: On Tue, 2007-10-23 at 12:07 +0530, Srinivasa Ragavan wrote: Hello everyone, For Evolution 2.22 we should be having MAPI based Exchange connector which developed in parallel with Openchange based libmapi. The team is currently working on that and the code is currently maintianed at GNOME SVN in EXCHANGE_MAPI_BRANCH (both for evolution and evolution-data-server) http://svn.gnome.org/viewvc/evolution/branches/EXCHANGE_MAPI_BRANCH/ http://svn.gnome.org/viewvc/evolution-data-server/branches/EXCHANGE_MAPI_BRANCH/ I created the branch yesterday and we committed our week long effort there. We now have a working account setup plugin, base camel/calendar code and a partially working addressbook impl. Things should get to a working shape in another week or two. I hope that soon, Johnny would be able to create a OpenSUSE Build Service repository (rpms for OpenSUSE, Fedora, Ubuntu and few more) for Evolution and its dependencies so that users can install the rpms and get a feel of it even before the release. Does this mean that evo + e-d-s will go GPLv3? Jules, as I replied in a previous email thread, Im working with Novell legal team to modify the license to either GPLV2 or later or dual-license Evolution/EDS under GPLv2 and GPLv3. I dont have yet received the final nod. But the mapi providers/plugins are developed under GPLv3 which can be a issue now, but may not be after the license change. Well, it will be also a problem for other applications linking with e-d-s libraries. Since EDS is LGPLv2, it may not have much issues. IIRC when Harish moved EDS from GPL to LGPL, he made it LGPLv2 or later. (I'm not a licensing expert. Just posting from what we had discussed sometime back on e-h list). From what I see in SVN, EDS is still LGPLv2 only, not v2 or later. But I don't know what it would mean if E-D-S was linked with GPLv3 library (ie Samba 4), for other programs linking to E-D-S library, with an non GPLv3 compatible license (like explained on http://www.fsf.org/licensing/licenses/gpl-faq.html#AllCompatibility ) -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Exchange MAPI Connector
Le mardi 23 octobre 2007 à 11:07 +0200, Jules Colding a écrit : On Tue, 2007-10-23 at 13:55 +0530, Srinivasa Ragavan wrote: On Tue, 2007-10-23 at 09:53 +0200, Frederic Crozat wrote: Le mardi 23 octobre 2007 à 13:01 +0530, Srinivasa Ragavan a écrit : On Tue, 2007-10-23 at 09:19 +0200, Jules Colding wrote: On Tue, 2007-10-23 at 12:07 +0530, Srinivasa Ragavan wrote: Hello everyone, For Evolution 2.22 we should be having MAPI based Exchange connector which developed in parallel with Openchange based libmapi. The team is currently working on that and the code is currently maintianed at GNOME SVN in EXCHANGE_MAPI_BRANCH (both for evolution and evolution-data-server) http://svn.gnome.org/viewvc/evolution/branches/EXCHANGE_MAPI_BRANCH/ http://svn.gnome.org/viewvc/evolution-data-server/branches/EXCHANGE_MAPI_BRANCH/ I created the branch yesterday and we committed our week long effort there. We now have a working account setup plugin, base camel/calendar code and a partially working addressbook impl. Things should get to a working shape in another week or two. I hope that soon, Johnny would be able to create a OpenSUSE Build Service repository (rpms for OpenSUSE, Fedora, Ubuntu and few more) for Evolution and its dependencies so that users can install the rpms and get a feel of it even before the release. Does this mean that evo + e-d-s will go GPLv3? Jules, as I replied in a previous email thread, Im working with Novell legal team to modify the license to either GPLV2 or later or dual-license Evolution/EDS under GPLv2 and GPLv3. I dont have yet received the final nod. But the mapi providers/plugins are developed under GPLv3 which can be a issue now, but may not be after the license change. Well, it will be also a problem for other applications linking with e-d-s libraries. Since EDS is LGPLv2, it may not have much issues. IIRC when Harish moved EDS from GPL to LGPL, he made it LGPLv2 or later. (I'm not a licensing expert. Just posting from what we had discussed sometime back on e-h list). Generally it is a mess down there in the eds source license wise. Many files are LGPLv2 some are LGPLv2+ and many doesn't even have a license notice. Some samples: LGPLv2 only: http://svn.gnome.org/viewvc/evolution-data-server/branches/EXCHANGE_MAPI_BRANCH/addressbook/libebook/e-contact.c?revision=8126view=markup LGPLv2+: http://svn.gnome.org/viewvc/evolution-data-server/branches/EXCHANGE_MAPI_BRANCH/camel/camel-certdb.c?revision=8126view=markup No license header: http://svn.gnome.org/viewvc/evolution-data-server/branches/EXCHANGE_MAPI_BRANCH/addressbook/idl/Evolution-DataServer-Addressbook.idl?revision=8126view=markup To be fair, it is a mess in the entire GNOME stack ;) -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Request for improved svn commit messages
Le samedi 06 octobre 2007 à 00:46 +0530, Srinivasa Ragavan a écrit : Nice discussion guys. Lets go this way then. - Sync ChangeLogs with commit logs - Why instead of what in ChangeLogs It is just that I never saw a reason for myself and If people see a value out of it, lets help them then. Thanks you very much, this change will be greatly appreciated by many people ;) -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
[Evolution-hackers] Request for improved svn commit messages
Hi everyone, I'd like to suggest to Evolution hackers, whenever it is possible for them, to try to improve their svn commit messages. Some of you are currently using a very short commit message (something like fix for bug#xxx), which make reading svn commit extremely difficult without having to go each time on bugzilla to see what was the fix really for. Moreover, it also adds complexity when you are checking a file history and bump into such commits. May I suggest you use either the same ChangeLog entry you wrote in the various changelog file (so it is even faster, just use copy/paste :) or even a stripped version of it (it used to be extremely useful for CVS to see which files were changed at the same time, but it is no longer required with svn atomic commit) ? Thanks you in advance. -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Request for improved svn commit messages
Le vendredi 05 octobre 2007 à 13:36 +0530, Srinivasa Ragavan a écrit : Oh, I remember a thread on d-d-l where there was discussion on two ChangeLogs (one part of tree and other part of svn logs). Btw, I'm one of those who use those short logs for svn commits and I know a few people who copy ChangeLogs to svn commit logs. In anycase, I really dont know/see what is the benefit of this over the short messages. Many times with patches and review being on bugzilla, atleast I find easy to see what broke where with just the bug number part of commit logs over viewcvs. First, consistency : evolution/e-d-s are almost the only modules on GNOME using micro message for SVN commit. And it isn't even consistent across evolution maintainers ;) Second, being self-contained (and therefore, ease of use for external maintainers / lurkers / packagers / release-team). You are only thinking of svn log when using viewcvs. But if you are, just like me, subscribed to svn-commit mailing list, it is really much easier to see directly what it a commit purpose (fix a typo, a bug, etc) without having to rely on another tool / website. Same apply when using svn log command directly. It is the same reason why we ask people, when requesting freeze break, to attach patch to mail and not just a link to bugzilla :) (Just to be clear, this suggestion is not done with my release-team hat :) -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] evolution's UI, consistency and codebase
Le jeudi 31 mai 2007 à 07:19 +, Srinivasa Ragavan a écrit : Last point is, why is the mail view headers fixed (like not look like buttons) in 2.10 and not the other views as well (memos, calendars, contacts) In few themes, Ive seen that it looks like a table header, but not in all themes. If you have seen this 2.10, may be with a right theme. Im sure that this should be fixable in widgets/table. I don't think it would right to fix all the other themes for this. Well, speaking with my theme writer hat on, I'm forced to do some matching on ETable class name and so on to get a consistent rendering, compared to TreeView. -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] evolution's UI, consistency and codebase
Le jeudi 31 mai 2007 à 08:38 +, Srinivasa Ragavan a écrit : On Thu, 2007-05-31 at 10:24 +0200, Frederic Crozat wrote: Le jeudi 31 mai 2007 à 07:19 +, Srinivasa Ragavan a écrit : Last point is, why is the mail view headers fixed (like not look like buttons) in 2.10 and not the other views as well (memos, calendars, contacts) In few themes, Ive seen that it looks like a table header, but not in all themes. If you have seen this 2.10, may be with a right theme. Im sure that this should be fixable in widgets/table. I don't think it would right to fix all the other themes for this. Well, speaking with my theme writer hat on, I'm forced to do some matching on ETable class name and so on to get a consistent rendering, compared to TreeView. Right. IIRC the New button too had some similar issues, but that was resolved in 2.8.x. Not entirely : EComboButton still need to be treated differently for themes with rounded edges for buttons (like Ia Ora or Galaxy) otherwise the separations between both part of the button looks strange.. -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Missing svn tags for e-d-s / evolution 2.18 releases
Le lundi 21 mai 2007 à 19:24 +0200, Gilles Dartiguelongue a écrit : Le lundi 21 mai 2007 à 17:19 +0200, Frederic Crozat a écrit : Hi Evolution / E-D-S maintainers, it appears that since CVS to SVN migration, no evolution / e-d-s release was followed by a SVN tag creation in module_name/tags. These tags are very useful for you, maintainers but also for contributors and vendors when they try to search for changes between releases. Could you try to create those missing tags and make sure they are created when releasing new tarballs in the future (I guess somebody script was not migrated correctly to SVN ;) ? Thanks you in advance. in fact it seems evolution uses branches over tags evolution stable branch can be found at : http://svn.gnome.org/svn/evolution/branches/gnome-2-18 Branches and tags are different beast : -branches are used to do developement for a particular release of GNOME (here 2.18.x series) -tags are pointing each release (ie tarball generation), regardless of branches. -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Missing svn tags for e-d-s / evolution 2.18 releases
Le lundi 21 mai 2007 à 20:21 +0200, Gilles Dartiguelongue a écrit : Le lundi 21 mai 2007 à 18:03 +0200, Frederic Crozat a écrit : Le lundi 21 mai 2007 à 19:24 +0200, Gilles Dartiguelongue a écrit : Le lundi 21 mai 2007 à 17:19 +0200, Frederic Crozat a écrit : Hi Evolution / E-D-S maintainers, it appears that since CVS to SVN migration, no evolution / e-d-s release was followed by a SVN tag creation in module_name/tags. These tags are very useful for you, maintainers but also for contributors and vendors when they try to search for changes between releases. Could you try to create those missing tags and make sure they are created when releasing new tarballs in the future (I guess somebody script was not migrated correctly to SVN ;) ? Thanks you in advance. in fact it seems evolution uses branches over tags evolution stable branch can be found at : http://svn.gnome.org/svn/evolution/branches/gnome-2-18 Branches and tags are different beast : -branches are used to do developement for a particular release of GNOME (here 2.18.x series) -tags are pointing each release (ie tarball generation), regardless of branches. sorry I was unclear. I meant that afaics, evolution never tagged releases, or something definitely got lost in the cvs-svn transition. They did, check : svn ls http://svn.gnome.org/svn/evolution/tags/ | grep EVOL -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Missing svn tags for e-d-s / evolution 2.18 releases
Le lundi 21 mai 2007 à 16:36 +, Srinivasa Ragavan a écrit : Frederic, One reason why me and Harish didn't want to tag is that we are able to map the svn revision number to a particular release. I hope isn't so difficult to get that from the ChangeLog/configure.in/NEWS commit logs. At least that is how we do while preparing NEWS file for a dot release to know what went in since the last release. If you have better points, We are open for it. Nothing against it :) I don't really see what it causing problem here : just tags the release corresponding to the commit for configure.in / NEWS / Changelog. It isn't really a big problem if there is another commit for the tag operation in SVN. Or am I missing something ? -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Missing svn tags for e-d-s / evolution 2.18 releases
Le lundi 21 mai 2007 à 16:57 +, Srinivasa Ragavan a écrit : On Mon, 2007-05-21 at 18:57 +0200, Frederic Crozat wrote: Le lundi 21 mai 2007 à 16:36 +, Srinivasa Ragavan a écrit : Frederic, One reason why me and Harish didn't want to tag is that we are able to map the svn revision number to a particular release. I hope isn't so difficult to get that from the ChangeLog/configure.in/NEWS commit logs. At least that is how we do while preparing NEWS file for a dot release to know what went in since the last release. If you have better points, We are open for it. Nothing against it :) I don't really see what it causing problem here : just tags the release corresponding to the commit for configure.in / NEWS / Changelog. It isn't really a big problem if there is another commit for the tag operation in SVN. I didn't say it a problem. I'm saying that the TAG would map directly to a revision in svn which would be the revision of the commit of those files. You can achieve what you want with tag with just revision number itself. In case of CVS, you can't do this. If it is of difficulty to map to a revision, no problem in resuming that again. So, I've just discussed with sri over IRC : -we agreed tagging is less needed now we have SVN than years ago, in the CVS days. -nevertheless, since other GNOME modules are following the tagging convention and since it can be often more convenient to rely on tags when doing diff than digging into svn log, sri agreed to start back tagging evolution tree when doing releases. -in short, we are in agreement ;) Thanks again to Evolution team ! -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Why is GnomePrintContext still in GtkHtml?
Le jeudi 22 février 2007 à 13:46 +, Srinivasa Ragavan a écrit : Hi Frederic, We did update the GtkHTML versions under the assumptions of API extensions in 3.13.90. In 3.13.91 we have broken API/ABI and removed the obsolete APIs but we havent bumped the versions accordingly. We will be doing that in RC Monday. Thanks for pointing it out to us :) Thanks. Please add a big warning in the release announcement, since it breaks some applications like gnucash (which wasn't been ported to gtk-print). -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Reorganize Evolution's preferences dialog
Le jeudi 07 décembre 2006 à 11:05 +0530, Srinivasa Ragavan a écrit : Hi Matthew I think it is a pretty good idea :-). The two main reason are - Width is controlled by the number of tabs in Mail Preferences - Height is controlled by the General tab in Mail Preferences Another issue is l10n. I still haven't found time to fill proper bug reports but some l10n are expanding preferences dialogs a lot, and moreover, initial dialog placement is done before all tabs size are know, causing the correctly sized dialog to not be centered. -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Code Freeze Break Requests
Le vendredi 01 septembre 2006 à 15:27 +0200, Vincent Untz a écrit : Le vendredi 01 septembre 2006, à 18:54, Harish Krishnaswamy a écrit : Patch #1 Bug : http://bugzilla.gnome.org/show_bug.cgi?id=324118 Description : Remove IMAP4rev1 from stable releases Approval 1/2. Approval 2/2 Patch #2 Bug : http://bugzilla.gnome.org/show_bug.cgi?id=350250 Description : Show my message list from the cache first Quite a big patch. But I trust the evo team on this one. Approval 1/2. Same comment as vincent. Approval 2/2. Patch #3 Bug : http://bugzilla.gnome.org/show_bug.cgi?id=353763 Description : cannot enter text or edit memo summary field Approval 1/2. Approval 2/2 -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Camel in evolution-data-server, a different proposal
Le jeudi 13 juillet 2006 à 11:35 +0100, Ross Burton a écrit : On Thu, 2006-07-13 at 12:25 +0200, Philip Van Hoof wrote: Calendar data isn't being stored by the addressbook server either. That isn't a great argument. And I question ... do all applications that want to use calendaring (and only calendaring) have to depend on most of the Evolution components? Right now, if you translate that to Camel and E-mailing, it depends on which distribution you have. On most Redhat based ones: yes. On Debian based ones: no. Is there clarity? no. Is it making it more easy to develop a pure E-mail application and to document which dependencies you have (maybe even letting packagers share the same dependencies): no. The list of reasons (all valid ones, it's not because *you* mark them as rant that it also *is* rant) goes on and on and on. So you've found a problem with the Red Hat packaging, in that it treats all of EDS a single library. File a bug with Red Hat, and notice that Debian, Maemo, and OpenEmbedded (at least) already have split EDS packages. Mandriva too ;) -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Hard Patch Review Mode
Le mercredi 01 mars 2006 à 14:08 +0530, Srinivasa Ragavan a écrit : Hi, We are entering hard code freeze on March 6th. To prepare for that, let us make sure that *all* the patches with no exceptions should be mailed to the [EMAIL PROTECTED] list. It should be committed only after a *review* by the respective maintainers. And after approval from release-team ;) Please, get approval from evolution maintainers FIRST and when it is ok, ask for release-team approval. Thanks you. -- Frederic Crozat [EMAIL PROTECTED] Mandriva ___ Evolution-hackers mailing list Evolution-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-hackers
