[Pyogclib-developers] RE: PyOGCLib release candidate 1

[<Jea...@CC...>]

Sean,

OK, I've thrown in our first news item!

As for the future, sure, I have no problem doing some of them.

As for the script or list of files to include in a release, a good idea,
just one concern: This assumes that we want to tag the latest version ? What
if it's not the case? Maybe we should track the version of the file we want
tagged also ?

Have a file that lists the files/dirs we want released for that specific
release. For example a file called "release-files-0_2_0.txt" that contains:

README.txt 1.3
LICENCE.txt 1.4
ogclib/__init__.py 1.3

etc ... ?

A separate sed/awk/perl script can process them upon each release.

Thoughts ?
J.F.

-----Original Message-----
From: Sean Gillies [mailto:sgi...@fr...]
Sent: Sunday, October 05, 2003 12:23 PM
To: Jea...@cc...
Cc: pyo...@li...
Subject: Re: PyOGCLib release candidate 1


J.F.,

I made the new release.  Maybe you can do the next one?  And would you
want to write the News item about the release?  Maybe this would be a
good way to share the load: each release one of us makes the release
and one writes a news?

I wrote a sh script called tools/tagrel to help tag files for release.
We might in the future want to keep a text manifest of files for 
release,
but for now they are just named in the script.  The script takes a
single argument like '0-1-0' or '0-2' (maybe in the future we'd drop
the superfluous 0) and tags the files like

    cvs tag rel-$1 ...

To make a release distribution, I did

    cvs export -r rel-0-1-0 PyOGCLib

My mistake was 'checkout' rather than 'export' for RC1.  Then tar and 
gzip.
I'm not bothering with windows ZIP or Apple SIT files since in my
experience the common applications can handle tar.gz.

cheers,
Sean

On Saturday, October 4, 2003, at 06:15  PM, 
Jea...@cc... wrote:

> Sean,
>
> Right on! Thanks for the work Sean :)
>
> A few little problems I noticed:
>
> - In the API docs the link for ogclib.GML.Coordinates is bad ... This 
> is a
> new class, an edit I did earlier today ... probably will need to do a 
> cvs
> add on it ... It replaces ogclib.GML.coordinates (lower "c").
>
> - The file PyOGCLib.txt isn't really necessary anymore as it's 
> replaced by
> the README ... It can be removed from the CVS entirely I think.
>
> - The CVS subdirectory appears in the tarball ?? Did you do an export 
> ? BTW,
> when it's longer an RC, maybe we should tag the tree for 0.1.0, and do 
> a
> proper export without the CVS stuff ?
>
> If you want I can take care of it, I should maybe do my part ? :)
>
> Cheers,
> J.F.
>
> -----Original Message-----
> From: Sean Gillies
> To: pyo...@li...
> Cc: Jea...@cc...
> Sent: 04/10/2003 6:13 PM
> Subject: PyOGCLib release candidate 1
>
> All,
>
> I'm calling this RC 1, will replace it with pyogclib-0.1.0 first thing
> Monday AM unless we find any problems with it.
>
> Web page has also been updated:
>
> http://pyogclib.sourceforge.net
>
> Sean
>