# HG changeset patch
# User John Rouillard <rouilj@ieee.org>
# Date 1762580439 18000
# Node ID bc3d3c54e1f01b9e732f933e99077906f10de218
# Parent  5346abcf429ea5791af8f9097f5286f48d0319e1
doc: removed line referencing API change in 1.6

Removed sentence:

  This may be fixed in Roundup 1.6 by introducing
  ``init_web(client)`` callback or a more flexible extension point
  mechanism.

as I think RegisterAction can be used for both cgi/html
interface (action inherits from roundup.cgi.actions.Action) and
rest/xmlrpc interface (action inherits from roundup.actions.Action).

diff -r 5346abcf429e -r bc3d3c54e1f0 doc/reference.txt
--- a/doc/reference.txt	Fri Nov 07 22:14:01 2025 -0500
+++ b/doc/reference.txt	Sat Nov 08 00:40:39 2025 -0500
@@ -1368,10 +1368,8 @@
 each file supplying itself as a first argument.
 
 Note that at this point web interface is not loaded, but
-extensions still can register actions for it in the tracker
-instance. This may be fixed in Roundup 1.6 by introducing
-``init_web(client)`` callback or a more flexible extension point
-mechanism.
+extensions can register actions for it in the tracker
+instance.
 
 * ``instance.registerUtil`` is used for adding `templating utilities`_
   (see `adding a time log to your issues
@@ -1384,8 +1382,9 @@
 
 * ``instance.registerAction`` is used to add more actions to the
   instance and to web interface. See `Defining new web actions`_
-  for details.  Generic action can be added by inheriting from
-  ``action.Action`` instead of ``cgi.action.Action``.
+  for details.  Generic action (used by xmlrpc or rest interfaces) can
+  be added by inheriting from ``action.Action`` instead of
+  ``cgi.action.Action``.
 
 .. _interfaces.py:
 .. _modifying the core of Roundup: