Bug reporting
0 views
Skip to first unread message
MaggieL
Jun 4, 2009, 12:48:26 PM6/4/09
to Google Wave API
Having a method that works for bug searching and reporting (fixing
Buggy, perhaps?) should be a high priority. For example, I know that
*some* folks are seeing the "empty wave/Dr. Wave" problem, but I don't
know how many, who's found a good fix, and whether the Wave devs are
aware of the issue.
The WaveFAQ wave is turning into an informal bugtracker (and casual
information exchange, which is it's original purpose).
Seems like the Wave team didn't expect that the users were going to
use the sandbox more for communications than for extension
development.
Buggy, perhaps?) should be a high priority. For example, I know that
*some* folks are seeing the "empty wave/Dr. Wave" problem, but I don't
know how many, who's found a good fix, and whether the Wave devs are
aware of the issue.
The WaveFAQ wave is turning into an informal bugtracker (and casual
information exchange, which is it's original purpose).
Seems like the Wave team didn't expect that the users were going to
use the sandbox more for communications than for extension
development.
Brian Kennish (Googler)
Jun 4, 2009, 1:14:51 PM6/4/09
to google-...@googlegroups.com
> Having a method that works for bug searching and reporting (fixing
> Buggy, perhaps?) should be a high priority. For example, I know that
> *some* folks are seeing the "empty wave/Dr. Wave" problem, but I don't
> know how many, who's found a good fix, and whether the Wave devs are
> aware of the issue.
> Buggy, perhaps?) should be a high priority. For example, I know that
> *some* folks are seeing the "empty wave/Dr. Wave" problem, but I don't
> know how many, who's found a good fix, and whether the Wave devs are
> aware of the issue.
Hey, we do have a shiny, official place for bugs that takes care of
all the stuff you mention. Please put them here:
http://code.google.com/p/google-wave-resources/issues/list.
> Seems like the Wave team didn't expect that the users were going to
> use the sandbox more for communications than for extension
> development.
What, we thought there were no client bugs?! Just kidding, of course.
The client has a boatload (heh) of known bugs and unimplemented
features. And we, for sure, want to know if you find more. But the
reason we released it this early is to get developers developing, so
that's our main focus right now.
MaggieL
Jun 4, 2009, 5:40:13 PM6/4/09
to Google Wave API
On Jun 4, 1:14 pm, "Brian Kennish (Googler)" <byoo...@google.com>
wrote:
> What, we thought there were no client bugs?! Just kidding, of course.
> The client has a boatload (heh) of known bugs and unimplemented
> features. And we, for sure, want to know if you find more. But the
> reason we released it this early is to get developers developing, so
> that's our main focus right now.
themselves hands-on a bit before they will have the right visions for
writing extensions. So anything that impedes that is a blocker for
your main goal.
Off to look at the issues list now.
MaggieL
Jun 4, 2009, 7:14:10 PM6/4/09
to Google Wave API
> And we, for sure, want to know if you find more. But the
> reason we released it this early is to get developers developing, so
> that's our main focus right now.
Might make sense to give us access somehow to the "boatload" you
> reason we released it this early is to get developers developing, so
> that's our main focus right now.
already know about so we don't duplicate effort reporting them and we
can avoid them when planning to write extensions.
Brian Kennish (Googler)
Jun 5, 2009, 6:59:07 PM6/5/09
to google-...@googlegroups.com
On Thu, Jun 4, 2009 at 4:14 PM, MaggieL<margare...@gmail.com> wrote:
> Might make sense to give us access somehow to the "boatload" you
> already know about so we don't duplicate effort reporting them and we
> can avoid them when planning to write extensions.
> Might make sense to give us access somehow to the "boatload" you
> already know about so we don't duplicate effort reporting them and we
> can avoid them when planning to write extensions.
Good idea. There isn't a practical way to do a dump of our bug DB, but
perhaps we can do some sort of general writeup instead.
aetopo
Jun 5, 2009, 7:03:22 PM6/5/09
to Google Wave API
I'll gladly help with the write up.
On Jun 5, 6:59 pm, "Brian Kennish (Googler)" <byoo...@google.com>
wrote:
On Jun 5, 6:59 pm, "Brian Kennish (Googler)" <byoo...@google.com>
wrote:
MaggieL
Jun 5, 2009, 7:34:46 PM6/5/09
to Google Wave API
On Jun 5, 6:59 pm, "Brian Kennish (Googler)" <byoo...@google.com>
wrote:
Good idea. There isn't a practical way to do a dump of our bug DB, but
> perhaps we can do some sort of general writeup instead.
There already is a "known issues" wave I think everybody can get to.
> perhaps we can do some sort of general writeup instead.
Even a simple paste of the descriptions and issue numbers might be
helpful.
Reply all
Reply to author
Forward
0 new messages