Re: [Evolution] Msg Selection
On Tue, 2010-06-15 at 22:44 -0400, Matthew Barnes wrote: On Tue, 2010-06-15 at 21:31 -0400, Philippe LeCavalier wrote: If you click a folder Evo forces the auto-selection of the newest unread message and worked back from there. It's not that sophisticated. It remembers the highlighted message ID and automatically selects that when you return to the folder. If that message doesn't exist or isn't visible, it either selects the first in the list or none at all, depending on the context. Is that configurable in any way? I like my newest mail to be at the end (bottom) of a list. The jump to first in list is mildly annoying in such circumstances, especially in folders with a lot of mail. Now I know /why/ this is happening I can try to work around it; hadn't realised that that was what was causing it. G -- %~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~% Dr. Gavin Simpson [t] +44 (0)20 7679 0522 ECRC, UCL Geography, [f] +44 (0)20 7679 0565 Pearson Building, [e] gavin.simpsonATNOSPAMucl.ac.uk Gower Street, London [w] http://www.ucl.ac.uk/~ucfagls/ UK. WC1E 6BT. [w] http://www.freshwaters.org.uk %~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~% ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection
On Wed, 2010-06-16 at 07:30 +0100, Gavin Simpson wrote: On Tue, 2010-06-15 at 22:44 -0400, Matthew Barnes wrote: On Tue, 2010-06-15 at 21:31 -0400, Philippe LeCavalier wrote: If you click a folder Evo forces the auto-selection of the newest unread message and worked back from there. It's not that sophisticated. It remembers the highlighted message ID and automatically selects that when you return to the folder. If that message doesn't exist or isn't visible, it either selects the first in the list or none at all, depending on the context. To add to what matt has said, the message would also be unselected if evolution terminates abruptly, either by a crash or process kill (evolution --force-shutdown). This is to ensure that we don't keep crashing on start-up selecting the same message. Is that configurable in any way? I like my newest mail to be at the end (bottom) of a list. The jump to first in list is mildly annoying in such circumstances, especially in folders with a lot of mail. Now I know /why/ this is happening I can try to work around it; hadn't realised that that was what was causing it. Its not configurable. - Chenthill. G ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] API Reference guide to write internet application by using evolution backend
On Thu, 2010-06-10 at 17:44 +0530, Vijay Khurdiya wrote: Hello, I want to write my own application for integrated mail, addressbook and calendaring functionality by using evolution as backend. can anyone guide me what is the best way to start. Please let me know where is API reference guide available or any sample code for me to start. http://live.gnome.org/Evolution/ has some useful information. - Chenthill. ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection
On Tue, 2010-06-15 at 22:44 -0400, Matthew Barnes wrote: On Tue, 2010-06-15 at 21:31 -0400, Philippe LeCavalier wrote: If you click a folder Evo forces the auto-selection of the newest unread message and worked back from there. It's not that sophisticated. It remembers the highlighted message ID and automatically selects that when you return to the folder. If that message doesn't exist or isn't visible, it either selects the first in the list or none at all, depending on the context. So in order to achieve the desired effect I'll have to sort by date, descending so that I have the newest on top. The annoying thing about that solution is that I think Evo seems to default to the exact opposite and isn't each folder setting independent? PHil ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection
On Wed, 2010-06-16 at 06:24 -0400, Philippe LeCavalier wrote: On Tue, 2010-06-15 at 22:44 -0400, Matthew Barnes wrote: On Tue, 2010-06-15 at 21:31 -0400, Philippe LeCavalier wrote: If you click a folder Evo forces the auto-selection of the newest unread message and worked back from there. It's not that sophisticated. It remembers the highlighted message ID and automatically selects that when you return to the folder. If that message doesn't exist or isn't visible, it either selects the first in the list or none at all, depending on the context. So in order to achieve the desired effect I'll have to sort by date, descending so that I have the newest on top. The annoying thing about that solution is that I think Evo seems to default to the exact opposite and isn't each folder setting independent? PHil ___ Ooops. Apparently I'm loosing my mind and had already asked that question. http://www.mail-archive.com/evolution-list@gnome.org/msg12356.html Sorry for the double post. I guess I'm finding this more annoying than originally thought. Phil ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection
On Wed, 2010-06-16 at 07:30 +0100, Gavin Simpson wrote: On Tue, 2010-06-15 at 22:44 -0400, Matthew Barnes wrote: On Tue, 2010-06-15 at 21:31 -0400, Philippe LeCavalier wrote: If you click a folder Evo forces the auto-selection of the newest unread message and worked back from there. It's not that sophisticated. It remembers the highlighted message ID and automatically selects that when you return to the folder. If that message doesn't exist or isn't visible, it either selects the first in the list or none at all, depending on the context. Is that configurable in any way? I like my newest mail to be at the end (bottom) of a list. The jump to first in list is mildly annoying in such circumstances, especially in folders with a lot of mail. Now I know /why/ this is happening I can try to work around it; hadn't realised that that was what was causing it. I'm in the same boat. I've complained about it in the past (so long ago I can't even remember) but to no effect, I suspect because the devels probably use the default newest at the top layout. In my view the algorithm should be: Show the last selected message if it still exists else show the oldest unread message in the folder, if any else show the newest message in the folder This is independant of the sorting order. poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection/date ordering
On Wed, 2010-06-16 at 13:10 +0530, chen wrote: Is that configurable in any way? I like my newest mail to be at the end (bottom) of a list. The jump to first in list is mildly annoying in such circumstances, especially in folders with a lot of mail. Now I know /why/ this is happening I can try to work around it; hadn't realised that that was what was causing it. Its not configurable. - Chenthill. brewster: This is interesting, and raises an additional question or two. I always get my newest at the bottom, and here's how... I have over twenty different folders, for things like interest areas, personal business categories, or e-group memberships, like this group. I tend to leave a lot of messages in the folders, because I will eventually perform differing operations on various ones, depending upon the subject, and I don't always have time to do those things right away. So where new (unread) messages show up is decidedly an issue. I sort by date, oldest first. So my unreads generally appear at the bottom, unless they're a spam dated 1969 which somehow slipped through the filters :-) But here's an Evo artifact I have never understood - sometimes, not consistently, when I click on an unread to highlight that line, the entire body of messages will shift around, usually pushing the bottom ones off the screen. There does not appear to be any logical purpose for this motion, and worst, it doesn't always take place. Has anyone else encountered this phenomenon? The other one that is a bit disconcerting is that there seems to be a bug in Evo's reporting on the left-hand pane where the folders list appears, of how many unreads are in a given folder. I can be staring right at a main screen that shows all eight messages in a folder, with every single one of the eight displaying as read, yet the left-hand list pane entry shows that folder as having one (or sometimes two) unread messages. Has anyone else noticed that one? Thanks, Brewster -- *** Embrace a sharing community of sustainable justice low-carbon diversity *** W. Brewster Gillett b...@fdi.usPortland, OR USA *** Simply because you don't like to hear it, that doesn't make it untrue. *** ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection/date ordering
On Wed, 2010-06-16 at 07:32 -0700, Brewster Gillett wrote: I sort by date, oldest first. So my unreads generally appear at the bottom, unless they're a spam dated 1969 which somehow slipped through the filters :-) Sort by Received Date and you take care of that. The sender's date is often pure fantasy. But here's an Evo artifact I have never understood - sometimes, not consistently, when I click on an unread to highlight that line, the entire body of messages will shift around, usually pushing the bottom ones off the screen. There does not appear to be any logical purpose for this motion, and worst, it doesn't always take place. Has anyone else encountered this phenomenon? Not sure what you mean here. When you say the messages shift around, do you mean the sort order changes? Also, do you have threading enabled? Threading modifies the strict date order. The other one that is a bit disconcerting is that there seems to be a bug in Evo's reporting on the left-hand pane where the folders list appears, of how many unreads are in a given folder. I can be staring right at a main screen that shows all eight messages in a folder, with every single one of the eight displaying as read, yet the left-hand list pane entry shows that folder as having one (or sometimes two) unread messages. Has anyone else noticed that one? Yes, it's a known bug and is quite annoying. If you're talking about IMAP folders you can sometimes fix it by unsubscribing from the folder and resubscribing it. This forces Evo to update everything. I can't recall seeing the bug on non-IMAP folders. poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection
On Wed, 2010-06-16 at 09:20 -0430, Patrick O'Callaghan wrote: On Wed, 2010-06-16 at 07:30 +0100, Gavin Simpson wrote: On Tue, 2010-06-15 at 22:44 -0400, Matthew Barnes wrote: On Tue, 2010-06-15 at 21:31 -0400, Philippe LeCavalier wrote: If you click a folder Evo forces the auto-selection of the newest unread message and worked back from there. It's not that sophisticated. It remembers the highlighted message ID and automatically selects that when you return to the folder. If that message doesn't exist or isn't visible, it either selects the first in the list or none at all, depending on the context. Is that configurable in any way? I like my newest mail to be at the end (bottom) of a list. The jump to first in list is mildly annoying in such circumstances, especially in folders with a lot of mail. Now I know /why/ this is happening I can try to work around it; hadn't realised that that was what was causing it. I'm in the same boat. I've complained about it in the past (so long ago I can't even remember) but to no effect, I suspect because the devels probably use the default newest at the top layout. In my view the algorithm should be: Show the last selected message if it still exists else show the oldest unread message in the folder, if any else show the newest message in the folder This is independant of the sorting order. poc Patrick, That is /exactly/ what I not only want but would expect as a logical sorting. To do the opposite -which is the default in Evo, goes against logic. We always advocate/preach on this list about logical order, namely top vs. bottom posting and the like, yet we're faced with this, rather contradicting flow. Assuming there is already been a request for this is there anything that can be done to push that through? Phil ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection/date ordering
On Wed, 2010-06-16 at 10:29 -0430, Patrick O'Callaghan wrote: The other one that is a bit disconcerting is that there seems to be a bug in Evo's reporting on the left-hand pane where the folders list appears, of how many unreads are in a given folder. I can be staring right at a main screen that shows all eight messages in a folder, with every single one of the eight displaying as read, yet the left-hand list pane entry shows that folder as having one (or sometimes two) unread messages. Has anyone else noticed that one? Yes, it's a known bug and is quite annoying. If you're talking about IMAP folders you can sometimes fix it by unsubscribing from the folder and resubscribing it. This forces Evo to update everything. I can't recall seeing the bug on non-IMAP folders. I see this on usenet newsgroups quite regularly. But it's been a long time (probably years) that I have seen this on imap. -- Han Pilmeyer pilux_at_pilmeyer_dot_nl ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection/date ordering
On Wed, 2010-06-16 at 20:18 +0200, Han Pilmeyer wrote: On Wed, 2010-06-16 at 10:29 -0430, Patrick O'Callaghan wrote: The other one that is a bit disconcerting is that there seems to be a bug in Evo's reporting on the left-hand pane where the folders list appears, of how many unreads are in a given folder. I can be staring right at a main screen that shows all eight messages in a folder, with every single one of the eight displaying as read, yet the left-hand list pane entry shows that folder as having one (or sometimes two) unread messages. Has anyone else noticed that one? Yes, it's a known bug and is quite annoying. If you're talking about IMAP folders you can sometimes fix it by unsubscribing from the folder and resubscribing it. This forces Evo to update everything. I can't recall seeing the bug on non-IMAP folders. I see this on usenet newsgroups quite regularly. But it's been a long time (probably years) that I have seen this on imap. I don't use Evo for newsgroups, but most of my mail is on IMAP servers and I do see it from time to time. poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection
On Wed, 2010-06-16 at 12:49 -0400, Philippe LeCavalier wrote: On Wed, 2010-06-16 at 09:20 -0430, Patrick O'Callaghan wrote: On Wed, 2010-06-16 at 07:30 +0100, Gavin Simpson wrote: On Tue, 2010-06-15 at 22:44 -0400, Matthew Barnes wrote: On Tue, 2010-06-15 at 21:31 -0400, Philippe LeCavalier wrote: If you click a folder Evo forces the auto-selection of the newest unread message and worked back from there. It's not that sophisticated. It remembers the highlighted message ID and automatically selects that when you return to the folder. If that message doesn't exist or isn't visible, it either selects the first in the list or none at all, depending on the context. Is that configurable in any way? I like my newest mail to be at the end (bottom) of a list. The jump to first in list is mildly annoying in such circumstances, especially in folders with a lot of mail. Now I know /why/ this is happening I can try to work around it; hadn't realised that that was what was causing it. I'm in the same boat. I've complained about it in the past (so long ago I can't even remember) but to no effect, I suspect because the devels probably use the default newest at the top layout. In my view the algorithm should be: Show the last selected message if it still exists else show the oldest unread message in the folder, if any else show the newest message in the folder This is independant of the sorting order. poc Patrick, That is /exactly/ what I not only want but would expect as a logical sorting. To do the opposite -which is the default in Evo, goes against logic. We always advocate/preach on this list about logical order, namely top vs. bottom posting and the like, yet we're faced with this, rather contradicting flow. Assuming there is already been a request for this is there anything that can be done to push that through? Wish I knew. I'm not a devel and have no insight into how their minds work :-) In fact I thought I had filed a BZ report a long time ago but I can't seem to find it. Feel free to file it yourself and post the BZ number here for others to add comments. poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection/date ordering/POC
Brewster wrote: The other one that is a bit disconcerting is that there seems to be a bug in Evo's reporting on the left-hand pane where the folders list appears, of how many unreads are in a given folder. I can be staring right at a main screen that shows all eight messages in a folder, with every single one of the eight displaying as read, yet the left-hand list pane entry shows that folder as having one (or sometimes two) unread messages. Has anyone else noticed that one? POC: Yes, it's a known bug and is quite annoying. If you're talking about IMAP folders you can sometimes fix it by unsubscribing from the folder and resubscribing it. This forces Evo to update everything. I can't recall seeing the bug on non-IMAP folders. I don't use Evo for newsgroups, but most of my mail is on IMAP servers and I do see it from time to time. poc Brewster chimes in: This is probably the juncture at which I need to point out that I am using strictly POP in this home network... no IMAP anywhere hereabouts to the best of my knowledge :-) Brewster -- *** Embrace a sharing community of sustainable justice low-carbon diversity *** W. Brewster Gillett b...@fdi.usPortland, OR USA *** Simply because you don't like to hear it, that doesn't make it untrue. *** ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] Current network connection state
Hi you all, could someone please explain me how Evolution gets the current network connection state (going offline when the Internet connection gets down) and if this would be easy to implement in other mail programmes (like Sylpheed)? Thanks in advance! Best regards Raphael ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Current network connection state
On Wed, 2010-06-16 at 23:37 +0200, Raphael Frey wrote: could someone please explain me how Evolution gets the current network connection state (going offline when the Internet connection gets down) and if this would be easy to implement in other mail programmes (like Sylpheed)? Thanks in advance! NetworkManager's D-Bus service. We call its state() method at startup to get the current network state, and listen for StateChanged signals thereafter. The code is here: http://git.gnome.org/browse/evolution/tree/modules/network-manager/evolution-network-manager.c If some parts look complex it's only because we're using raw libdbus calls. The logic should get much simpler once it's ported to GDBus. ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection/date ordering/POC
On Wed, 2010-06-16 at 14:15 -0700, Brewster Gillett wrote: I don't use Evo for newsgroups, but most of my mail is on IMAP servers and I do see it from time to time. poc Brewster chimes in: This is probably the juncture at which I need to point out that I am using strictly POP in this home network... no IMAP anywhere hereabouts to the best of my knowledge :-) That makes it even wierder. If it were a question of synch problems with a remote server one could let it pass, as these things can be tricky, but all POP info is completely local. In particular, the notion of which messages have been read doesn't depend on anything on the server. poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Current network connection state
On Wed, 2010-06-16 at 18:47 -0400, Matthew Barnes wrote: On Wed, 2010-06-16 at 23:37 +0200, Raphael Frey wrote: could someone please explain me how Evolution gets the current network connection state (going offline when the Internet connection gets down) and if this would be easy to implement in other mail programmes (like Sylpheed)? Thanks in advance! NetworkManager's D-Bus service. We call its state() method at startup to get the current network state, and listen for StateChanged signals thereafter. It should be pointed out that this works only when the interface is managed by NetworkManager. Since that depends on how the user's system is configured, Why does Evo say I'm offline when I'm not? is becoming a frequently-asked question both on this list and on others (the Fedora list for example). poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Msg Selection
On Wed, 2010-06-16 at 16:39 -0430, Patrick O'Callaghan wrote: Wish I knew. I'm not a devel and have no insight into how their minds work :-) In fact I thought I had filed a BZ report a long time ago but I can't seem to find it. Feel free to file it yourself and post the BZ number here for others to add comments. poc ___ Hopefully this will get /some/ attention... The BZ # is 621839 Cheers, Phil ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Current network connection state
On Wed, 2010-06-16 at 23:37 +0200, Raphael Frey wrote: Hi you all, could someone please explain me how Evolution gets the current network connection state (going offline when the Internet connection gets down) and if this would be easy to implement in other mail programmes (like Sylpheed)? Thanks in advance! NetworkManager via D-bus. http://live.gnome.org/NetworkManager http://projects.gnome.org/NetworkManager/developers/spec-08.html http://www.freedesktop.org/wiki/Software/dbus http://dbus.freedesktop.org/doc/dbus-tutorial.html -- Adam Tauno Williams awill...@whitemice.org LPIC-1, Novell CLA http://www.whitemiceconsulting.com OpenGroupware, Cyrus IMAPd, Postfix, OpenLDAP, Samba ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] How our minds work (was: Msg Selection)
On Wed, 2010-06-16 at 16:39 -0430, Patrick O'Callaghan wrote: Wish I knew. I'm not a devel and have no insight into how their minds work :-) In fact I thought I had filed a BZ report a long time ago but I can't seem to find it. Feel free to file it yourself and post the BZ number here for others to add comments. Here's some insight, at least from my perspective: There are 4698 outstanding bugs on file for Evolution and related modules, of which 1452 are enhancement requests. The bug backlog spans ten years, far longer than most of us have even been on the team. There are four, maybe five full-time developers left (myself included) and we all work for open source companies that have their own products to be maintained, which takes priority over upstream development (which, I think it's safe to say, we all prefer doing). I'd say at least half of the roughly one million lines of the code we're maintaining was written by developers no longer on the team. When I have time for upstream development and I'm not already engrossed in some mini-project for an upcoming release [1], I turn to my bugs folder which holds emails Bugzilla sends me when a new bug is filed or an existing one is updated. The mails are sorted by date and I tend to pick from the top, which means new bugs and noisy bugs tend to get my time and attention. Bugs that aren't resolved immediately and go silent usually get lost in the stack as new bugs stream in: out-of-sight means out-of-mind. I think my work flow is fairly typical of all of us. Best way to get our time and attention is to add constructive comments to the bug. Evolution being an open source project obviously source code patches are ideal, but also helpful are screen shots, click by click reproducer steps, complete gdb back traces or valgrind logs (for the more technically savvy reporters)... and for enhancements: UI mock ups (even if hand-drawn and scanned), algorithmic steps, thinking through corner cases... basically anything that makes the bug easier to solve. Or just ask what you can do to help. It doesn't guarantee an immediate response -- we're all swamped -- but it at least puts the bug back on top of our bugs folder where we're more likely to flag it to come back to later. What not to do: - Post obnoxious or nagging comments about the bug not being fixed yet. - Post me too comments, especially of the form I still see this bug in $SOME_UNSUPPORTED_VERSION. If you're not running at least the latest stable release (currently 2.30.1), don't bother commenting. - Post the same stack trace over and over. As long as the first trace has all the debugging info we need, you're good. If we need another trace, we'll ask. - Raise a bug's priority or severity setting in hopes of getting our attention. Those fields are meaningless to us for the most part precisely because anyone can come along and change them. I hope this is somewhat helpful or enlightening. [1] http://live.gnome.org/Evolution/Planning30 ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] How our minds work (was: Msg Selection)
On Wed, 2010-06-16 at 21:39 -0430, Patrick O'Callaghan wrote: A few questions: 1) Is the bug queue growing or shrinking? Perhaps there isn't a simple answer to that, but nearly 5000 outstanding bugs for 4 or 5 full-time devels is a lot. No doubt there's some overlap between them, and not all are equally urgent, but still. We have bug masters finding dupes and closing out obsolete or already fixed bugs, and developers trying to keep up with new and active bugs. Overall, seems to be a wash. 2) Do you have an rough estimate of what proportion of fixed issues correspond to enhancement requests? How about bugs or ERs related to Exchange? Pretty low ratio. ERs-to-bugs is already ~25% and a lot of bugs are just quick fixes. ERs tend to take awhile. No idea about Exchange. Two of our devs work on Exchange: one full-time, one half-time. 3) How are bugs and ERs prioritized? As it gets close to release time we try to identify important bugs to focus on, but otherwise I think we're mostly autonomous. Partly because we're scattered across time zones (India / Europe / North America) and have only a small overlapping window each day (for me, early a.m.), and partly because we're all just focused on different parts of Evolution. You seem to imply a LIFO ordering, so what is a reporter supposed to do when a report is old but still not dealt with? Perhaps some people mess with the priority/severity fields because they don't know what to do (though IIRC I've never done this myself). I don't really have a definitive answer other than what I already suggested. Patches almost always helps, constructive comments in bugs sometimes helps, discussing it on the mailing list sometimes helps, hopping on the IRC channel or even the monthly IRC meetings [1] and engaging us in real time sometimes helps. Other times we're just too busy to address it that day or that week or even that month. Also, if the priority/severity indicators are meaningless, why are they there? It's a standard form for all projects using GNOME Bugzilla. Small, tightly-knit projects might even use them effectively. For us, there's just too many bugs. I hope you don't think I was being snide. I've made a number of ERs over the years and seen one or two being accepted. The fact that most of the time one gets little or no feedback about these things makes it hard to have a mental model of how they're dealt with. No, that was more about comments with the maturity level of WTF, this bug has been opened for 4 years! What have you people been doing!? No wonder Evolution still sucks! I'm not exaggerating. Incoming enhancement requests tend to get marked as such, stamped with appropriate topic keywords [2] and thrown on the pile. Not because we don't care, but because a lot of them require a large time investment, possibly having to rethink deep or long-standing design decisions. But as long as they sound relatively sane I never close them no matter how old they are. Bugzilla is a gold mine of good ideas and every so often I like to go in there with a pickaxe. [1] http://projects.gnome.org/evolution/meetings.shtml [2] http://live.gnome.org/Evolution/BugzillaTopics ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] Updating evolution 2.24.5 to 2.30.1
Hello, Evolution 2.24.5 is currently installed in my Fedora 10. I have downloaded and extracted 2.30.1 to my home folder. Now, how do I update 2.24.5 to 2.30.1? Thanks, Larry ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Updating evolution 2.24.5 to 2.30.1
On Wed, 2010-06-16 at 10:30 -0700, larrysl...@znet.com wrote: Hello, Evolution 2.24.5 is currently installed in my Fedora 10. I have downloaded and extracted 2.30.1 to my home folder. Now, how do I update 2.24.5 to 2.30.1? Thanks, Larry Kindly stop asking the same question over and over again. You've already asked that question at least twice and been answered. Asking it again is not going to change the answer. You need to update your system to Fedora 13. Support for F10 by the Fedora Project has now ceased and you should no longer be using it as it doesn't even get security updates. Evolution 2.30 requires Gnome 2.30, which is only supported on F13. The alternative is to download the Evo source and compile it with all the supporting Gnome stuff it needs, which will have to be installed in a parallel tree. It's not an easy thing to do and you won't find many people willing to help you with something that is essentially pointless and error-prone. poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] From column not showing email address in 2.28.3
Hi, I am having a bit of a weird problem with my installation of Evolution. First off let me list what I am using. Kubuntu Linux 10.04 LTS Evolution 2.28.3 Evolution MAPI plugin 0.28.3 I have successfully connected to my company's Exchange server using the MAPI plugin and I was able to download all my mail, contacts, tasks and calendar items. This was great. The only problem was that in the Mail section where I see the list of emails. The column labeled From appears to be blank. The only place it is filled are for really old emails that are about a year old. Every new email that arrives shows the email address or name in the From column, but not for any of the older emails previous to that. I can't find anything about this on bugzilla and the ubuntu forms are leaving me to a dead end. Anyone here have an idea what could be causing this? Thanks much appreciated. -- George george@gmail.com ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
