That looks fine. Thanks, Mike.
On 29/05/10 03:19, Mike Pumphrey wrote:
> Actually, even though it's not 100% correct, I thought it would be less
> confusing and more visible to put it with the top links. But it's easy to
> move around, so please suggest away.
>
> http://docs.geoserver.org
>
>
>
Actually, even though it's not 100% correct, I thought it would be less
confusing and more visible to put it with the top links. But it's easy to move
around, so please suggest away.
http://docs.geoserver.org
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
On 5/27/2010 10:40 PM, Ben Carad
On 27/05/10 22:52, Mike Pumphrey wrote:
>> Thanks, I see it now. Perhaps moving it into the trunk section, with the
>> other trunk docs? I think the reason I missed it was that I expected so
>> see it in the trunk section.
>
> http://docs.geoserver.org/trunk/en/docguide/
> It is in the trunk sectio
> Thanks, I see it now. Perhaps moving it into the trunk section, with the
> other trunk docs? I think the reason I missed it was that I expected so
> see it in the trunk section.
http://docs.geoserver.org/trunk/en/docguide/
It is in the trunk section. :) It's just its own project.
Since I've r
On 26/05/10 22:07, David Winslow wrote:
> To my knowledge the copy that is built nightly and published to
> http://docs.geoserver.org/trunk/en/docguide/ is the only "published"
> version of the documentation guide. It's the very last thing on the
> front page at http://docs.geoserver.org/ ; I imag
On 05/26/2010 03:52 AM, Ben Caradoc-Davies wrote:
> Do we build and publish the documentation guide? Would it be easier if
> it were included in the developer guide?
>
>
To my knowledge the copy that is built nightly and published to
http://docs.geoserver.org/trunk/en/docguide/ is the only "p
Do we build and publish the documentation guide? Would it be easier if
it were included in the developer guide?
--
Ben Caradoc-Davies
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
-
: Ben Caradoc-Davies
Asunto: Re: [Geoserver-devel] Documentation Guide
Para: "Justin Deoliveira"
Cc: "Geoserver-devel"
Fecha: martes, 9 de junio de 2009, 1:27 am
I agree. We should treat the docs just like code. Having them live on
trunk, instead of starting fresh each time, i
I agree. We should treat the docs just like code. Having them live on
trunk, instead of starting fresh each time, is in my view the way to
keep them alive. We can always hide or remove abandoned docs, as we do
abandoned code.
Justin Deoliveira wrote:
> I would say if it is not version specific
Perfect. Docguide is copied to trunk, and I edited the Hudson job to build
that as well.
http://docs.geoserver.org/trunk/docguide/
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
Justin Deoliveira wrote:
> I would say if it is not version specific we can just store it and
> maintain it on
I would say if it is not version specific we can just store it and
maintain it on trunk. It will get copied over to branches but I don't
seen an issue with that, as long as the trunk version of the one that
gets maintained, and the one that gets published.
-Justin
Mike Pumphrey wrote:
> As the
As the transition towards Sphinx docs continues...
I was looking at our documentation guide[1], a meta-document about the
GeoServer docs, and I was thinking that it really isn't all that version
specific. This is fine, as I don't think best practices change according to
the version. (Can you
12 matches
Mail list logo
