We'd like to do landing slots for these (in the above order) so we don't have a last-minute dash to the freeze. Each of the above changes should land separately from the other (e.g. with a full tbox cycle between them). Other smaller changes are still clear to land up to the freeze tonight. After the freeze we'll continue landing these big changes. So:
a) Can the above named folks coordinate their landings appropriately? b) If you have a big change can you make sure to get on this list? c) We are gecko feature frozen as of tonight - so if you have a feature or any change that is exposed to content you should either get on this list or defer to 1.9.1 or moz2.
Because I'm in EET (UTC+2), I could land xml:id early afternoon tomorrow when it is night or very early morning in PDT. ...hoping ofc that tinderbox is green then, especially all perfboxes.
> We'd like to do landing slots for these (in the above order) so we > don't have a last-minute dash to the freeze. Each of the above > changes should land separately from the other (e.g. with a full tbox > cycle between them). Other smaller changes are still clear to land > up to the freeze tonight. After the freeze we'll continue landing > these big changes. So:
> a) Can the above named folks coordinate their landings appropriately? > b) If you have a big change can you make sure to get on this list? > c) We are gecko feature frozen as of tonight - so if you have a > feature or any change that is exposed to content you should either get > on this list or defer to 1.9.1 or moz2.
> Reply here if you have any thoughts or questions.
> b) If you have a big change can you make sure to get on this list?
I have SVG lighting filters ready to land, so would like to get on the list.
> c) We are gecko feature frozen as of tonight - so if you have a > feature or any change that is exposed to content you should either get > on this list or defer to 1.9.1 or moz2.
We have a number of SVG feature items which will be ready in the 1.9 timeframe:
* SVG tile filter * SVG displacement filter * SVG image filter * SVG text character positioning * SVG fonts
On Jul 25, 5:58 pm, T Rowley <t...@acm.org> wrote:
> On 7/25/07 1:55 PM, Schrep wrote:
> > b) If you have a big change can you make sure to get on this list?
> I have SVG lighting filters ready to land, so would like to get on the list.
k That's probably well contained so go ahead and land that.
> > c) We are gecko feature frozen as of tonight - so if you have a > > feature or any change that is exposed to content you should either get > > on this list or defer to 1.9.1 or moz2.
> We have a number of SVG feature items which will be ready in the 1.9 > timeframe:
> Because I'm in EET (UTC+2), I could land xml:id early afternoon > tomorrow when it is night or very early morning in PDT. > ...hoping ofc that tinderbox is green then, especially all perfboxes.
> -Olli
> Schrep wrote: > > Hey Folks,
> > Reminder that freeze is tonight. At the Gecko meeting today the > > following large changes yet to land were identified:
> > We'd like to do landing slots for these (in the above order) so we > > don't have a last-minute dash to the freeze. Each of the above > > changes should land separately from the other (e.g. with a full tbox > > cycle between them). Other smaller changes are still clear to land > > up to the freeze tonight. After the freeze we'll continue landing > > these big changes. So:
> > a) Can the above named folks coordinate their landings appropriately? > > b) If you have a big change can you make sure to get on this list? > > c) We are gecko feature frozen as of tonight - so if you have a > > feature or any change that is exposed to content you should either get > > on this list or defer to 1.9.1 or moz2.
> > Reply here if you have any thoughts or questions.
> > Best,
> > Schrep
How about early AM PDT assuming the dust has settled?
Schrep wrote: > Bug 17754 doesn't look ready to go (waiting on reviews)...
For what it's worth, this is a fairly self-contained change, that doesn't affect web sites unless users make use of this functionality. Depending on what the reviewers think, and depending on how usable it is, we should consider approving it in the next beta.
> On Jul 25, 5:58 pm, T Rowley <t...@acm.org> wrote: >> On 7/25/07 1:55 PM, Schrep wrote:
>>> b) If you have a big change can you make sure to get on this list? >> I have SVG lighting filters ready to land, so would like to get on the list.
> k That's probably well contained so go ahead and land that.
You mean, well contained besides touching DOMClassInfo and the style system? I'll look for a relatively quiet time to land it tonight.
>>> c) We are gecko feature frozen as of tonight - so if you have a >>> feature or any change that is exposed to content you should either get >>> on this list or defer to 1.9.1 or moz2. >> We have a number of SVG feature items which will be ready in the 1.9 >> timeframe:
> Do you mean will be ready after today? Today is the cutoff for this > kind of stuff....
Yes, after today. The resources for SVG are low, so things are ready when they're ready. The filters we want to add since it will complete the specified SVG 1.1 filters. SVG fonts are a frequently requested feature, and character positioning is of particular interest to a group who is working on implementing it.
Patches are in various states of completion for four of these five items, with the exception being the relatively straightforward displacement filter.
These changes are isolated to SVG, and given the current schedule are still acceptable from a risk/benefit point of view by the SVG module owner (me).
> These changes are isolated to SVG, and given the current schedule are > still acceptable from a risk/benefit point of view by the SVG module > owner (me).
While I respect your opinion as a module owner, this is not likely to be acceptable from a schedule or driver standpoint. We have been quite open and clear about feature freeze for gecko being M7 (formerly beta 1), since at least March. This in the newsgroups, the wiki schedule, and the weekly Gecko 1.9 meetings. Past M7, all checkins for 1.9 to Gecko will require driver approval, and while in past releases we have made exceptions to feature freezes for SVG, I do not believe we will do so for 1.9.
Gecko 1.9 has been two years in the making, the longest cycle without a release off the trunk in the project's history, and eventually we have to close the door to new features.
> > These changes are isolated to SVG, and given the current schedule are > > still acceptable from a risk/benefit point of view by the SVG module > > owner (me).
> While I respect your opinion as a module owner, this is not likely to > be acceptable from a schedule or driver standpoint. We have been > quite open and clear about feature freeze for gecko being M7 > (formerly beta 1), since at least March. This in the newsgroups, the > wiki schedule, and the weekly Gecko 1.9 meetings. Past M7, all > checkins for 1.9 to Gecko will require driver approval, and while in > past releases we have made exceptions to feature freezes for SVG, I > do not believe we will do so for 1.9.
> Gecko 1.9 has been two years in the making, the longest cycle without > a release off the trunk in the project's history, and eventually we > have to close the door to new features.
> -- Mike
The SVG tile filter that tor referred to is ready to land. Or at least will be within the next hour or so.
