You could; we would need to think about where to place it; currently the
"Welcome" section seems the most appropriate; since we have a Welcome page for
specific groups of users; we could have a "Welcome GeoTools Developers" page
helping people upgrade? A child page for each set of "update to instructions"
etc...
Currently we maintain the following on the wiki for each release branch:
- A page describing the stated goals for the release (this amounts to our
roadmap)
- A page for each accepted proposal (I think we are stuck with the wiki for
this; as we want to be able to accept proposals from those with out commit
access?)
- An "update to" page describing API changes made ( move to
welcome/geotools/udpate8 etc...)
- A page for each release (move to blog - as right now we are duplicating
effort)
Do I have that right?
--
Jody Garnett
On Wednesday, 18 May 2011 at 5:26 PM, Ben Caradoc-Davies wrote:
> +1. That is where it belongs.
>
> On 18/05/11 15:10, Andrea Aime wrote:
> > Afaik Simone cannot access the wiki anymore. Should we migrate that page to
> > sphinx too?
>
> --
> Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au>
> Software Engineering Team Leader
> CSIRO Earth Science and Resource Engineering
> Australian Resources Research Centre
>
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
