Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version
В списке pgsql-www по дате отправления:
| От | Dave Page |
|---|---|
| Тема | Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version |
| Дата | |
| Msg-id | 461BA604.7070600@postgresql.org обсуждение исходный текст |
| Ответ на | Re: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version (Alvaro Herrera <alvherre@commandprompt.com>) |
| Список | pgsql-www |
Alvaro Herrera wrote: > It makes sense to store things separately when they have a semantic > difference. What we call "major" is the first two digits and dot. We > call "minor" to the third digit, and that's all. We don't have > "revisions". This is how it has ever been and we even document it as > such. Offering the first two digits separately would be a mistake > because it causes confusion over what's significant -- the first digit > by itself is not significant. Yes, and for the most part it's true (certainly as far as the purpose of that documentation is concerned), however it all falls apart next time we have the 'are there enough new features in this release to bump the first digit' discussion which, along with the fact that we have bumped it twice now, is proof in itself that we do give it some meaning. Anyhoo, I've said my piece now - I'll await the inevitable replies telling me I'm a donut and then move on :-) Regards, Dave
В списке pgsql-www по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера