public inbox for [email protected]
help / color / mirror / Atom feedFrom: Robert Treat <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: Getting ready for beta
Date: Sun, 07 Oct 2007 20:58:25 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On Saturday 06 October 2007 13:13, Joshua D. Drake wrote:
> Magnus Hagander wrote:
> >>>>> Any objections to the plan of loading the beta docs on the main site?
> >>>>> (No, I don't intend to flag them as "current", they'll just go under
> >>>>> /docs/8.3/)
> >>>>
> >>>> Sounds good to me. Would the release notes be /docs/beta/release.html
> >>>> ?
> >>>
> >>> Unless someone changes the way the docs are built before then, it'll be
> >>> /docs/8.3/static/release-8-3.html
> >>
> >> s/static/interactive/ :-)
> >
> > That would work too. But since we have them both I figured we'd want to
> > use the static ones during beta.
> >
> > or maybe this is the time when we should retire one sdu of docs once and
> > for all? now that we have properly moderated comments I think it wound be
> > a good idea to consider..
>
> Only if there is a way (I haven't checked) to turn off viewing of the
> comments *regardless* if I am logged in.
>
> I personally don't read, care to read, or want anything to do with
> interactive documentation :). Give me what I need, only what I need and
> if I need something you don't provide, I will ask.
>
Luckily the source distribution comes with a complete copy of the
documentation included, so you can just build it and install it locally and
never have to worry about using the interactive version.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
view thread (17+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Getting ready for beta
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox