Re: 10.0
От | Greg Stark |
---|---|
Тема | Re: 10.0 |
Дата | |
Msg-id | CAM-w4HONMKNRyhwQH_+=zb2WXw3o2=3PmkC_gm9gB3Dk8zfg7Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 10.0 ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: 10.0
|
Список | pgsql-hackers |
<p dir="ltr"><br /> On 15 Jun 2016 2:59 pm, "David G. Johnston" <<a href="mailto:david.g.johnston@gmail.com">david.g.johnston@gmail.com</a>>wrote:<br /> ><br /> > IIRC the plan isto have the machine version behave as if the middle number is present and always zero. It would be (the?) one place thatthe historical behavior remains visible but it is impossible to have a totally clean break.<br /><p dir="ltr">I haven'tbeen keeping up with hackers, sorry if this has been suggested already but...<p dir="ltr">Why don't we just *actually*keep the middle digit and *actually* have it always be zero?<p dir="ltr">So we would release 10.0.0 and 10.0.1and the next major release would be 11.0.0.<p dir="ltr">This would have two benefits:<p dir="ltr">1) It emphasisesthat minor releases continue to be safe minor updates that offer the same stability guarantees. Users would beless likely to be intimidated by 10.0.1 than they would be 10.1. And it gives users a consistent story they can apply toany version whether 9.x or 10.0+<p dir="ltr">2) If we ever do release incompatible feature releases on older branches --or more likely some fork does -- it gives them a natural way to number their release.
В списке pgsql-hackers по дате отправления: