Hi
pgadmin-hackers@lists.postgresql.org<mailto:pgadmin-hackers@lists.postgresql.org>,
I have noticed that the support lifecycle section has recently been
updated at https://www.pgadmin.org/support/.
Lifecycle
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.
I have concerns about the first statement as it requires that my team test and
validate the latest version every 4 weeks (or sooner if out-of-cycle release)
in order to use the tool and get support. Is there any opportunity to adjust
this policy to cover the last major version of pgAdmin?
Thanks
Meyer
