Hi all,
I am starting to hack up docs for my ows4 work. I would like to move the
programmers guide from GEOS to GEOSDEV, as it doesn't really apply to
trunk. The rest of the developers guide is fine though.
What do people think. If people prefer I can also hack the docs in the
GEOS space as is.
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
Hi all,
I am starting to hack up docs for my ows4 work. I would like to move the
programmers guide from GEOS to GEOSDEV, as it doesn't really apply to
trunk. The rest of the developers guide is fine though.
The programmers guide in GEOS should reflect (and be completed fo?) trunk? I figured you would hack up some new pages to add to the programmers guide in GEOSDEV and then migrate when 1.6 goes out?
What do people think. If people prefer I can also hack the docs in the GEOS space as is.
GEOS reflects the current stable branch, and no more. It is used as a staging area to
produce documentation for each & every stable release right?
Jody
Well everything minus the programmers guide does reflect trunk at the
moment.
Things are still a bit messy with the transition from the old service
model to the new one, so the tutorial on building a new service still
isn't accurate. I don't see much gain in us documenting the system as is
as it is planned to change once the ows4 work comes to trunk.
-Justin
Jody Garnett wrote:
Justin Deoliveira wrote:
Hi all,
I am starting to hack up docs for my ows4 work. I would like to move the
programmers guide from GEOS to GEOSDEV, as it doesn't really apply to
trunk. The rest of the developers guide is fine though.
The programmers guide in GEOS should reflect (and be completed fo?)
trunk? I figured you would hack up some new pages to add to the
programmers guide in GEOSDEV and then migrate when 1.6 goes out?What do people think. If people prefer I can also hack the docs in the
GEOS space as is.
GEOS reflects the current stable branch, and no more. It is used as a
staging area to
produce documentation for each & every stable release right?Jody
!DSPAM:1004,4537b4d876201425493344!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Sorry, after reviewing the docs with Chris most of the programmers guide
is still consistent with trunk / ows4, except for the modules page. I
apologize for the confusion.
So let me change my request to just moving the module page to the
GEOSDEV space.
Justin Deoliveira wrote:
Well everything minus the programmers guide does reflect trunk at the
moment.Things are still a bit messy with the transition from the old service
model to the new one, so the tutorial on building a new service still
isn't accurate. I don't see much gain in us documenting the system as is
as it is planned to change once the ows4 work comes to trunk.-Justin
Jody Garnett wrote:
Justin Deoliveira wrote:
Hi all,
I am starting to hack up docs for my ows4 work. I would like to move the
programmers guide from GEOS to GEOSDEV, as it doesn't really apply to
trunk. The rest of the developers guide is fine though.
The programmers guide in GEOS should reflect (and be completed fo?)
trunk? I figured you would hack up some new pages to add to the
programmers guide in GEOSDEV and then migrate when 1.6 goes out?What do people think. If people prefer I can also hack the docs in the
GEOS space as is.
GEOS reflects the current stable branch, and no more. It is used as a
staging area to
produce documentation for each & every stable release right?Jody
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
Sorry, after reviewing the docs with Chris most of the programmers guide
is still consistent with trunk / ows4, except for the modules page. I
apologize for the confusion.So let me change my request to just moving the module page to the
GEOSDEV space.
Cool, we should confirmed we caught this kind of thing as part of the project procedures in the developers guide. I think you can find it under documentation guidelines.
Jody