[postgis-devel] What feeds this Change Log and Release date iswrong

[Paul Ramsey]

That might be a very good convention, since what I put in SVN notes is
not necessarily "release notes" worthy, but if every item suitable for
release notes was tagged at commit, building a comprehensive set would
be much easier.
p.

On Fri, Nov 28, 2008 at 8:55 AM, Obe, Regina <robe.dnd at cityofboston.gov> wrote:
> I suppose we can't just make it a convention that when we do something
> History worthy we flag it in the SVN notes.
>
> Something like when we put in notes we prefix with
>
> #HISTORY:  Did something big
>
> That way we can just parse the logs grab anything in our release period
> with #HISTORY and stuff it in there.
>
> So we don't have to do this as a separate task.
>
>
>
> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net
> [mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Paul
> Ramsey
> Sent: Friday, November 28, 2008 11:48 AM
> To: PostGIS Development Discussion
> Subject: Re: [postgis-devel] What feeds this Change Log and Release date
> iswrong
>
> SVN.txt is created nighty by svn2cl.
> I actually replaced the ChangeLog in the latest 1.3 release with a
> generated version.
> I'm with Mark, we should remove it entirely. We can still include a
> make target for it and release it, and have the online version... but
> it shouldn't be in SVN anymore, it's not an artefact, it's a
> resultant.
>
> If we want to start being "formal", then going whole hog like
> Mapserver HISTORY.txt strikes me as best.
>
> http://svn.osgeo.org/mapserver/trunk/mapserver/HISTORY.TXT
>
> Changes annoted in human readable form, only "big" things, and
> cross-references to trac numbers.
>
> P.
>
> On Fri, Nov 28, 2008 at 1:56 AM, Mark Cave-Ayland
> <mark.cave-ayland at siriusit.co.uk> wrote:
>> Obe, Regina wrote:
>>
>>> http://svn.refractions.net/postgis/trunk/ChangeLog which on home page
> is
>>> tied to text  "Release Change Log" which is terribly confusing.
>>>
>>> I thought it would have changed when Paul put in the change release
>>> notes.
>>>
>>> The  SVN Change Log (linked to here
>>> http://postgis.refractions.net/SVN.txt) is ironically more accurate
> of
>>> release state.
>>>
>>> Also the date on the home page says November 11th 2008.  Didn't we
> just
>>> release yesterday or is someone in a time warp?
>>>
>>> Don't forget to add to list
>>> ST_Transform support for Circular Strings/Curves
>>>
>>> (I don't think it ever got a GBT number because Mark fixed it before
> I
>>> had a chance to complain about it :))
>>>
>>> Thanks,
>>> Regina
>>
>> Yeah, I'm totally for leaving the ChangeLog during normal development,
> and
>> then copying the final release notes into both the ChangeLog and the
>> documentation just before release.
>>
>>
>> ATB,
>>
>> Mark.
>>
>> --
>> Mark Cave-Ayland
>> Sirius Corporation - The Open Source Experts
>> http://www.siriusit.co.uk
>> T: +44 870 608 0063
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
> -----------------------------------------
> The substance of this message, including any attachments, may be
> confidential, legally privileged and/or exempt from disclosure
> pursuant to Massachusetts law. It is intended
> solely for the addressee. If you received this in error, please
> contact the sender and delete the material from any computer.
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>