You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 5701 Reporter:@ygrek Assigned to:@damiendoligez Status: closed (set by @damiendoligez on 2012-07-31T15:31:36Z) Resolution: fixed Priority: normal Severity: feature Version: 4.00.0 Category: web site Monitored by:@hcarty
Bug description
Consider the situation when one wants to link to the official manual for the current release. It is available at the following url : http://caml.inria.fr/pub/docs/manual-ocaml/ but the problem is that after the next release this link will serve the manual for the new version and the old link becomes broken (section numbers are not stable). The old manual meanwhile becomes available at e.g. manual-ocaml-312. Hence the feature wish is to create such manual-ocaml-xxx directories (for the latest xxx version) at the time of release so that one can get future-proof links for now-current documentation. (I.e. it means copy current manual-ocaml to manual-ocaml-4.00).
The web site now uses the stable link throughout. Note that the naming convention has changed:
manual-ocaml-312 (without the period) to manual-ocaml-4.00 (with the period). The old links
will remain valid.
Original bug ID: 5701
Reporter: @ygrek
Assigned to: @damiendoligez
Status: closed (set by @damiendoligez on 2012-07-31T15:31:36Z)
Resolution: fixed
Priority: normal
Severity: feature
Version: 4.00.0
Category: web site
Monitored by: @hcarty
Bug description
Consider the situation when one wants to link to the official manual for the current release. It is available at the following url : http://caml.inria.fr/pub/docs/manual-ocaml/ but the problem is that after the next release this link will serve the manual for the new version and the old link becomes broken (section numbers are not stable). The old manual meanwhile becomes available at e.g. manual-ocaml-312. Hence the feature wish is to create such manual-ocaml-xxx directories (for the latest xxx version) at the time of release so that one can get future-proof links for now-current documentation. (I.e. it means copy current manual-ocaml to manual-ocaml-4.00).
Steps to reproduce
Here is an example that happened to me just today :
http://stackoverflow.com/questions/11667357/can-you-compile-an-ocaml-project-natively-as-a-windows-library
The text was updated successfully, but these errors were encountered: