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". 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". That would solve the issue with hardcoded version numbers and keep Google happy.
http://codereview.appspot.com/5530043/ _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
