headers
Marcel Berteler | 1 Aug 2010 22:53
Picon

Re: Plans for the next calendar release

gNeandr wrote the following on 2010/07/31 18:57:
> It seems Marcel point's are well aligned with the very limited resources
> of the calendar team. Only that one point
>> - Continue to improve existing functionality on the Comm-1.9.2
> seems not to be appropriated.
> Focusing further developments to the new platform (M2.0) *only* makes
> much more sense.
>
> For me the example with TB2/TB3
>> When the decision was taken to stop developing for TB2 and focus on
>> TB3, this risk was 100% accepted and no mitigation was done. This did
>> not turn out to be the best decision as TB3 was delayed over and over
>> again and users where left with a stale product.

> sounds a bit different. TB2 was always supported with bug fixing /
> security updates. New features dropped into TB3 only (AFAIR). So anybody
> was able to decided for *his* TB solution.

TB2 was supported with bug fixes, but LN0.9 was the last release that 
supported TB2 and no bug fixes / security patches where done on the 
calendar project. That was way before TB3 was even considered safe or 
stable so there was no fair choice for the end user. They simply had to 
wait for TB3 to be released.

on 2008/10/02 I posted this question:

----
Am I correct is saying that what ever bug fixes are committed to LN 
after 0.9 release will not make it into a nightly or release that will 
work on TB2 and I am forced to move to TB3?
(Continue reading)

Permalink | Reply | 13 comments |
headers
gNeandr | 1 Aug 2010 23:48

Re: Plans for the next calendar release

  Just to make clear: the part of your posting "When the decision was 
taken to stop ... " is only speaking about TB! And that's what I was 
commenting! And all the discussion is ONLY about which track to support 
and which one to bring forward.
Yes, Lightning has a dependency with TB. But with respect to the 
resources they have this thread is about an acceptable way for *all* 
parties. Don't overload it with unrealistic expectations, that will 
never help.

So once more:
security and patches for the 'old' LG yes, but further developments 
*only* with M2.0.

Günter

  [01.08.2010 22:53]    »Marcel Berteler« wrote:
>>
>> For me the example with TB2/TB3
>>> When the decision was taken to stop developing for TB2 and focus on
>>> TB3, this risk was 100% accepted and no mitigation was done. This did
>>> not turn out to be the best decision as TB3 was delayed over and over
>>> again and users where left with a stale product.
>
>> sounds a bit different. TB2 was always supported with bug fixing /
>> security updates. New features dropped into TB3 only (AFAIR). So anybody
>> was able to decided for *his* TB solution.
>
> TB2 was supported with bug fixes, but LN0.9 was the last release that 
> supported TB2 and no bug fixes / security patches where done on the 
> calendar project. That was way before TB3 was even considered safe or
(Continue reading)

Permalink | Reply | 2 comments |

Warning: fopen(/var/tmp/weft/gmane/comp/mozilla/devel/calendar/16450): failed to open stream: No such file or directory in /home/httpd/gmane/php/lib.php on line 314
headers
Mark Banner | 5 Aug 2010 20:41
Favicon

Thunderbird 3.1.2 now available for download.

Thunderbird 3.1.2 is now available as a free download for Windows, Mac, 
and Linux from www.GetThunderbird.com. We recommend that users keep up 
to date with the latest stability and support versions of Thunderbird, 
and encourage all our users to upgrade to this very latest version. If 
you already have Thunderbird, you will receive an automated update 
notification within 24 to 48 hours. This update can also be applied 
manually by selecting “Check for Updates…” from the Help menu.

This releases fixes some stability issues and several user experience 
concerns.  For a list of changes and more information, please review the 
Thunderbird 3.1.2 release notes:

http://www.mozillamessaging.com/en-US/thunderbird/3.1.2/releasenotes/

Note: All Thunderbird 2 users are strongly encouraged to upgrade to 
Thunderbird 3.1.2 by downloading it from www.GetThunderbird.com
_______________________________________________
dev-apps-calendar mailing list
dev-apps-calendar <at> lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-calendar
Permalink | Reply | 0 comments |
headers
EricNo.SpamValette | 6 Aug 2010 16:19
Picon
Favicon

Re: Plans for the next calendar release

On 02/08/2010 11:55, Alan Lord (News) wrote:
> On 30/07/10 20:25, Philipp Kewisch wrote:
>>
>> I'd really appreciate some input from others too!
>
> Lightning is a very important extension for TB (probably the most
> important for me) and one that lets TB provide one of the few
> alternatives to Outlook that is cross platform. Which provides a great
> way to start migrating users off Proprietary software and Windows.
> Almost all the other major desktop apps are now catered for: OOo,
> Firefox, Chrome, Gimp, Inkscape etc.

I could not agree more. Unfortunately, the outlook compatibility has 
still a long way to be fully workable, especially now that outlook 2007 
version and soon 2010 version start finding they way in enterprise system.

You can more easily change clients than a complete mailing system when 
changing the server means no solution for remaining outlook users.

> My request is that Lightning is enhanced/fixed/developed in terms of
> features & functionality *before* porting to TB4. If TB3 was anything to
> go by, TB4 could be a long way away before it reaches stability/maturity.

Some recent post have shown that in term of memory consumption and cpu 
usage, thunderbird 3 itself has to mature a bit.

> So, if it were my decision, I'd concentrate on working on all the big
> bugs/feature requests in the current lightning platform first, then,
> when TB4 is nearing prime-time start the migration.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Philipp Kewisch | 6 Aug 2010 16:55
Picon

Re: Plans for the next calendar release

I agree that the decision to move to TB3 might not have been the best,
but at that point we had the feeling that Thunderbird 3 was just
around the corner. The Thunderbird team was also confident that they
would release soon, but things just didn't work out as expected. Yes,
we accepted the risk and shot ourselves in the foot. This is a past
decision that we can't undo. I still think that focusing on trunk is
the right thing to do, but we clearly are in need for a strategy to
still be able to bring out releases on the last branch if things take
longer. Note also that since the number of developers shrunk, it was
even less easy to backport fixes to 0.9.

There are various reasons to focus on trunk rather than the last
stable release. Back when Thunderbird 3 was released and we weren't
ready with Lightning, we had numerous complaints why Lightning wasn't
working with Thunderbird 3. I can imagine that we have lost more than
a few users due to this, I do hope they'll come back. The only way out
of this is to actively support two branches: keep the trunk nightly in
shape for the upcoming release of Thunderbird, and continue to fix the
last branch release. As Simon correctly mentioned we don't have enough
developer resources to do this. Doing so means double the QA, more
programming work since we need to backport features. Given that the
mozilla platform and also Thunderbird change substantially between
branches this is not just checking in the trunk patches on branch. For
example, the mozilla 1.8. branch forced us to some very horrible hacks
that we are really glad we got rid of. These hacks costed our
developers a great amount of time that I think could better be used to
fix bugs on trunk.

> The worst that can happen when continuing to enhance the TB3 version of
> Calendar is that the TB4 version will have less functionality compared
(Continue reading)

Permalink | Reply | 9 comments |

Gmane