A few notes on the next PostgreSQL development cycle (the one after 9.6): - After several rounds of consultations, it has been decided to change the version numbering scheme. Instead of X.Y.Z, future releases will have a two-part version number M.N, where M is the major version number, which changes with a major release, every year or so, and N is the minor version number, which changes with a minor release, every few months or so. This does not change in any way development practices or approaches to backward compatibility. It merely makes the version numbering scheme match existing development practices better.
- The next major release of PostgreSQL (after 9.6) will be known as PostgreSQL 10. (The actual version number of the first production release will as before have a minor version number of .0, so the actual release number will be 10.0.) Again, this jump does not change any policies or conventions on backward compatibility. - Per [1], the first commit fest of the version 10 development cycle starts on September 1. In spite of 124 patches already showing at <https://commitfest.postgresql.org/10/>, it seems like we have had a good couple of months focusing on release work. If you have been hesitating because of that, now is surely the time to start submitting any patches you want for consideration in September. - We need a commit fest manager. Volunteers, step forward! - The branching of the Git tree is tentatively scheduled for August 15. (There will be minor releases and a beta release on August 11.) [1]: https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting#9:55_-_10:05_.09Next_Release_Schedule_.09All -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
