This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 856 - [RELEASE] 0.7.0 Release Metabug
Summary: [RELEASE] 0.7.0 Release Metabug
Status: RESOLVED FIXED
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.7.0
Hardware: All All
: P1 blocker
Target Milestone: 0.7.0
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on: 70 89 98 109 120 128 139 192 193 194 204 213 214 736 747 749 752 772 773 789 838 860 861 863 864 866 915 1071 1184 1392 1393
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-01 10:42 UTC by Terje Bless
Modified: 2006-10-31 06:45 UTC (History)
0 users

See Also:


Attachments

Description Terje Bless 2004-09-01 10:42:23 UTC
To nominate bugs for fixing, or to make sure they make the Release Notes, set
them to Block this bug. Other random notes for the Release Notes can be added
as comments on this bug.
Comment 1 Bj 2004-09-06 20:33:03 UTC
Here are Bugs that are better addressed later than 0.7.0

Bug #749 -- fixing this would suggest quite some re-design
Bug #862 -- major and controversial layout change
Bug #336 -- major and controversial change esp. if XHTML 1.1 is involved
Bug #301 -- I think this is better addressed with using S::P::O than an interim 
Bug hack
Bug #298 -- I agree with Terje's comment
Bug #297 -- I also suggest postponing such changes until S::P::O happens
Bug #197 -- this should wait until we use Encode.pm which provides similar means
Bug #194 -- ISO-8859-11 won't be registered any time soon, pointless to wait 
for Bug it
Bug #193 -- wait for Encode.pm
Bug #192 -- this is a major and problematic change, lets do this later
Bug #139 -- should wait for S::P::O
Bug #131 -- I am opposed to do this for *all* XHTML docs, should wait for 
S::P::O too
Bug #98 -- I am not too fond of the idea to list all these in the form
Bug #78 -- *Very* unlikely that this will happen in the next few weeks
Bug #75 -- this requires some major work and there are design issues...
Bug #68 -- better addressed with a proper S::P::O infrastructure
Bug #65 -- well... there is no solution yet
Bug #63 -- I agree with comment #1
Comment 2 Olivier Thereaux 2004-09-09 06:31:11 UTC
A certain number of these are on the verge of being closed already (Bug #80, #81, #82, #139, #194, 
#193)

Most of the "must do before any release" seem to have been fixed, with probably the notable exception 
of #860 ATM.

#89, #70, #109, #739 seem to fit in the "good idea" category and could probably be addressed rapidly.

#75 #192 #197 #204 #213 #298 #301 and #749 either seem to be too much work for little outcome 
(e.g #75) or would benefit from/be easier to do with our future modularized arch. 

 #131 and #336 need discussion it seems, before we even targetting one version or another.
Comment 3 Bj 2004-09-09 06:38:01 UTC
"""
A certain number of these are on the verge of being closed already (Bug #80, 
Bug #81, Bug #82, Bug #139, Bug #194, Bug #193)

Most of the "must do before any release" seem to have been fixed, with probably 
the notable exception of Bug #860 ATM.

Bug #89, Bug #70, Bug #109, Bug #739 seem to fit in the "good idea" category 
and could probably be addressed rapidly.

Bug #75, Bug #192, Bug #197, Bug #204, Bug #213, Bug #298, Bug #301 and Bug 
#749 either seem to be too much work for little outcome (e.g Bug #75) or would 
benefit from/be easier to do with our future modularized arch. 

Bug #131 and Bug #336 need discussion it seems, before we even targetting one 
version or another.
"""
Comment 4 Olivier Thereaux 2004-09-09 06:55:15 UTC
Thank you  Björn.
Comment 5 Ville Skyttä 2004-09-15 21:23:10 UTC
Ok, here's my take on the blocker list.  As the general idea, IMO we should
focus on completing the transition and "architectural" changes introduced so far
since 0.6.x, and then release 0.7.0.

Real blockers:
Transition incomplete, would be regressions: bug 89, bug 860, bug 861.
Bug 838 is unfortunate, but unless fixed, far too much "feedback" expected.

Nice to have:
These are more long standing issues, and since I currently think that finishing
what has been started first would have the high priorities, I wouldn't consider
these as blockers for 0.7.0.  bug 48, bug 63, bug 65, bug 68, bug 78, bug 109,
bug 196, bug 213, bug 301, bug 336, bug 749, bug 752.

Not important now: bug 75, bug 297.

Undecided:
Bug 739 is an implementation detail, dunno enough about it (yet?) to be able to
really comment.  And Tabtastic (bug 862) looks cool, but there was a broader
discussion about the UI a while back, including some folks volunteering to
help/advice/comment/(re)design it.
Comment 6 Olivier Thereaux 2005-05-16 05:51:55 UTC
A few more  recent candidates:
Bug 1184 is almost fixed, only need to do some more testing
Bug 1393 is template related, MUST fix (added to dependency tree)
Bug 1399 would be nice to close before a release
Comment 7 Olivier Thereaux 2005-05-17 05:25:57 UTC
Also tracking Bug #1392 (template-related) here, and reassigning the metabug to myself. 
Comment 8 Olivier Thereaux 2005-08-05 00:44:06 UTC
all dependencies cleared.