[Geoserver-devel] updating README for minor releases

GeoServer GeoServer Developer
1

Hi all,

I just took a look at the README.txt on 1.6.x and noticed the latest entry is for 1.6.0, which means nothing was added for 1.6.1 and 1.6.2. Unless the policy has changed we are supposed to be updating for every release.

-Justin

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

2

We did it in the tags before releasing, the 1.6.2a release also includes notes for 1.6.1:
http://svn.codehaus.org/geoserver/tags/1.6.2/geoserver/release/README.txt

I don't have checkouts handy on this box, could you copy that one into 1.6.x and trunk for me?

I'll make a step for it in the documentation.

-Arne

Justin Deoliveira wrote:

Hi all,

I just took a look at the README.txt on 1.6.x and noticed the latest entry is for 1.6.0, which means nothing was added for 1.6.1 and 1.6.2. Unless the policy has changed we are supposed to be updating for every release.

-Justin

3

Ahh... ok that makes sense. I always tagged after committing the readme and all of that. It is kind of nice to keep the README's on the main branches up to date though.

I can copy it over, no problemo.

-Justin

Arne Kepp wrote:

We did it in the tags before releasing, the 1.6.2a release also includes notes for 1.6.1:
http://svn.codehaus.org/geoserver/tags/1.6.2/geoserver/release/README.txt

I don't have checkouts handy on this box, could you copy that one into 1.6.x and trunk for me?

I'll make a step for it in the documentation.

-Arne

Justin Deoliveira wrote:

Hi all,

I just took a look at the README.txt on 1.6.x and noticed the latest entry is for 1.6.0, which means nothing was added for 1.6.1 and 1.6.2. Unless the policy has changed we are supposed to be updating for every release.

-Justin

!DSPAM:4007,47ec705546594901796417!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com