W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > April 2008

Pushing to 1.0

From: Sean Owen <srowen@google.com>
Date: Tue, 1 Apr 2008 12:16:02 -0400
Message-ID: <e920a71c0804010916u76a292dr37c3e9abaceb340b@mail.gmail.com>
To: public-mobileok-checker <public-mobileok-checker@w3.org>

http://www.w3.org/Bugs/Public/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=mobileOK+Basic+checker&content=

I closed 2 more bugs and reassigned 1, and that concludes the bugs
that are assigned to me. I'm unfortunately just about finally out of
time to work on this. I'll be around in the working group for some
time, enough to release 1.0. But now the question is, what else *must*
be done, and can folks in the group commit to fix, before 1.0? are
there any other known issues out there, perhaps culled from
validator.w3.org/mobile logs, that are known to happen "in the field"?

While I'm in favor of making it as good as possible, not everything
has to be fixed for 1.0 in order for it to be a valid, successful
release, and I'm judging that there may not be enough developer-hours
available to do so anyway. Some issues are important but some are
basically enhancements, or corner cases. So whatever is left: is it
important enough that it must be fixed? if so can you commit to fix
it, or are you sure someone else can? if not, it's either not actually
that important, or we have a bit of a problem. :)

I'll get on fixing any bugs I've caused, and that one open issue about
XSLT and base hrefs. But let's be practical and think realistically
about what we have to do to get to 1.0 by the end of April.
Received on Tuesday, 1 April 2008 16:16:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 April 2008 16:16:40 GMT