= Angband development tracker =

Welcome to the Angband development wiki. If you do not consider yourself a developer but rather a player, you might prefer to read the main angband wiki at http://rephial.org/wiki/. Of course, in the world of open source, anyone can be a developer - even if you only want to edit a single text file in lib/edit/.

If you have come to open a ticket, please check one or more of the following: 

 * [/query?status=new&status=reopened&group=resolution&max=1000&order=milestone&col=id&col=summary&col=milestone&col=reporter&col=keywords&type=bug New and unconfirmed bugs]
 * [/query?status=pending&max=1000&col=id&col=summary&col=status&col=type&col=milestone&col=time&order=priority Bugs which have actually been fixed in the staging branch but are not yet in nightlies]
 * [/query?status=new&status=assigned&status=reopened&status=confirmed&group=resolution&milestone=3.2.0&order=id Ticket list for the next release]
 * KeywordGuide — Please read this before creating a ticket, and assign the relevant keywords
 * [/query?status=assigned&status=confirmed&status=new&status=reopened&max=1000&col=id&col=summary&col=type&col=keywords&col=changetime&order=keywords List of all open tickets by keywords] 

In particular, please check this last one before opening a new ticket, in case a ticket already exists for the same issue. Duplicate tickets are painful and should be avoided wherever possible: if you're not sure if your ticket would duplicate an existing one, leave a comment about your issue on the existing ticket in preference to creating a new ticket. 

Whatever you aspire to do, please read the [CodingGuidelines coding guidelines] if you intend to read or modify the source code.  To get a copy of the latest released development code, use {{{git clone git://github.com/angband/angband.git}}}.

The development wiki is still in, er, development. For now, we have the current useful things: 

 * [http://angband.oook.cz/mailman/listinfo/angband-dev The angband development mailing list archive]
 * ReleaseChecklist - things to be checked before a release
 * CodeMasters - a guide to which developers are most familiar with which parts of the code, and who is currently working on what
 * GitUsage - a guide to pushing etiquette and tips for those cowed by the awesome complexity of git (i.e. everybody)
 * ToDiscuss - stuff that the devteam should make a decision on
 * ToDocument - stuff that the devteam needs to document fully ...
 * [[Policy]] - a growing archive of helpful guidance