Re: Bug 124906. I know what needs to be
done to fix it, but have not had cycles to do the change. It is kind of hard to
test, too, because it depends on an external event happening at just the wrong
time. A good test would require hitting the mark within 2 seconds.
Re: Documentation. Documentation continues
to be pushed back in favor of handling bugs. I have spent some time on it
today, and getting it organized is the first big hurdle. You modified the top
level of the Voice Tools documentation, with Getting Started, Concepts, Tasks,
and References. I keep thinking that each browser should be documented as an
entity, and reconciling those points of view is slowing me down.
I still have tomorrow.
I need to file a bug on the two Stop
button pushed dialogs which I mentioned earlier, and if I were to try to fix
anything, that happens much more readily than 124906.
-- Mike
From:
vtp-dev-bounces@xxxxxxxxxxx [mailto:vtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Brent D Metz
Sent: Wednesday, February 01, 2006
2:46 PM
To: vtp-dev@xxxxxxxxxxx
Subject: [vtp-dev] Moving thursday
development discussions online
Hi All,
Participation
in our weekly development call has waned over the past month to 3-4
participants. There are over 60 people signed up for vtp-dev and I don't want
to leave so many people out of the loop on development discussions. I believe
they have helped get the word out on what's going but that the point of
diminishing returns has been reached. For that reason I'd like to shift these
discussions to the mailing list so there is a better written record.
Let
me start up by reviewing the milestone plan, available at
http://www.eclipse.org/vtp/VTP_Milestone_Plan_1.0.html. The current plan has us
publishing a release candidate in two weeks with a release date of February 21,
subject to the approval of the Eclipse Technology PMC. While yesterday's
milestone release contains all of the function planned for the release, there
are still many things left to do on the project, including unit tests,
functional testing, bugzilla defect resolution, in-eclipse documentation, web
tutorials, mandated website look and feel updates, and preparation of materials
for the release review. These tasks all can benefit from help, even if the help
is just complaints about what you'd like to see that's missing.
One
portion of the release review is a discussion of the developer base. While I
have previously spoken to some of you directly about your company's product
plans with respect to the VTP I would like to hear more from others who are
using the VTP. Beyond download statistics this is a hard thing to quantify so I
am eager to hear from those of you out there who are finding it useful. This
information is helpful in showing to the PMC that the project has an ecosystem
of parties developing, extending, and directly using it.
Now
that we have a milestone out it is a good time to verify bugs in the bugzilla
database. If you have previously opened bugzilla bugs please install M2 and
make sure the bugs are properly resolved. You may do this by going to
https://bugs.eclipse.org/bugs/query.cgi and searching for bugs in the RESOLVED
state with you as the bug reporter will yield a list of bugs that need to be
verified.
Michael's
last day before he goes on a three week vacation is the third, so now would
also be a good time to actively try and break the Tellme browser :). Michael,
the only actionable bug I am seeing in bugzilla is 124906 (Remote chance user
will see log from previous session). Do you believe this will be resolved
before you leave? Also, any update on the status of documentation for the
Tellme browser?
--
Brent D. Metz
Enterprise
Voice Tools
bdmetz@xxxxxxxxxx
"Simple things should be simple, and complex things should be
possible." - Alan Kay