Changes between Version 12 and Version 13 of WikiStart


Ignore:
Timestamp:
01/28/10 00:04:28 (10 years ago)
Author:
Valik (IP: 71.31.22.172)
Comment:

Cleanups, Table of Contents and Commenting Guidelines.

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v12 v13  
    11= Welcome to the !AutoIt issue tracker =
     2[[PageOutline]]
    23
    34The !AutoIt issue tracker is the new system for placing bug reports and feature requests for !AutoIt.  Please take a few moment to read over this page to get an understanding of what you need to do in order to help the developers improve the !AutoIt language.  Below are guidelines, tips and expectations for using this service.
    45
    56== General Guidelines ==
    6     * Search the issue tracker to see if the ticket has already been discussed.
    7     * Search the [http://www.autoitscript.com/forum/index.php forum] to see if the issue has been discussed there.
    8     * Do not create a new ticket because an old ticket was closed. Reply to the old ticket if you have additional information and the developers will make the determination if the ticket should be re-opened.
     7These guidelines should be taken into consideration when posting to the issue tracker.
     8 * Search the issue tracker to see if the ticket has already been discussed.
     9 * Search the [http://www.autoitscript.com/forum/ forum] to see if the issue has been discussed there.
     10 * Do not create a new ticket because an old ticket was closed. Reply to the old ticket if you have additional information and the developers will make the determination if the ticket should be re-opened.
    911 * Please use the following syntax when inserting code.  It helps the code stand out making it easier to read.
    1012{{{
     
    1618 * Do not demand priority for your issue.  People always suggest their issue should receive priority because it's important to them.  It's a waste of time to suggest priority and will just lead to your ticket being ignored for longer than it would have otherwise been.  It is up to the developers to choose what they want to work on and when it gets worked on.
    1719 * Do not argue about the resolution a ticket is given unless you can prove that closing the ticket was a mistake.
    18  * '''Do not ask for support.'''  This is for bug reports and feature requests only.  See the AutoIt [http://www.autoitscript.com/forum/index.php forum] to ask for support.
     20 * '''Do not ask for support.'''  This is for bug reports and feature requests only.  See the AutoIt [http://www.autoitscript.com/forum/ forum] to ask for support.
    1921 * Tickets should be stand-alone.  They should contain all the information necessary to reproduce the issue without the need for links to the forum.  It is acceptable to link to the forum so the developers may see the discussion that lead to the discovery of the bug.  However, linking to the forum without extricating the pertinent information and using that to create the ticket will result in the ticket being ignored and closed.
    2022 * Each ticket should cover one issue.  Tickets that cover multiple issues are confusing and hard to resolve since some parts may not be completed in a way that matches the ticket's resolution.  If you think you've found multiple related issues, post on the forum first.  Chances are, fixing one issue will resolve the related issues, otherwise they should be separate tickets anyway.
    2123[[BR]]
    2224== Bug Report Guidelines ==
    23     * If you are asking a question you do not have a bug to report, use the  forum to ask questions.
    24     * You must provide a short test script that reproduces the problem. The script should be no more than the bare minimum code necessary to reproduce the problem.
    25     * Test the reproduction script with both the latest stable and latest beta versions of AutoIt. Check the links to ensure you have the latest versions, AutoIt is updated frequently.
    26     * Please choose the correct version and component for the ticket.
     25These guidelines should be taken into consideration when creating a bug report.
     26 * If you are asking a question you do not have a bug to report, use the  forum to ask questions.
     27 * You must provide a short test script that reproduces the problem. The script should be no more than the bare minimum code necessary to reproduce the problem.
     28 * Test the reproduction script with both the latest stable and latest beta versions of AutoIt. Check the links to ensure you have the latest versions, AutoIt is updated frequently.
     29 * Please choose the correct version and component for the ticket.
    2730[[BR]]
    2831== Feature Request Guidelines ==
     32These guidelines should be taken into consideration when creating a feature request.
    2933 * Ensure the idea isn't on the list of things we won't do.
    3034 * Seriously, go and read this [wiki:AutoItNotOnToDoList page] again.  Do not ask for these things.
     
    3337 * Don't ask the developers to write UDFs.  If you want to see UDFs added then you'll need to write it or get someone else to write it and submit it with the proper documentation.
    3438 * Don't assume that just because you need a feature that the majority of people will use the feature.  In other words don't ask for very niche things.  This is doubly true if you can do what you need via a UDF.  Things added to the language are intentionally very broad to reduce bloat.
     39[[BR]]
     40== Commenting Guidelines ==
     41These guidelines should be taken into consideration when replying to a ticket.
     42 * You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
     43 * In-depth discussions should take place on the [http://www.autoitscript.com/forum/ forum].
    3544[[BR]]
    3645== Description of Ticket Fields ==