Welcome to the QGIS Development pages
If you find a bug, please report it!
You need an OSGeo account and login in order to submit bug reports. To get started, first create Create an OSGeo4 account.
Once you have your account, use QGIS issue tracking to search if the issue you’d like to report is probably already entered.
On the OSGEO userid page you can find more information about the OSGEO id we use. For example to change your password or email address. Lost your password? Then request a password reset via info at osgeo.org
Issues are used to report bugs, request enhancements and submit patches. Redmine is more than a bug reporting system. Issues can be associated with a QGIS Milestone, allowing you to see progress towards completion. Completion of a Milestone not only requires closing bugs, but completing other tasks related to a release such as documentation, web site updates, packaging, and announcements.
Before filing a bug, review the currently open issues to make sure that you aren’t creating a duplicate. If you have additional information on an issue, you can add it to the existing ticket. Third party plugins might also cause problems. If you have installed any, you should also verify that the problem is still reproducible without them. Please don’t report multiple unrelated bugs in a single bug report.
Plugin bugs must be opened in their respective bug tracking system. Check first if the plugin is listed in the plugin overview. If so, click on the plugin name then click “New issue”. Otherwise, consult the plugin documentation to find the address of the relevant bug tracking system or a developer to contact.
To report a bug choose New Issue from the menu bar. Note: You can also request an enhancement or submit a patch using the Ticket system.
Important information needed when opening a ticket:
Before sending the bug, please check the formatting of your report by clicking on “Preview”. Please avoid editing existing reports, if not for typos. Better add further comments in any other case.
If you have a crash it might be useful to include a backtrace as the bug might be not reproducible on an other machine.
On Linux QGIS automatically tries to use gdb to connect to the crashing process to produce a backtrace. But some distributions disable the possiblity to connect debuggers to a running processes. In that case gdb only produces a rather useless message like:
QGIS died on signal 11Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. No thread selected No stack. gdb returned 0 Aborted (core dumped)
In that case you should reenable that option by setting kernel.yama.ptrace_scope to 0 in /etc/sysctl.d/10-ptrace.conf (or /etc/sysctl.conf or some other file in /etc/sysctl.d/) and run sysctl -p as root. When you reproduce the crash after that, a backtrace will be printed instead.
If you cannot reproduce the crash, there should still be a core dump in the current directory, that can be analysed after the process has already terminated. It’s called core (on some systems a dot and the process id is append to the filename).
On some distributions the creation of core dumps is also disabled. In the event that you just get Aborted instead of Aborted (core dumped) when the crash occurs. Then you need to run ulimit -c unlimited before starting QGIS. You can also include that in your .profile, so that it’s always enabled when you login.
To produce a backtrace from the core file it you start gdb /path/to/the/qgis/binary core. The binary is usually /usr/bin/qgis or /usr/bin/qgis.bin on Debian with the GRASS plugin installed. In gdb you run bt which will produce the backtrace.
The nightly build in OSGeo4W (package qgis-dev) is built with debugging output, that you can view with DebugView. If the problem is not easy to reproduce the output might shed some light about where QGIS crashes.
To be done
Since QGIS 2.0 further development will occur based on a timebased roadmap.
Odd version numbers (2.1, 2.3 etc) are development versions.
Even version numbers (2.2, 2.4 etc) are release versions.
Release will happen every four month. In the first three month new development is taking place. Then a feature freeze is invoked and the final month is used for testing, bugfixing, translation and release preparations. When the release happens, a branch with a even release number is created and the master branch advances to the next odd version. After the release a call for packaging is issued.
Every third release (starting with 2.8) is a long-term-release (LTR) that is maintained until the next long-term-release occurs.
In the development phase developers work on adding new features for the next release. Early adopters can use the nightly builds we have for all major platforms to see the development progress, do preliminary testing and provide bug reports and their thoughts to help with development.
In the feature freeze phase new features are not allowed in anymore and the focus of everyone moves from enhancing QGIS to stablizing it. This also turns the nightly builds effectively into prereleases.
Users should start extensive testing of these prereleases in their environment to verify that there are no issues, they wouldn’t want to see in the upcoming release. All such issues should be reported (see Bugs, Features and Issues). Everything that goes unnoticed, will also end up in the next release. Only in case of serious problems backports to a latest release will occur. Therefore testing of the prereleases and reporting issues is very important.
In the feature freeze developers monitor the hub and start working on fixing the reported issues.
With the begin of the feature freeze the translation files will be updated so that translators can start their work. Note that this might be an incremental process as although the features are frozen, bug fixes might still introduce translation string changes.
The schedule is aligned to produce roughly the same dates for each year given our four monthly releases with LTRs in late february.
Beginning after 2.12 the development phase is always 12 weeks and the freeze phase is at least 5 weeks. Remainders are used to extend the freeze phase of LTR releases.
Point releases will happen every months on the latest release branch and the LTR branch, if there are backports.
Future version numbers are subject to change in case of a major releases.
|LTR||Long term release, begin of new development phase|
|LR||Regular release, begin of new development phase|
|DEV||Feature freeze, end of development phase|
|PR||Point release of latest release and LTR branch|
We have Developer Guidelines on this page:
QGIS has a plugin infrastructure. You can add a lot of new functionality by writing your own plugins.
These plugins can either be written in C++ or in Python
To learn how to write your first C++ plugin, please go here: Developing C++ plugins
Via a script you will generate a plugin stub which can be used further.
QGIS has a lot to offer for python developers too.
QGIS has python bindings so you can automate tasks in QGIS via python.
Looking for examples of python plugins, see http://plugins.qgis.org
You can find the QGIS-iface which you can use via python here:
http://qgis.org/api/classQgisInterface.html (for QGIS testing)
http://qgis.org/api/2.0/classQgisInterface.html (for QGIS 2.0)
http://qgis.org/api/1.8/classQgisInterface.html (for QGIS 1.8)
Contributors of new functions are encouraged to let people know about their contribution by:
adding a note to the changelog for the first version where the code has been incorporated, of the type:
This feature was funded by: Olmiomland http://olmiomland.ol This feature was developed by: Chuck Norris http://chucknorris.kr
writing an article about the new feature on a blog, and add it to the QGIS planet http://plugins.qgis.org/planet/
adding their name to: