Closed Bug 334603 Opened 18 years ago Closed 18 years ago

[Meta] 0.7 Release

Categories

(Core Graveyard :: XForms, enhancement)

Product:
Core Graveyard
Component:
XForms
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: allan, Unassigned)

References

(
URL
)

Details

(Keywords: fixed1.8.0.8, fixed1.8.1.1)

Attachments

(3 files, 1 obsolete file)

patch 2 for 1.8.0
332.75 KB, patch
Details | Diff | Splinter Review
patch 3 for 1.8.0
33.74 KB, patch
Details | Diff | Splinter Review
patch 1 for 1.8.1
365.37 KB, patch
Details | Diff | Splinter Review
Depends on: 334604
Severity: normal → enhancement
Assignee: aaronr → xforms
Depends on: 348819
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.
Depends on: 347610
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.
Depends on: 331984, 334937, 339198
Depends on: 353159
A new erratum was published today for XForms 1.0 SE.
http://www.w3.org/2006/03/REC-xforms-20060314-errata.html
Depends on: 353715
Depends on: 353699
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?
Depends on: 316691, 321311, 329376, 331987, 352462, 353598
Depends on: 316354
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.
Depends on: 312956
I filed bug 353738 for 0.8 release to move there all bugs that will not be fixed for 0.7 version :)
Depends on: 353672
Depends on: 354309
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
Attachment #239592 - Attachment is obsolete: true
checked 'patch 2' into 1.8.0
Depends on: 354561
checked in bug 354561 and bug 353598 to 1.8.0.8, so they'll be in 0.7, too
Depends on: 355208
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
Depends on: 355314
(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.
Depends on: 355619
need bug 355743 to prevent a 0.6 to 0.7 regression.
Depends on: 355743
Moving out dependency on bug 321311 since xul:scale is available on trunk only.
No longer depends on: 321311
Depends on: 356199
No longer depends on: 356199
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.
No longer depends on: 334937, 339198
checked in bug 356342.  THAT should be our last checkin.
No longer depends on: 312956
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.
Attachment #242906 - Flags: approval1.8.1.1?
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.
Attachment #242906 - Flags: approval1.8.1.1?
Status: NEW → RESOLVED
Closed: 18 years ago
Keywords: fixed1.8.0.8, fixed1.8.1.1
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: