Last updated 8 May 2015. Created on 19 February 2011.
Edited by rivimey, gisle, mgifford, joachim. Log in to edit this page.

Note: There is currently an active issue in the Webmasters' queue suggesting that these status tags are given proper tag descriptions and that after this has been done, this wiki page shall be replaced with a view exposing the tag descriptions. If you have any thoughts about this, please participate in the issue. projects have fields to classify the current maintenance and development status. This gives project maintainers a well-defined way to communicate their intentions to potential users of the code. It also gives people searching for projects more information about how actively maintained and what kind of development the project is undergoing so they can have reasonable expectations. This page explains the possible values of each of these fields so everyone know what they're supposed to mean.

Maintenance status

Actively maintained
This project has a maintainer that actively monitors its issue queue and responds in a timely manner.
This means that bug reports, tasks, feature requests and support request posted in the project's issue should receive timely attention from project's maintainers. Other community members are also welcome to resolve issues posted to the issue queue.
Minimally maintained
This project has a maintainer that monitors its issue queue, but no fast response is guaranteed.
The maintainer(s) of this project may not have time to respond to all issues. However, serious bug reports will receive attention and patches will be reviewed within reasonable delays. Maintainers will certainly appreciate it if you read Helping maintainers in the issue queues and dive in to help.
Seeking co-maintainer(s)
This project has a maintainer that monitors its issue queue, but need assistance to process it.
The maintainer of this project is seeking help. If you are interested in helping on a regular basis, you should create an issue in the module's queue offering to help out as co-maintainer. It usually a good idea to have posted a few patches before asking to become co-maintainer, since this will show what abilities you have to maintain the code. If your intent as co-maintainer is to focus on a specific branch of the project, mention that as well. You can also help out by posting patches to the project's issue queue, and by reviewing the patches that are not yet given the status "Reviewed & Tested By the Community" (RTBC). You may want to read Contribute to development to learn more about creating, posting and reviewing patches.
Seeking new maintainer
This project is put up for adoption and it is possible for other people to take ownership of it.
The current owner of this project no longer wishes to be responsible for it. If you are interested in taking over the project and work on it to make it healthy again, you should create an issue in the module's queue. See Dealing with unsupported (abandoned) projects to learn the correct procedure to follow.
The project is not supported (i.e. abandoned), and is no longer being developed.
Nobody is currently responsible for this project. If you want to take it over, see Dealing with unsupported (abandoned) projects to learn what to do. Some project's are marked as unsupported due to unresolved security or licensing issues. If this is the case, all those issues must be resolved and the solution must be approved (by the security or licensing team respectively) before the project regains supported status. Please note that if the project's Development status is also marked as "Obsolete", the project may not be worth salvaging.

Development status

Under active development
This project is still under active development.
New features are still being added to this project. Furthermore, its user interface or API may be in a state of flux: Consult the project page and the project's documentation for specific details.
Maintenance fixes only
This project is considered feature complete by its present owner.
The project has reached the target the owner/maintainer aimed for, and as a general rule, no new features will be added (though it's always possible to make a compelling case). Bug reports filed in the project's issue queue are looked at and eventually fixed. If a patch is provided to fix an issue, it may lead to a more timely issue resolution.
No further development
This project is no longer developed at all.
This may indicate the maintainer has no time to work on it, or has lost interest. Please refer to the the project's Maintenance status to learn more about why development has ceased.
Use of this project is depreciated.
Using this project in its present state is not recommended. The project may have been given this status because the project has unfixed security or licensing issues, because the project is no longer relevant to any supported version of Drupal, because it has been made redundant by other projects or core features, or due to other reasons. The project page or documentation may give further details about why the project is marked as obsolete. If you want to take over the namespace (but not the code) of an obsolete project, you post a request for taking over the namespace in the Project ownership issue queue.

Looking for support? Visit the forums, or join #drupal-support in IRC.