[Bf-extensions-cvs] [686f1f14] master: Use latest/version number for manual links

Aaron Carlisle noreply at git.blender.org
Fri Jul 5 00:31:50 CEST 2019


Commit: 686f1f149ef0c0cd66480ff52b8db8f72772d12d
Author: Aaron Carlisle
Date:   Thu Jul 4 18:24:44 2019 -0400
Branches: master
https://developer.blender.org/rBA686f1f149ef0c0cd66480ff52b8db8f72772d12d

Use latest/version number for manual links

We want users to go to the current version for their current version 
when possible if not point to latest.

/dev should really only be for development related work. End users 
should not be browsing /dev unless they are reading about upcoming 
features ahead of time.

===================================================================

M	io_scene_gltf2/__init__.py
M	space_view3d_stored_views/__init__.py
M	space_view3d_stored_views/stored_views_test.py

===================================================================

diff --git a/io_scene_gltf2/__init__.py b/io_scene_gltf2/__init__.py
index 1003bf69..3c158e4d 100755
--- a/io_scene_gltf2/__init__.py
+++ b/io_scene_gltf2/__init__.py
@@ -20,7 +20,7 @@ bl_info = {
     'location': 'File > Import-Export',
     'description': 'Import-Export as glTF 2.0',
     'warning': '',
-    'wiki_url': "https://docs.blender.org/manual/en/dev/addons/io_gltf2.html",
+    'wiki_url': "https://docs.blender.org/manual/en/latest/addons/io_gltf2.html",
     'tracker_url': "https://github.com/KhronosGroup/glTF-Blender-IO/issues/",
     'support': 'OFFICIAL',
     'category': 'Import-Export',
@@ -595,4 +595,3 @@ def unregister():
     # remove from the export / import menu
     bpy.types.TOPBAR_MT_file_export.remove(menu_func_export)
     bpy.types.TOPBAR_MT_file_import.remove(menu_func_import)
-
diff --git a/space_view3d_stored_views/__init__.py b/space_view3d_stored_views/__init__.py
index 9dce505f..9e475a9c 100644
--- a/space_view3d_stored_views/__init__.py
+++ b/space_view3d_stored_views/__init__.py
@@ -43,7 +43,7 @@ NOTE: logging setup has to be provided by the user in a separate config file
     as Blender will not try to configure logging by default in an add-on
     The Config File should be in the Blender Config folder > /scripts/startup/config_logging.py
     For setting up /location of the config folder see:
-    https://docs.blender.org/manual/en/dev/getting_started/
+    https://docs.blender.org/manual/en/latest/getting_started/
     installing/configuration/directories.html
     For configuring logging itself in the file, general Python documentation should work
     As the logging calls are not configured, they can be kept in the other modules of this add-on
diff --git a/space_view3d_stored_views/stored_views_test.py b/space_view3d_stored_views/stored_views_test.py
index fa4866f0..c31639ad 100644
--- a/space_view3d_stored_views/stored_views_test.py
+++ b/space_view3d_stored_views/stored_views_test.py
@@ -43,7 +43,7 @@ NOTE: logging setup has to be provided by the user in a separate config file
     as Blender will not try to configure logging by default in an add-on
     The Config File should be in the Blender Config folder > /scripts/startup/config_logging.py
     For setting up /location of the config folder see:
-    https://docs.blender.org/manual/en/dev/getting_started/
+    https://docs.blender.org/manual/en/latest/getting_started/
     installing/configuration/directories.html
     For configuring logging itself in the file, general Python documentation should work
     As the logging calls are not configured, they can be kept in the other modules of this add-on



More information about the Bf-extensions-cvs mailing list