[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 2212 in lilypond: WEB: change search to stable and development (se
From: |
lilypond |
Subject: |
Issue 2212 in lilypond: WEB: change search to stable and development (see T2191) |
Date: |
Wed, 11 Jan 2012 01:21:13 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Enhancement
New issue 2212 by address@hidden: WEB: change search to stable and
development (see T2191)
http://code.google.com/p/lilypond/issues/detail?id=2212
From R5530043 and T2191:
Graham Percival
21 hours, 59 minutes ago #5
On Mon, Jan 09, 2012 at 02:10:24PM +0000, address@hidden wrote:
I totally share your sentiment, but we depend on an external entity
here, which we cannot control. Suppose we go from 2.15.x to 2.17.x and
put the documentation under "v2.17". For some time, Google won't have
the new location in its index, so the search would get nothing. It
would be better to keep "v2.15" in the search for a while and have a
redirection from "v2.15" to "v2.17".
Great point! Could you add a comment to this effect to the top of
this file? there's no way that I'll remember otherwise.
Speaking of redirections, I would
prefer that Lilypond had just two versions of its documentation online -
latest "stable" and latest "development". "v2.12" and "v2.14" shoould
redirect to "stable", "v2.15" should redirect to "development".
We want to keep all stable docs available for historical reasons,
but I'm not opposed to directing people to
/doc/stable/
/doc/development/
rather than vX.Y. If you feel like looking into this, the
htaccess is in Documentation/web/server/
- Graham
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Issue 2212 in lilypond: WEB: change search to stable and development (see T2191),
lilypond <=