Re: How can we get the word out about the change in version numbering?
От | Peter Eisentraut |
---|---|
Тема | Re: How can we get the word out about the change in version numbering? |
Дата | |
Msg-id | 31e08181-82f7-4fa8-34d2-3bfe97661609@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: How can we get the word out about the change in version numbering? (Darren Duncan <darren@darrenduncan.net>) |
Ответы |
Re: How can we get the word out about the change in
version numbering?
|
Список | pgsql-advocacy |
On 8/19/16 1:44 AM, Darren Duncan wrote: >> Realistically, most stuff doesn't even support 9.6 yet, and we wouldn't >> want to distract from that. So my take is to do nothing for about the >> next 6 months. > > So, per my initial response, a good and easy strategy would be a one-two punch > of mentioning both 9.6 and 10.0 in the same announcements. The announcements > would headline with and be focused on 9.6, but each would include a footnote > about 10.0 also. That way people are reminded of the 10.0 need without being > hit over the head by having dedicated announcements about it. -- Darren Duncan My argument is that we should exactly not do that. The point of announcements about release 9.6 is to get people to test or use release 9.6. Mentioning a distant future release does not further that aim. Furthermore, a note about version 10 is not really actionable right now. No author of a driver or extension or application is realistically going to download 10devel now and port their code and then tuck it away for another 8 months. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-advocacy по дате отправления: