Ticket #1483843 requests for a mass mark as read option. I would like to see this extended to mass flag/move option. It would be nice to select multiple mails and then move those to specific folder, as is possible with GMail and IlohaMail. For an individual mail this is already possible.
I can add this to the existing ticket or create a new one, but I'm wondering what the best way for feature requests is. I see things asked for on the mailing list being implemented right away while some tickets are entered a long time ago. In a few weeks, I probably (hopely) have some more spare time left, which I want to spent on the RC when required. I would like to dig through the list of open tickets and see of some of them have been solved in the meantime. But maybe it is better to do this when a second beta is to be released. Is a date for a new beta release already planned? It would be nice for those users who don't use SVN to benefit from all the great improvements made over the passed few months.
-- Regards, Erik
On Tue, 4 Jul 2006 14:01:20 +0200, Erik erik@prikbord.org wrote:
Ticket #1483843 requests for a mass mark as read option. I would like to see this extended to mass flag/move option. It would be nice to select multiple mails and then move those to specific folder, as is possible with GMail and IlohaMail. For an individual mail this is already possible.
This is already a feature in RC. Select multiple mails and drog and drop on the folder you want them to go.
I can add this to the existing ticket or create a new one, but I'm wondering what the best way for feature requests is. I see things asked for on the mailing list being implemented right away while some tickets are entered a long time ago. In a few weeks, I probably (hopely) have some more spare time left, which I want to spent on the RC when required. I would like to dig through the list of open tickets and see of some of them have been solved in the meantime. But maybe it is better to do this when a second beta is to be released. Is a date for a new beta release already planned? It would be nice for those users who don't use SVN to benefit from all the great improvements made over the passed few months.
You are totally right on this. I guess there isn't the enough interest in seeing the tickets as the come in. I'm really not sure if they have already been asighned to someone or not. Maybe the developers should get a quick notification of the tickets that get in the trac system, maybe they already do... I don't know.
Any way, I was going to send a mail in respect of this subject, basically asking if there is any intention of freezing the development at some time soon and getting all the bugs fixed and release a more stable version. Any ideas on this?
--
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador
On Tue, 4 Jul 2006 14:01:20 +0200, Erik erik@prikbord.org wrote:
Ticket #1483843 requests for a mass mark as read option. I would like to see this extended to mass flag/move option. It would be nice to select multiple mails and then move those to specific folder, as is possible with GMail and IlohaMail. For an individual mail this is already possible.
I think it's a fine idea, however, before we keep adding text links at the bottom perhaps we could have a dropdown to handle all of this funtionality? Right now it just doesn't go with all the icon links at the top.
I can add this to the existing ticket or create a new one, but I'm wondering what the best way for feature requests is. I see things asked for on the mailing list being implemented right away while some tickets are entered a long time ago. In a few weeks, I probably (hopely) have some more spare time left, which I want to spent on the RC when required. I would like to dig through the list of open tickets and see of some of them have been solved in the meantime. But maybe it is better to do this when a second beta is to be released. Is a date for a new beta release already planned? It would be nice for those users who don't use SVN to benefit from all the great improvements made over the passed few months.
I was just thinking the same thing, now with 'Draft' and 'Junk' folders, there are some real user available features (not just bug fixes) to show off. I love the way things are progressing.
P
-- Regards, Erik
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
-- http://fak3r.com - you don't have to kick it
On Tue, 4 Jul 2006 9:43:13 -0300, Martin Marques martin@bugs.unl.edu.ar wrote:
On Tue, 4 Jul 2006 14:01:20 +0200, Erik erik@prikbord.org wrote:
Ticket #1483843 requests for a mass mark as read option. I would like to see this extended to mass flag/move option. It would be nice to select multiple mails and then move those to specific folder, as is possible
with
GMail and IlohaMail. For an individual mail this is already possible.
This is already a feature in RC. Select multiple mails and drog and drop on the folder you want them to go.
That's true and I use this sometimes, but for some reason I keep moving the mouse pointer to the top the page to a drop down menu that's not there .... ;-)
It's just an idea, and i know that Thunderbird and Outlook don't have an option, but still it might be something more people would like to use instead of drag-drop.
On the other hand, once filters have been implemented, this might not be necessary anymore.
-- Regards, Erik -- mvg. Erik
On Tue, 4 Jul 2006 14:55:58 +0200, Erik erik@prikbord.org wrote:
On Tue, 4 Jul 2006 9:43:13 -0300, Martin Marques martin@bugs.unl.edu.ar wrote:
On Tue, 4 Jul 2006 14:01:20 +0200, Erik erik@prikbord.org wrote:
Ticket #1483843 requests for a mass mark as read option. I would like
to
see this extended to mass flag/move option. It would be nice to select multiple mails and then move those to specific folder, as is possible
with
GMail and IlohaMail. For an individual mail this is already possible.
This is already a feature in RC. Select multiple mails and drog and drop on the folder you want them to go.
That's true and I use this sometimes, but for some reason I keep moving the mouse pointer to the top the page to a drop down menu that's not there .... ;-)
It's just an idea, and i know that Thunderbird and Outlook don't have an option, but still it might be something more people would like to use instead of drag-drop.
On the other hand, once filters have been implemented, this might not be necessary anymore.
Ah, that makes more sense, I guess I never think of it since I have all of mail handled via procmail on the server, so the server side filters silently take care of that. Before I had that setup though it was a pain dragging ever little bit around.
P
-- Regards, Erik -- mvg. Erik
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
-- http://fak3r.com - you don't have to kick it
On Tue, 4 Jul 2006 7:56:18 -0500, phil phil@cryer.us wrote:
Ah, that makes more sense, I guess I never think of it since I have all of mail handled via procmail on the server, so the server side filters silently take care of that. Before I had that setup though it was a pain dragging ever little bit around.
Ah right, procmail, that makes sense to me ;-) That would be an option for me I guess, as I have access to the system, but for 'web-only-users' this is going to be difficult. And I'm not going to do that for them. Ach well, they'll just have to wait for filters to be implemented then ;-)
-- Regards, Erik
On Tue, 4 Jul 2006 15:04:52 +0200, Erik erik@prikbord.org wrote:
On Tue, 4 Jul 2006 7:56:18 -0500, phil phil@cryer.us wrote:
Ah, that makes more sense, I guess I never think of it since I have all
of
mail handled via procmail on the server, so the server side filters silently take care of that. Before I had that setup though it was a
pain
dragging ever little bit around.
Ah right, procmail, that makes sense to me ;-) That would be an option for me I guess, as I have access to the system, but for 'web-only-users' this is going to be difficult. And I'm not going to do that for them. Ach well, they'll just have to wait for filters to be implemented then ;-)
Yeah, it was brought up awhile ago to use the procmail or sieve (pref both) front end from Squirrelmail or Horde. All we'd have to do was to get it working as a standalone webpage, then migrate the style over to RC and put it under a Personal Settings tab. I used to use the Squirrel filters that were part of SM - not server side, and once you got lots of mail the system would just drag, so server side is the way to go. Using an existing project on this sounds like a no brainer, if I find time I'll look at it, but otherwise it'd be a quick win for anyone who wants to pick it up.
P
-- Regards, Erik
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
On Tue, 4 Jul 2006 14:55:58 +0200, Erik erik@prikbord.org wrote:
On Tue, 4 Jul 2006 9:43:13 -0300, Martin Marques martin@bugs.unl.edu.ar wrote:
This is already a feature in RC. Select multiple mails and drog and drop on the folder you want them to go.
That's true and I use this sometimes, but for some reason I keep moving the mouse pointer to the top the page to a drop down menu that's not there .... ;-)
Well, I guess you have to get used to it. I personally don't like new features that are already present, but that's my point of view. ;-)
On the other hand, once filters have been implemented, this might not be necessary anymore.
This made me change the subject of the thread... what features are need to get a stable 1.0 version out? As I said in an earlier mail, maybe a freeze in the coding would be good to concentrate on the existing bugs, and then get a new beta out.
--
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador
On Tue, 4 Jul 2006 10:16:55 -0300, Martin Marques martin@bugs.unl.edu.ar wrote:
This made me change the subject of the thread... what features are need to get a stable 1.0 version out? As I said in an earlier mail, maybe a freeze in the coding would be good to concentrate on the existing bugs, and then get a new beta out.
I think a start would be to collect all known bugs and feature requests and insert those into the ticket system properly. I've got the feeling this is not yet the case and many things get discussed on mailing list only. These than have to be prioritized and eventually assigned to a developer. Deciding on priority automatically boils down to the needed features for a release, as lower priotity means later release.
-- Regards, Erik
On Tue, 4 Jul 2006 15:29:41 +0200, Erik erik@prikbord.org wrote:
I think a start would be to collect all known bugs and feature requests and insert those into the ticket system properly. I've got the feeling this is not yet the case and many things get discussed on mailing list only. These than have to be prioritized and eventually assigned to a developer. Deciding on priority automatically boils down to the needed features for a release, as lower priotity means later release.
Yes, you are right, but as someone pointed out earlier today, things get done faster when they are sent to the mailling list, contrary of just adding a ticket. I had 2 tickets with patches that fixed the problem, and one of them got commit (thanks rich on that) after I asked on this list why it wasn't commit yet. Other things get done fast from the tickets.
The question then is if the developers have an horizon (not in time, but in efforts) of when a new beta will be out.
--
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador
Martin Marques wrote:
[...]
This made me change the subject of the thread... what features are need to get a stable 1.0 version out? As I said in an earlier mail, maybe a freeze in the coding would be good to concentrate on the existing bugs, and then get a new beta out.
There'a a beta2 planned to be released soon. I'm still working on the tickets because after the migration from SourceForge to Trac they're not properly assigned. As you can see, there are milestones that would make the prediction of upcoming releases more easy. Unfortunately, currently most tickets (Import!) are assigned to the 0.1beta2 which is not quite correct.
Just give me some more days (currently very busy at school) to get the tracker cleaned. There isn't much more than the current features for beta2 and once we have tested the new features, I'll create the release.
I agree with you suggestion to work on bug tickets rather than feature requests now.
Sorry for the bad project management but time, time, time...
Regards, Thomas
On Tue, 4 Jul 2006 10:34:15 -0300, Martin Marques martin@bugs.unl.edu.ar wrote:
On Tue, 4 Jul 2006 15:29:41 +0200, Erik erik@prikbord.org wrote:
I think a start would be to collect all known bugs and feature requests and insert those into the ticket system properly. I've got the feeling this
is
not yet the case and many things get discussed on mailing list only.
These
than have to be prioritized and eventually assigned to a developer. Deciding on priority automatically boils down to the needed features for a
release,
as lower priotity means later release.
Yes, you are right, but as someone pointed out earlier today, things get done faster when they are sent to the mailling list, contrary of just adding a ticket. I had 2 tickets with patches that fixed the problem, and one of them got commit (thanks rich on that) after I asked on this list why it wasn't commit yet. Other things get done fast from the tickets.
These are two different things:
- report problem
- provide patch through mailing list and ask if it can be applied
And my opinion is that 2 cannot be done without 1, and then why not use tickets, as that is want they are ment for. And I prefer tickets as this provides some sort of documentation. Also to new users. For example, feature request which have been added and discussed on mailing list and then denied, don't get requested for a second time. These discussions and decisions then also have to be added to the wiki and documentation, so that it is clear to everyone what is being done and when (or why not).
I realize that everyone involved has to agree on workflow, especially developers and those started the project (as it is their project).
Tickets and wiki provide decent documentation for current developers and users, but even more for new users and developers. Because I think a project like this, with its growing popularity every day, can only get better and really succeed when these things are also covered well.
-- Regards, Erik
On Tue, 04 Jul 2006 15:42:04 +0200, Thomas Bruederli roundcube@gmail.com wrote:
Martin Marques wrote:
[...]
This made me change the subject of the thread... what features are need
to get a stable 1.0 version out? As I said in an earlier mail, maybe a freeze in the coding would be good to concentrate on the existing bugs, and then get a new beta out.
There'a a beta2 planned to be released soon. I'm still working on the tickets because after the migration from SourceForge to Trac they're not properly assigned. As you can see, there are milestones that would make the prediction of upcoming releases more easy. Unfortunately, currently most tickets (Import!) are assigned to the 0.1beta2 which is not quite correct.
Excelent. Any help you need, just ask.
--
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador
On Tue, 4 Jul 2006 15:55:40 +0200, Erik erik@prikbord.org wrote:
On Tue, 4 Jul 2006 10:34:15 -0300, Martin Marques martin@bugs.unl.edu.ar wrote:
Yes, you are right, but as someone pointed out earlier today, things get done faster when they are sent to the mailling list, contrary of just adding a ticket. I had 2 tickets with patches that fixed the problem,
and
one of them got commit (thanks rich on that) after I asked on this list why it wasn't commit yet. Other things get done fast from the tickets.
These are two different things:
- report problem
- provide patch through mailing list and ask if it can be applied
And my opinion is that 2 cannot be done without 1, and then why not use tickets, as that is want they are ment for. And I prefer tickets as this provides some sort of documentation. Also to new users. For example, feature request which have been added and discussed on mailing list and then denied, don't get requested for a second time. These discussions and decisions then also have to be added to the wiki and documentation, so that it is clear to everyone what is being done and when (or why not).
My patches were attached to the ticket. I asked the list why they weren't commit, but patches were in the ticket. :-D
--
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador
-
Erik -
Martin Marques -
phil -
Phil Cryer
-
Thomas Bruederli