[postgis-devel] [postgis-tickets] r14796 - Version bumps, release notes for 2.2.2

[Paul Ramsey]

Yes, I was just looking at doing it ("what's the harm") but then
thought: if I'm doind 2.2.2dev, why don't we also have 2.2.1dev... and
then also... ... ...
Yeah.

On Tue, Mar 22, 2016 at 11:42 AM, Regina Obe <lr at pcorp.us> wrote:
> Let's keep it without the dev.  Dev just adds more clutter and people are usually not upgrading for that.
>
> We could put in our dev docs (or FAQ) that to upgrade from dev, copy the 2.2.1-2.2.2  and name 2.2.1--2.2.2dev
>
> -----Original Message-----
> From: Paul Ramsey [mailto:pramsey at cleverelephant.ca]
> Sent: Tuesday, March 22, 2016 2:32 PM
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>; Paul Ramsey <pramsey at cleverelephant.ca>; Paragon Corporation <lr at pcorp.us>
> Subject: Re: [postgis-tickets] r14796 - Version bumps, release notes for 2.2.2
>
> That wasn't the pattern in the prior versions, so I didn't do that. I guess I assume people are upgrading from release to release
>
> On Tue, Mar 22, 2016 at 11:24 AM, Sandro Santilli <strk at keybit.net> wrote:
>> On Tue, Mar 22, 2016 at 10:51:16AM -0700, Paul Ramsey wrote:
>>
>>> Modified: branches/2.2/extensions/upgradeable_versions.mk
>>> ===================================================================
>>> --- branches/2.2/extensions/upgradeable_versions.mk   2016-03-22 16:43:29 UTC (rev 14795)
>>> +++ branches/2.2/extensions/upgradeable_versions.mk   2016-03-22 17:51:16 UTC (rev 14796)
>>> @@ -18,4 +18,5 @@
>>>       2.1.8 \
>>>    2.1.9 \
>>>    2.2.0 \
>>> -  2.2.1
>>> +  2.2.1 \
>>> +  2.2.2
>>
>> Should we the last line read 2.2.2dev rather than 2.2.2 ?
>> That is, to allow 2.2.2dev to be upgraded to 2.2.2
>>
>> --strk;
>
>