[X-POST] Share your recipes!
wjm at wjm.org
Wed Nov 29 10:44:24 CST 2006
Yeah yeah, first non-ASCII message I send in three years to the list an
everyone's writing me about it :) The graphic smiley appeared because I
simply copied and pasted my post from the forums. I didn't even notice it.
I'll be doubly careful about it in the future.
As for the list, I simply forwarded what I got from the development team in
the category of "need help with recipes" and I'll need to look deeper into
that. There will be several changes occurring in Bugzilla VERY SOON to
enable more intelligent categorization of bugs... hopefully that will
eliminate this problem.
Truth be told, everyone should be going through BugZilla right now -- even
before the changes are implemented -- and commenting on their bugs, adding
info, etc. All the old stuff *will* carry over to the new system, so nothing
will be lost/wasted. I just know that there's several bugs out there that
are a) not reported and b) not fully fleshed out.
Best ways to help:
1) Go through your own bugs, make sure they're categorized properly and have
sufficient recipes, test cases, screen shots, sample stacks, etc. Add
comments and attachments if they are not.
2) Use the voting system. Precious few bugs have been voted on. (There are a
lot of *enhancements* with votes, but those aren't really being considered
for 2.7.5.) Don't worry about "using up" your votes right now... just make
sure at least one vote is applied to each bug that is significant at all.
The more people who vote on a bug, the earlier in-line it will be to be
3) Scan through your old posts to the discussion list(s) and make sure that
the problems you've chatted about and worked around are recorded. Marielle
has graciously agreed to tackle this problem with a gee-whiz semantic
analysis routine, but it's probably not likely that any one person would be
able to catch the unreported bugs with 100% accuracy.
I'm very confident now that Bugzilla is being used extensively and that
effort put into your bugs will be noticed and acted upon. This isn't
guaranteeing a fix for ever single bug... but I can say that each bug is
being reviewed; the tagging is being double-checked, and a massive cleanup
is otherwise underway.
As for the beta... beta 2 is just around the corner. The target date is Dec
7 and you will see an AMAZING difference... more than 100 bug fixes, PLUS
the long-awaited Linux version!
<m.schonewille at economy-x-talk.com> wrote in
message news:5551DB16-0197-4643-9DAA-20775CEADBE7 at economy-x-talk.com...
> Why is
> 3890 - Missing handler in Dictionary - Throws up Script error
> included in your list?
> P.S. Your smiley made your message end up in my spam box.
> Consultancy and Software Engineering
> Get your store on-line within minutes with Salery Web Store software.
> Download at http://www.salery.biz
> Op 28-nov-2006, om 21:38 heeft Bill Marriott het volgende geschreven:
>> I'm reposting this to the list from the forums in the hopes of getting
>> widest possible group of people looking at how to coax these bugs out.
>> Please help if you can!
>> Calling all bug chefs! One of the toughest problems to fix is one you
>> reproduce. There are several of these in the bug system. The developers
>> identified a list of bugs that need "recipes" -- in other words, the
>> required to reproduce the problem.
>> Those bugs include the following:
>> 2868 - Saving with control-S has problems
>> 3067 - Find and Replace too darned slow
>> 3410 - revMail on MacOS X does not work correctly with non ASCII
>> 3816 - openStack seems not to be sent to stacks on Mac OS
>> 1377 - Printing Scripts in color causes overlapping text in the printout
>> 3843 - openStack and openCard messages not being sent on stack launch
>> 3845 - Dictionary Quick Search can't be canceled
>> 3890 - Missing handler in Dictionary - Throws up Script error
>> 3830 - "object does not have this property" in IDE when deselecting a
>> multiple-image selection
>> So here's an open invitation for you to read up on these bugs and try to
>> devise a "test case" which can reliably (or at least more often than
>> cause these errors to be generated.
>> If/when you find a way to reproduce these issues, please log into
>> and post a new comment to the bug and/or attach your sample file.
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode