On Tue, Apr 12, 2016 at 4:07 PM, Oleg Bartunov <obartu...@gmail.com> wrote: > Our roadmap http://www.postgresql.org/developer/roadmap/ is the problem. We > don't have clear roadmap and that's why we cannot plan future feature full > release. There are several postgres-centric companies, which have most of > developers, who do all major contributions. All these companies has their > roadmaps, but not the community. I think 9.6 release is inflection point, > where we should combine our roadmaps and release the one for the community. > Than we could plan releases and our customers will see what to expect. I > can't say for other companies, but we have big demand for many features from > russian customers and we have to compete with other databases. Having > community roadmap will helps us to work with customers and plan our > resources.
I don't think it's realistic to plan what is going to go into a certain release. We don't know whether we want the patch until we see the patch and review it and decide whether it's good. We can't make the decision, first, that the patch will be in the release, and then, second, write the patch. What we *can* do, as Josh says, is discuss our plans. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers