docs: removed some old update notices

Author: fstagni

docs/source/AdministratorGuide/Resources/storage.rst

@@ -354,9 +354,7 @@ Multi Protocol with FTS
 External services like FTS requires pair of URLs to perform third party copy.
 This is implemented using the same logic as described above. There is however an extra step: once the common protocols between 2 SEs have been filtered, an extra loop filter is done to make sure that the selected protocol can be used as read from the source and as write to the destination. Finally, the URLs which are returned are not necessarily the url of the common protocol, but are the native urls of the plugin that can accept/generate the common protocol. For example, if the common protocol is gsiftp but one of the SE has only an SRM plugin, then you will get an srm URL (which is compatible with gsiftp).
 
-
-.. versionadded:: v7r1p37
-    The FTS3Agent can now use plugins to influence the list of TPC protocols used. See :ref:`fts3`
+The FTS3Agent can use plugins to influence the list of TPC protocols used. See :ref:`fts3`
 
 
 MultiHop support

docs/source/AdministratorGuide/Systems/DataManagement/fts3.rst

@@ -4,8 +4,6 @@
 FTS3 support in DIRAC
 ---------------------
 
-.. versionadded:: v6r20
-
 .. contents:: Table of contents
    :depth: 2
 
@@ -148,10 +146,6 @@ The FTS3Operation goes to ``Processed`` when all the files are in a final state,
 FTS3 Plugins
 ------------
 
-.. versionadded:: v7r1p37
-    The ``FTS3Plugin`` option
-
-
 The ``FTS3Plugin`` option allows one to specify a plugin to alter some default choices made by the FTS3 system. These choices concern:
 
    * the list of third party protocols used
@@ -165,8 +159,6 @@ This can be useful if you want to implement a matrix-like selection of protocols
 MultiHop support
 ----------------
 
-.. versionadded:: v7r3p21
-
 .. |trade|   unicode:: U+2122
 
 .. warning::

docs/source/AdministratorGuide/Systems/DataManagement/s3.rst

@@ -4,8 +4,6 @@
 S3 support in DIRAC
 -------------------
 
-.. versionadded:: v7r0p19
-
 .. contents:: Table of contents
    :depth: 2
 

docs/source/AdministratorGuide/Systems/Transformation/index.rst

@@ -46,10 +46,7 @@ Within the TS a user can (for example):
 
 Disadvantages:
 
-- For very large installations, the submission may be perceived as slow, since there is no use (not yet) of Parametric jobs.
-
-  .. versionadded:: v6r20p3
-     Bulk submission of jobs is working for the transformations, so job submission can be sped up considerably.
+- For very large installations, the submission may be perceived as slow, since there is no use (not yet) of Parametric jobs. Bulk submission of jobs is working for the transformations, so job submission can be sped up considerably.
 
 Several improvements have been made in the TS to handle scalability, and extensibility issues.
 While the system structure remains intact, "tricks" like threading and caching have been extensively applied.
@@ -691,9 +688,6 @@ Multi VO Configuration
 ----------------------
 
 
-
-.. versionadded:: v6r20p5
-
 There are two possibilities to configure the agents of the transformation system for the use in a multi VO installation.
 
  - Use the same WorkflowTaskAgent and RequestTaskAgents for multiple VOs, no

docs/source/DeveloperGuide/Overview/index.rst

@@ -112,7 +112,6 @@ Interfaces
    control the ongoing tasks. The Web interfaces are based on the DIRAC Web Portal framework which ensures
    secure access to the system service using X509 certificates loaded into the user browsers.
 
-.. versionadded:: 8.0
     DIRAC also has the ability to implement additional interfaces based on the http protocol, see :ref:`apis`.
 
 DIRAC Framework

docs/source/UserGuide/GettingStarted/GettingUserIdentity/index.rst

@@ -54,9 +54,6 @@ If another non-default user group is needed, the command becomes::
 
 where ``user_group`` is the desired DIRAC group name for which the user is entitled.
 
-.. versionadded:: 8.0
-   added the possibility to generate proxy with new `dirac-login` command, use *--help* switch for more information. E.g.: dirac-login <user_group>
-
 Token authorization
 -------------------
 

docs/source/UserGuide/Tutorials/JobManagementAdvanced/index.rst

@@ -345,8 +345,6 @@ using the "setNumberOfProcessors" method of the API::
 Calling ``Job().setNumberOfProcessors()``, with a value bigger than 1,
 will translate into adding also the "MultiProcessor" tag to the job description.
 
-.. versionadded:: v6r20p5
-
 Users can specify in the job descriptions NumberOfProcessors and WholeNode parameters, e.g.::
 
    NumberOfProcessors = 16;

src/DIRAC/DataManagementSystem/Agent/FTS3Agent.py

@@ -1,6 +1,4 @@
 """
-.. versionadded:: v6r20
-
 FTS3Agent implementation.
 It is in charge of submitting and monitoring all the transfers. It can be duplicated.
 

src/DIRAC/TransformationSystem/Agent/RequestTaskAgent.py

@@ -12,8 +12,6 @@
 * The options *SubmitTasks*, *MonitorTasks*, *MonitorFiles*, and *CheckReserved*
   need to be assigned any non-empty value to be activated
 
-* .. versionadded:: v6r20p5
-
    It is possible to run the RequestTaskAgent without a *shifterProxy* or
    *ShifterCredentials*, in this case the credentials of the authors of the
    transformations are used to submit the jobs to the RMS. This enables the use of

src/DIRAC/TransformationSystem/Agent/WorkflowTaskAgent.py

@@ -11,8 +11,6 @@
 The options *SubmitTasks*, *MonitorTasks*, *MonitorFiles*, and *CheckReserved*
 need to be assigned any non-empty value to be activated
 
-* .. versionadded:: v6r20p5
-
    It is possible to run the RequestTaskAgent without a *shifterProxy* or
    *ShifterCredentials*, in this case the credentials of the authors of the
    transformations are used to submit the jobs to the RMS. This enables the use of