pgAdmin is a community project comprising of a number of volunteers from around the world. We do not provide 'paid for' support for pgAdmin, although we do aim to fix bugs and help out wherever possible. Obviously we cannot guarantee to fix every problem or help every user though we always try to.
pgAdmin has a "rolling release" policy; only the latest release is considered to be supported at any time. We do not maintain back-branches or stable versions, and any bug fixes or new features will be added to the next release only.
The version number uses a major.minor format. Typically any new release will have the minor version number incremented, however if a significant change is included in a release, particularly one that will change a large part of the experience for users, we may increment the major version number instead.
We aim to release new versions of pgAdmin every 4 weeks, though the timing may vary around major holidays (e.g. Christmas/New Year, or Diwali). We may also make additional out-of-cycle releases in response to security related fixes.
If you have a problem that you need help with, please make sure you check the pgAdmin documentation for a solution first. If you cannot find the answer you need there, then please try searching on Google. Make sure you include any relevant error messages in your query.
If you are unable to find the answer you need in the documentation or when using Google, then please post a message to the Support Mailing List.
Issues and Bugs
If you believe you have found a bug in pgAdmin 4, please log the relevant information on the issue tracker.
If you would like to report a security issue with pgAdmin, please email security (at) pgadmin (dot) org.
Note that this address should only be used for reporting security issues that you believe you've found in the design or code of pgAdmin, pgAgent, and the pgAdmin website. It should not be used to ask security questions.
Help Us To Help You
General questions and discussion should remain on the mailing list and will be deleted if logged in the bug tracker.
Please do not send an email directly to one of the programmers; they might miss it, or even be the wrong person at all. Using the mailing list helps ensure that your request won't get lost and will be answered in a timely fashion. Dave Page's blog includes a frank posting describing why this is a bad idea, whilst Eric Raymond's paper 'How to ask questions the smart way' describes the best way to get the help you need.