Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Working for Firefox/Thunderbird 2.0

0 views
Skip to first unread message

Ricardo Palomares Martinez

unread,
Apr 23, 2006, 5:05:49 PM4/23/06
to
Hi,

It seems that I'm going to take over Óscar M. Gómez Senovilla on
shared components and Thunderbird es-ES localization (I will probably
register myself to get write access to CVS). I haven't been able to
find references about if we should be already working for Fx/Tb 2.0
versions. I suppose this is the case, as the roadmap for 2.0 versions
talks about a release at Q2/Q3-2006.

If so, we should use MOZILLA_1_8_BRANCH, isn't it? Are we already
somewhat behind schedule, or shouldn't we expect too many changes?

TIA

--
If it's true that we are here to help others,
then what exactly are the OTHERS here for?

Axel Hecht

unread,
Apr 24, 2006, 9:23:36 AM4/24/06
to
Ricardo Palomares Martinez wrote:
> Hi,
>
> It seems that I'm going to take over Óscar M. Gómez Senovilla on
> shared components and Thunderbird es-ES localization (I will probably
> register myself to get write access to CVS). I haven't been able to
> find references about if we should be already working for Fx/Tb 2.0
> versions. I suppose this is the case, as the roadmap for 2.0 versions
> talks about a release at Q2/Q3-2006.

Q3 it is.

> If so, we should use MOZILLA_1_8_BRANCH, isn't it? Are we already
> somewhat behind schedule, or shouldn't we expect too many changes?

You should still expect quite a few changes to happen in places land.

I suggest that you work on both the MOZILLA_1_8_BRANCH and the trunk,
that should mostly build in synch.
Look on devmo for cross-commit, that tool can help you to check-in fixes
on both.

Axel

Ricardo Palomares Martinez

unread,
Apr 24, 2006, 3:47:26 PM4/24/06
to
Axel Hecht escribió:

> You should still expect quite a few changes to happen in places land.
>
> I suggest that you work on both the MOZILLA_1_8_BRANCH and the trunk,
> that should mostly build in synch.
> Look on devmo for cross-commit, that tool can help you to check-in fixes
> on both.


URL for cross-commit, in case anyone is suffering from laziness: :-)
http://developer.mozilla.org/en/docs/Using_cross_commit

One thing I'm not sure if I'm getting it right. If we work on both
branches (the trunk and MOZILLA_1_8_BRANCH) using cross-commit, we
actually only keep local copy of one of them, and therefore we're
assuming that every change made on the en-US original of that one has
also been made on the other one (I doubt I'm clear enough to get
myself understood). Am I right? If so, which branch should we use at
this moment? MOZILLA_1_8_BRANCH or the trunk?

Thanks a lot for your answer.

Axel Hecht

unread,
Apr 25, 2006, 4:29:54 AM4/25/06
to

So, places died on the 1.8 branch. This means that considerable amounts
of UI and strings will be reverted to 1.5+ and we will see localization
differences between trunk and 1.8.

My proposal would be, work on 1.8, and if you check in a fix, look at
the tinderbox, or make a guess, on wether that should land on the trunk,
too.

The bottom line is, you need to get the MOZILLA_1_8_BRANCH in a happy
state, we will release 2.0 from that.
It depends on your personal skill set which way is the easiest to get
that work re-used on the trunk, which is what will lead to 3.0. I doubt
that I can give a general rule here.

Axel

0 new messages