None in this case. AFAIK the number in parenthesis is the number yesterday (which happens to be the same). Speaking of which.. Does anyone know where that neat graph someone made charting those numbers over the past few months went? I haven't seen it posted in a while.
Bugs nominated to block Firefox 1.0 = 99 (99) Bugs accepted to block Firefox 1.0 = 190 (190) Bugs blocking Firefox 1.0 and FIXED = 157 (157)
Whats the difference between the number inside and the number outside the parenthesis?
The first number is the current one, the number between parenthesis is the number we started with right after when the 20040803 Win32 branch build was released
crafteh wrote:Does "Regressions/confirmed/annoying bugs" mean bugs that have come back or were just created with the nightly?
It's a mix, some are regressions others are not, but placed there on request
Please, help:
In different tabs different languages should be active! For example, in one window I wrote in Russian, and having switched in other window English should be active and I do not need to switch constantly input languages!
I know that the Trunk of supposed to be the bleeding edge of the development and the branch is what is being worked on for 1.0. However, some of the fixes that get checked into the trunk seem somewhat important for the branch (1.0). If bugs aren't nominated to block 1.0 and they are fixed and checked into the trunk, does that mean that the branch will never see them?
DaCypher wrote:I know that the Trunk of supposed to be the bleeding edge of the development and the branch is what is being worked on for 1.0. However, some of the fixes that get checked into the trunk seem somewhat important for the branch (1.0). If bugs aren't nominated to block 1.0 and they are fixed and checked into the trunk, does that mean that the branch will never see them?
No, we will probably see some trunk fixes implemented in branch in the coming weeks, but only if they are really important and not create a range of regressions
DaCypher wrote:I know that the Trunk of supposed to be the bleeding edge of the development and the branch is what is being worked on for 1.0. However, some of the fixes that get checked into the trunk seem somewhat important for the branch (1.0). If bugs aren't nominated to block 1.0 and they are fixed and checked into the trunk, does that mean that the branch will never see them?
No, we will probably see some trunk fixes implemented in branch in the coming weeks, but only if they are really important and not create a range of regressions
Ok, it just seemed that some of the bugs (#253507 for example) aren't nominated to block 1.0 so a fix gets checked into the trunk and its marked as fixed. Do they have some type of internal tracking to later go back and add this to the branch? Or since it was never mentioned to have a large impact on 1.0, it gets put off until post-1.0?
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.
