Erik wrote:

On Fri, 14 Jul 2006 11:28:12 +0200, Thomas Bruederli roundcube@gmail.com wrote:

...

I finally made it to go through the most tickets and assigned a set of bugs that IMO need to be fixed for the next milestone. There are now 16 pending tickets assigned to milestone 0.1beta2: http://trac.roundcube.net/trac.cgi/query?status=new&status=assigned&...

OK, nice job. Is this list open for discussion or are these it?

The list is just my opinion. Of course we can discuss it. I just don't like to have much more tickets for that milestone because we will never be able to publish a new release.

...

It looks like I will have some time again to work on the project for the next couple of weeks. Let's try to get rid of those 16 tix and we're ready to publish a new release. This will also be the first release that is "planned" with the Trac system and a proof of success of that platform.

Please catch yourself some unassigned tickets and help finish this milestone.

My Ajax skills aren't at a high level yet, so I won't interfere with those for now. I will start with documentation and information in the wiki, as that needs some work as well.

-- Regards, Erik

Thomas Bruederli wrote:

Please catch yourself some unassigned tickets and help finish this milestone.

I reopened ticket #1143200 http://trac.roundcube.net/trac.cgi/ticket/1443200

It's a pretty simple fix. The change I suggested the first time merely needs to be copied to the 3 other places it shows up in the same file. I didn't notice it showed up more than once.

A diff is on the ticket. Should be an easy one to close out.

Thanks! Jim

On Fri, 14 Jul 2006 11:28:12 +0200, Thomas Bruederli roundcube@gmail.com wrote:

Hi everybody

I finally made it to go through the most tickets and assigned a set of bugs that IMO need to be fixed for the next milestone. There are now 16 pending tickets assigned to milestone 0.1beta2: http://trac.roundcube.net/trac.cgi/query?status=new&status=assigned&...

There are some tickets missing there[1], like this one:

http://trac.roundcube.net/trac.cgi/ticket/1343964

It looks like I will have some time again to work on the project for the next couple of weeks. Let's try to get rid of those 16 tix and we're ready to publish a new release. This will also be the first release that is "planned" with the Trac system and a proof of success of that platform.

Please catch yourself some unassigned tickets and help finish this milestone.

I'll try to see the encoding problem, because it's very important for my users (spanish speaking people). I may even add another ticket related to encoding problems.

P.D.: Has anybody checked the problem with autosaving not working asyncronically (in the AJAX fashion)?

[1]: How should tickets be assigned? If I find a bug in the SVN version, which milestone do I assign it to?

--

Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador

On Fri, 14 Jul 2006 07:01:28 -0700 (PDT), Eric Stadtherr estadtherr@gmail.com wrote:

There's one feature request that I was hoping would make it into the next release - #1455740 [1]

How does everyone else feel about this feature?

What kind of flag? Important, read/unread, answered? I guess there code be a menu for each message where you could toggle any of the posible mail flags.

Personally, I wouldn't add the feature to the beta2 release. I would leave it for later, as it's not a bug and it would demand doing it and debugging it latter.

--

Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador

Since you are working on polish 0.1beta2, I included some things (easy to do) that I think should be considered for the new beta.

1. Fixes to Spanish localization found on RC SVN Trunk 274, adding new

translated strings that where introduced in the latter trunks. http://trac.roundcube.net/trac.cgi/ticket/1483887

2. This one is a bug, also easy to fix. Currently RC do not provide a

way to modify date format of emails that arrive Today. Only provide short and long date formats. http://trac.roundcube.net/trac.cgi/ticket/1483879

Both tickets include patches to roundcube.

Thanks in advance

Mario Vazquez System Administrator Mundolink.Net

On 7/17/06, Eric Stadtherr estadtherr@gmail.com wrote:

Your logic is sound - this certainly isn't a bug, just a feature that is common to most e-mail clients. I would categorize it as a "must have" for a "1.0" release, but I agree it would be better to focus on defects for beta2. The IMAP v4r1 spec (RFC 3501) defines a "\Flagged" message attribute (§2.3.2). Many e-mail clients (Thunderbird/Mozilla-Messenger, Apple Mail) use this boolean "flag" to mark a message without making assumptions about what the flag means. M$ Outlook takes this a little further and gives you 5 or 6 flags that can be assigned names and colors within the client. IMAP implementations are allowed to define additional keywords (which may be what Outlook uses for its flags), but this single "\Flagged" attribute is a part of the spec that I think we should support. Read/Unread is a separate flag (see the "\Seen" attribute), as is Answered (the "\Answered" attribute).

On Sat, 15 Jul 2006 10:59:36 -0300, Martin Marques wrote:

On Fri, 14 Jul 2006 07:01:28 -0700 (PDT), Eric Stadtherr wrote:

...

There's one feature request that I was hoping would make it into the next release - #1455740 [1]

How does everyone else feel about this feature?

What kind of flag? Important, read/unread, answered? I guess there code be a menu for each message where you could toggle any of the posible mail flags.

Personally, I wouldn't add the feature to the beta2 release. I would leave it for later, as it's not a bug and it would demand doing it and debugging it latter.

--

Lic. Martín MarquÃ(c)s | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador

---

again i would like to mention these two bugs as they are pretty easy to resolve:

http://trac.roundcube.net/trac.cgi/ticket/1483845 http://trac.roundcube.net/trac.cgi/ticket/1483846

if they are allready fixed in the repository, please resolve these tickets!

kind regards, raoul bhatia

Eric Stadtherr wrote:

Here's another one to consider: #1483820

I put the details of the fix into the ticket (it's a one-character fix - can't beat that!)

On Fri, 14 Jul 2006 11:28:12 +0200, Thomas Bruederli wrote:

Hi everybody

I finally made it to go through the most tickets and assigned a set of
bugs that IMO need to be fixed for the next milestone. There are now 16
pending tickets assigned to milestone 0.1beta2:
http://trac.roundcube.net/trac.cgi/query?status=new&status=assigned&status=reopened&milestone=0.1-beta2

It looks like I will have some time again to work on the project for the
next couple of weeks. Let's try to get rid of those 16 tix and we're
ready to publish a new release. This will also be the first release that
is "planned" with the Trac system and a proof of success of that platform.

Please catch yourself some unassigned tickets and help finish this
milestone.

Thanks!
Thomas