Hi guys,
We need wiki space to create docs for 1.4.x without having to prepend 1.4.x to every page in order to not step on the toes of 1.3.x. GEOSDEV seems to be the place to do this.
I plan to import the relevant docs from GEOSDOC (architecture docs, articles new architecture, etc..), and the previous version of the 1.4.x developers guide which is being updated.
-Justin
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
Hi guys,
We need wiki space to create docs for 1.4.x without having to prepend 1.4.x to every page in order to not step on the toes of 1.3.x. GEOSDEV seems to be the place to do this.
I plan to import the relevant docs from GEOSDOC (architecture docs, articles new architecture, etc..), and the previous version of the 1.4.x developers guide which is being updated.
Thanks Justin, I withdraw my concern on this matter from the merge to trunk page:
- http://docs.codehaus.org/display/GEOSDEV/Merge+to+Trunk
Jody
Cool, looks great. So to summarize with respect to documentation it looks like the workflow is:
1. hack your page for R&D work in GEOSDEV
2. throw it in table of contents on GEOSDEV to make it available
3. once R&D is stable, approved move the page to GEOSDOC.
4. release
Sounds pretty good to me.
-Justin
Jody Garnett wrote:
Justin Deoliveira wrote:
Hi guys,
We need wiki space to create docs for 1.4.x without having to prepend 1.4.x to every page in order to not step on the toes of 1.3.x. GEOSDEV seems to be the place to do this.
I plan to import the relevant docs from GEOSDOC (architecture docs, articles new architecture, etc..), and the previous version of the 1.4.x developers guide which is being updated.
Thanks Justin, I withdraw my concern on this matter from the merge to trunk page:
- http://docs.codehaus.org/display/GEOSDEV/Merge+to+TrunkJody
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
Cool, looks great. So to summarize with respect to documentation it looks like the workflow is:
1. hack your page for R&D work in GEOSDEV
- aka this documents work on a branch
2. throw it in table of contents on GEOSDEV to make it available
- aka this documents work on trunk
3. once R&D is stable, approved move the page to GEOSDOC.
- aka this work documents work on a stable release
4. release
Sounds pretty good to me.
Sweet,
Jody
Okay apparently I was wrong - I had in mind:
- GeoServer 1.3.x , GeoTools 2.2.x, GEOSDOC are all released as "stable"
- GeoServer trunk, GeoTools 2.2.x, GEOSDEV "table of contents" are released as "milestones"
- GeoServer branch/* gather docs in GEOSDEV and are released as people need
In trying to plan out the wiki spaces reading http://docs.codehaus.org/display/GEOSDOC/Release+Guide and talking to Justin I have run into the following:
- GeoServer 1.3.x - not sure how it is used?
- GeoServer trunk, GeoTools 2.1.x (and GeoTools 2.2.x), GEOSDOC - being used to make GeoServer 1.3 releases?
- GeoServer 1.4.x, GeoTools 2.2.x, GEOSDEV - being used to make milestone releases
- GeoServer branch/* have docs in GEOSDOC and are released ad hoc
I would love to have is trunk set up for milestone releases targeting the next stable release with a wiki space documenting it,
a branch marked as stable that is in bug fix mode (matched to a stable geotools release and GEOSDOC),
and some venue for RnD branches such as WCS to come home.
Should I formally set up another space so we can have a documentation set for stable and a documentation set for milestone releases? And keep GEOSDEV for RnD documentation? Oh wait perhaps GEOS is already being used in this capacity? http://docs.codehaus.org/display/GEOS/RnD
Cheers,
Jody
Justin Deoliveira wrote:
Cool, looks great. So to summarize with respect to documentation it looks like the workflow is:
1. hack your page for R&D work in GEOSDEV
- aka this documents work on a branch
2. throw it in table of contents on GEOSDEV to make it available
- aka this documents work on trunk
3. once R&D is stable, approved move the page to GEOSDOC.
- aka this work documents work on a stable release
4. release
Sounds pretty good to me.
Sweet,
Jody-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel