Hi,
I read every email in this thread. Thanks everyone who contributed.
However, my point still did not change. The upcoming features in 9.6 is no less
than 9.0 or 8.0 -- even more. Apart from the feature list, the infrastructural
changes in 9.6 is a bit too much, so we should warn the users about that, with
a .0 release. I, as a person from the field, will raise warnings to my
customers about that, for example.
An argument about "we can have 10.0 release if we have this feature" is also
*very* conservative: No one is stopping us for 11.0 release, when we have those
cool features with those major breakages.
Eventually, before releasing 9.6beta1, to make the packagers lives easier, I
want to push for a change again. Let's stop being conservative, and mark this
release as 10.0.
Regards, Devrim
On Tue, 2016-03-22 at 16:07 +0200, Devrim GÜNDÜZ wrote:
> Hi,
>
> I've been ranting about this on Twitter for a while, and now blogged about
> it:
>
> http://people.planetpostgresql.org/devrim/index.php?/archives/89-9.6,-or-10.0
> .html
>
> There are major changes in 9.6 (some of them are listed in the blog post),
> and
> I think they are good enough to call this 10.0.
>
> A counter argument might be waiting for pglogical for inclusion, but I think
> the current changes are enough to warrant a .0 release.
>
> What do you think?
>
> Regards,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR