3 ms·
I'm not sure what you base the less conservative approach to development comment on. As far as I know, the development process and patch application process is
by crad 16y ago
I'm not sure what you base the less conservative approach to development comment on. As far as I know, the development process and patch application process is the same as it has been in recent years. Stability and quality of code are still #1.
Edit: clarified the conservative approach to development.
- mahmud 16y agoPerhaps the submission itself? From the first paragraph: "While past major releases have been quite conservative in their scope, this release shows a bold new desire to provide facilities that every new and existing user of PostgreSQL will embrace."
- crad 16y agoThe intent was not to speak to the development process per se, but the roadmap for Postgres.
- astine 16y agoI think you misunderstand me I don't mean to imply that the Postgres developers have decided to be sloppier in their development practices or anything like that. When I say 'less conservative in development' I mean that scope is an aspect of development. When a project's scope increases, so does it's workload and complexity; a development team can either allocate more resources and time to the project or let quality slide. This is a truism and I mean no slight to the Postgres people who, in my experience have consistently delivered a very stable project to date and may very well be able to handle a broader scope with no loss in quality.