Bugs to fix for 1.0b3

[Philipp Kewisch]

I'd like to discuss the bugs we should fix for the next calendar
release. I've propsed a very conservative list of 26 bugs that I think
make sense for the next release. Only 7 of them are not assigned and
many already have patches, but I think its better that we complete
this list early (and create a new one) than to postpone the next
release longer.

The goal is to release again in about 4 months, which means around
december.

Please let me know what you think of this list and which bugs might be
missing. Please remember that we need the manpower to fix these bugs,
so no gigantic features that take a long time to fix. Note also there
may be a few obvious bugs I forgot, recent regressions are of course
needed too. If those bugs are not already marked [needed beta] or
[needed chemspill], please let me know.

Here's the link to the bug query:
http://bit.ly/cLGKaJ

Thanks,
Philipp

[Philipp Kewisch]

Note: I'm going to reflect this list in bugzilla (i.e whiteboard
flags) at the end of this week if there are no major objections.

[Mark Banner]

On 08/08/2010 23:25, Philipp Kewisch wrote:
> Here's the link to the bug query:
> http://bit.ly/cLGKaJ

I think you should add
https://bugzilla.mozilla.org/show_bug.cgi?id=573568 onto your list.

Personas is likely to become more prominent in TB 3.2 and although that
affects only some personas, when it does show up it looks really bad.

Standard8

[Stefan Sitter]

In addition I suggest to check the list of bugs fixed after 1.0b2 and
port them back to comm-1.9.2:
<https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&query_format=advanced&product=Calendar&target_milestone=1.0b3>

[Stefan Sitter]

The following bugs are marked as fixed for 1.0b3:
https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+:calendar+milestone:1.0b3+resolution:FIXED

But they are only checked-in to comm-central, i.e. none of them is fixed
for 1.0b3.

How to proceed? How to nominate bugs that should be ported back to
comm-1.9.2, i.e. 1.0b3? What target version to use in bugs fixed for
1.1a1pre only?

Stefan

[Philipp Kewisch]

On Aug 24, 11:09 pm, Stefan Sitter <ssitter+n...@gmail.com> wrote:
> The following bugs are marked as fixed for 1.0b3:https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL+:calendar+mi...

>
> But they are only checked-in to comm-central, i.e. none of them is fixed
> for 1.0b3.
>
> How to proceed? How to nominate bugs that should be ported back to
> comm-1.9.2, i.e. 1.0b3? What target version to use in bugs fixed for
> 1.1a1pre only?
>
> Stefan

I'm not quite sure how to proceed here. I guess bugs with [needed
beta] automatically have approval for comm-1.9.2, and we need to file
a bug for a new target milestone. I'd suggest to just call the target
milestone "Trunk", this way we don't have to decide on a specific
version. Possibly we could rename the "Future" milestone, its only
used on three bugs. Stefan, do you think we should do the backporting
now?

Philipp

[Stefan Sitter]

Philipp Kewisch wrote:
> I'm not quite sure how to proceed here. I guess bugs with [needed
> beta] automatically have approval for comm-1.9.2, and we need to
> file a bug for a new target milestone. I'd suggest to just call the
> target milestone "Trunk", this way we don't have to decide on a
> specific version. Possibly we could rename the "Future" milestone,
> its only used on three bugs. Stefan, do you think we should do the
> backporting now?

I'd vote for porting them back as soon as possible. The comm-central
builds are not usable since a long time. Therefore most of the fixed
bugs could not be tested, verified or checked for regressions yet.

[Philipp Kewisch]

Sounds good. I'll take a look at whats been checked in and put
together a list of patches to be backported. I'll post my results as a
suggestion here and then proceed with setting approval-1.9.2 flags. I
hope we don't irritate the mozilla drivers, we might want to check
with them first.

Stefan, could you do me a favor and file bugs to do the milestone
renaming/adding?