About 1.1 features for branch Aaron said: This will be cool to have. But like the other 1.1 patches we've done and are being worked on, once the approvals are given this will only be checked into the trunk. Until the 1.1 spec reaches recommendation. That's looks reasonable but I'd like to see @mediatype output control (bug 347327) in 0.7. That's cool control and I guess we can keep it supported even if 1.1 specs will drop it. We can allow ourself it just because we have already controls that specs hasn't. What do you think?

I'd like to see bug 347610 here.

Also I'd like to see some range issues in 0.7. These are bug 348439, bug 331987 and bug 321311.

(In reply to comment #1) > About 1.1 features for branch Aaron said: > > This will be cool to have. But like the other 1.1 patches we've done and are > being worked on, once the approvals are given this will only be checked into > the trunk. Until the 1.1 spec reaches recommendation. > > That's looks reasonable but I'd like to see @mediatype output control (bug > 347327) in 0.7. That's cool control and I guess we can keep it supported even > if 1.1 specs will drop it. We can allow ourself it just because we have already > controls that specs hasn't. What do you think? > As with the other 1.1 stuff, my issue isn't if the spec drops it and we are supporting something unique to our processor. It is if the spec CHANGES it. And I don't like shipping stuff we aren't going to support. So that means supporting two versions of the same thing, which is "icky".

We should have special status whiteboard for such fixes if draft will become recommendation before 1.9 is out.

Add dependency on bug 331984, bug 334937 and bug 339198 that are supposed to be fixed in version 0.6.

A new erratum was published today for XForms 1.0 SE. http://www.w3.org/2006/03/REC-xforms-20060314-errata.html

first pass at patch to move trunk to branches for 0.7. This patch includes the fixes done for: bug 280368, bug 338135, bug 342473, bug 342227, bug 327239, bug 344246, bug 284068, bug 316609, bug 344180, bug 334503, bug 343905, bug 345865, bug 344621, bug 345506, bug 346325, bug 345729, bug 316614, bug 345224, bug 313313, bug 313768, bug 344379, bug 337250, bug 348867, bug 339075, bug 348689, bug 303865, bug 348439, bug 351879, bug 344473, bug 344387 and bug 331984

patch 1 also includes the schema-validation fixes for: bug 331897, bug 338005, bug 339247, bug 341672, bug 345907 and bug 353213

Adding several bugs: - derived types bugs: bug 329376 and bug 316691 - ally label click issue: bug 353598 - range issues: bug 352462, bug 331987 and bug 321311. Will Merle be in time to fix bug 316353?

Adding bug 312956 since he is on review stage and I still hope that it will be in time. The bug is important for js stuffs and that's fine to have it in 0.7.

I filed bug 353738 for 0.8 release to move there all bugs that will not be fixed for 0.7 version :)

This patch includes all the bugs from the previous patch plus: bug 353699, bug 353715, bug 353159, bug 353672, bug 351901, bug 352462, and bug 354309

checked 'patch 2' into 1.8.0

checked in bug 354561 and bug 353598 to 1.8.0.8, so they'll be in 0.7, too

We need to start thinking about getting 0.7 out. Soon. I still need to move bug 335082 and 355208 over to the 1.8.0 branch. bug 312956 - Alex, is this close to being ready? Should we still hold 0.7 for it? bug 316691 - I just need to change the bindings to use moz:typeList instead of moz:type. I'm fine if we do this in 0.8 but if we wait on other bugs long enough, I can quick get this bug done. bug 321311 - requires a code fix in core. Worth holding 0.7 for? bug 331987 - hopefully Merle will have done soon. I vote that we hold 0.7 for this since it is so close to being ready and will help us pass more testsuite testcases. bug 347610 and bug 348819 - documentation. I'd say nice to have, but not worth blocking the release. Let me know what you guys think. I'd rather not wait another month on this or we won't be able to get another preview out before everyone starts to take their Christmas breaks.

bug 355314 requested to be in 0.7 by user on NG

(In reply to comment #16) > We need to start thinking about getting 0.7 out. Soon. I still need to move > bug 335082 and 355208 over to the 1.8.0 branch. > > bug 312956 - Alex, is this close to being ready? Should we still hold 0.7 for > it? If we can then please. At least few days. > bug 316691 - I just need to change the bindings to use moz:typeList instead of > moz:type. I'm fine if we do this in 0.8 but if we wait on other bugs long > enough, I can quick get this bug done. My point is we should try to end up schema related things for controls before 0.7. > bug 321311 - requires a code fix in core. Worth holding 0.7 for? No, the bug goes on trunk since xul:scale defined there only. > bug 331987 - hopefully Merle will have done soon. I vote that we hold 0.7 for > this since it is so close to being ready and will help us pass more testsuite > testcases. I'm too. > bug 347610 and bug 348819 - documentation. I'd say nice to have, but not worth > blocking the release. Documentation is very important part. I'd vote to direct all forces what we can find to fix documentation related bugs. > Let me know what you guys think. I'd rather not wait another month on this or > we won't be able to get another preview out before everyone starts to take > their Christmas breaks. > I assume no more than one week. Documentations issue are big but they are simple to fix. The other bugs I guess shouldn't take a lot time too.

need bug 355743 to prevent a 0.6 to 0.7 regression.

Moving out dependency on bug 321311 since xul:scale is available on trunk only.

this patch includes patches for bug 355082, bug 355208, bug 331987, bug 355619, bug 355314, bug 355743 and bug 316691

checked 'patch 3' into 1.8.0. Should be our last checkin for 0.7.

Moving bug 334937 and bug 339198 to 0.8.

checked in bug 356342. THAT should be our last checkin.

leaving open. Need to get these patches in for 1.8.1

This patch will get 1.8.1 up to 0.7 level of code.

verified all of the 0.7 bugs are fixed by 'patch 1 for 1.8.1'

Comment on attachment 242906 [details] [diff] [review] patch 1 for 1.8.1 This patch is Not Part Of The Default Build, contains only xforms/schema-validation changes. Asking for approval to move bug into MOZILLA_1_8_BRANCH so that we can make the 0.7 version of our extension available for FF2.

got approval for NPOTDB for MOZILLA_1_8_BRANCH from jay and dveditz. Checked in 'patch 1 for 1.8.1' into MOZILLA_1_8_BRANCH last night.