backlogops-cli 0.1__tar.gz → 0.2__tar.gz

{backlogops_cli-0.1 → backlogops_cli-0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops-cli
-Version: 0.1
+Version: 0.2
 Summary: Command line interface for backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -24,7 +24,8 @@ Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
 Requires-Dist: argcomplete>=3.6.3
-Requires-Dist: backlogops>=0.1
+Requires-Dist: backlogops>=0.2
+Requires-Dist: versionreporter>=0.3
 Dynamic: author
 Dynamic: license-file
 Dynamic: requires-dist
@@ -34,16 +35,17 @@ Dynamic: requires-python
 
 There are 3 related packages for backlog operations:
 
-- backlogops: a collection of library functions to manipulate backlogs
+- **[backlogops](https://pypi.org/project/backlogops/)** a collection of library
+  functions to manipulate backlogs
 
-- backlogops-cli: command line interface to use the functions in the library.
-  This is just a thin wrapper around the library functions. It serves a dual
-  purpose as both an example of how to use the library and as a tool for the
-  user to use the library.
+- **[backlogops-cli](https://pypi.org/project/backlogops-cli/)** command line
+  interface to use the functions in the library. This is just a thin wrapper
+  around the library functions. It serves a dual purpose as both an example of
+  how to use the library and as a tool for the user to use the library.
 
-- backlogops-gui: graphical user interface to use the functions in the library.
-  It is based on TkInter. The ambition is to keep it as a thin wrapper around
-  the library.
+- **[backlogops-gui](https://pypi.org/project/backlogops-gui/)** graphical user
+  interface to use the functions in the library. It is based on TkInter. The
+  ambition is to keep it as a thin wrapper around the library.
 
 ## Available functionality
 
@@ -72,6 +74,9 @@ The following functionality is available in all 3 packages:
   the key is at a higher level it will bring all items it is a parent of in
   front of it (recursively).
 
+- Reorder the backlog in release order, optionally taking dependencies into
+  account.
+
 - Set planned release dates from the estimated release dates.
 
 - Calculate the release dates from the backlog items estimated ready dates, with
@@ -79,7 +84,23 @@ The following functionality is available in all 3 packages:
 
 - Validate the backlog and releases for consistency.
 
-- A wizard to create an available teams configuration.
+- Convert a backlog and releases between table file formats.
+
+- Order the releases by their planned or estimated date.
+
+- Rename columns when reading a file and when writing a file.
+
+- Map custom status names in input files to backlog item statuses.
+
+- Choose how backlog item levels are written: by number, by name, or both, and
+  configure custom level names.
+
+- Create stand-alone input or output preset configuration files.
+
+- Migrate an older configuration or preset file to the current file format.
+
+- A wizard to create a backlog-ops configuration file with the workforce, named
+  input and output presets, level names, and status name mapping.
 
 ## The operating model
 
@@ -97,45 +118,45 @@ availability of the team members.
 Each backlog item has the following fields that are used by the algorithms in
 the library:
 
-- key: The key of the backlog item. Required. Must be unique. Must not be empty,
-  must not contain whitespace and must not contain any of the characters , . ; :
-  ( ) \[ \] \{ \}.
+- `key` The key of the backlog item. Required. Must be unique. Must not be
+  empty, must not contain whitespace and must not contain any of the characters
+  , . ; : ( ) \[ \] \{ \}.
 
-- level: The level of the backlog item. Required. Must be an integer.
+- `level` The level of the backlog item. Required. Must be an integer.
 
-- title: The title of the backlog item. Required.
+- `title` The title of the backlog item. Required.
 
-- story_points: The story points of the backlog item. Required.
+- `story_points` The story points of the backlog item. Required.
 
-- status: The status of the backlog item. Required.
+- `status` The status of the backlog item. Required.
 
-- parent_key: The key of the parent backlog item. Optional. Must exist as a key
+- `parent_key` The key of the parent backlog item. Optional. Must exist as a key
   in the backlog. Parent keys are used to build the hierarchy of the backlog.
   The parent key must be at a higher level than the current item. Parent keys
   introduce implicit dependencies between items: the current item cannot start
   before the parent item starts, and the parent item cannot finish before all
   its children have finished.
 
-- release: The release of the backlog item. Optional. Follows the same character
-  rules as the key. Must not be empty string.
+- `release` The release of the backlog item. Optional. Follows the same
+  character rules as the key. Must not be empty string.
 
-- team: The team responsible for the backlog item. Optional. Must not be empty
+- `team` The team responsible for the backlog item. Optional. Must not be empty
   string. Must be a valid team name. If None the item can be done by any team.
   If not None. the item can only be done by the specified team.
 
-- depends_on_f2s: The list of keys of the backlog items that must have been
+- `depends_on_f2s` The list of keys of the backlog items that must have been
   finished before the current item can start. May be empty.
 
-- depends_on_f2f: The list of keys of the backlog items that must have been
+- `depends_on_f2f` The list of keys of the backlog items that must have been
   finished before the current item can finish. May be empty.
 
-- depends_on_s2s: The list of keys of the backlog items that must have been
+- `depends_on_s2s` The list of keys of the backlog items that must have been
   started before the current item can start. May be empty.
 
-- planned_ready_date: The planned ready date of the backlog item. The date that
+- `planned_ready_date` The planned ready date of the backlog item. The date that
   is communicated to the customer. Optional.
 
-- estimated_ready_date: The estimated ready date of the backlog item. Optional.
+- `estimated_ready_date` The estimated ready date of the backlog item. Optional.
 
 Additionally each backlog item can have any number of other fields.
 
@@ -184,33 +205,59 @@ backlogops_cli serves 2 purposes:
 ### Currently available commands
 
 ````text
+
   python3 -m backlogops_cli.adjust_release_content
      Adjust release content to fit the planned release dates
+
+  python3 -m backlogops_cli.config_wizard
+     Create a backlog-ops configuration file via a wizard
+
   python3 -m backlogops_cli.convert
      Convert a backlog and releases between table file formats
+
   python3 -m backlogops_cli.demo_backlog
      Write a demonstration backlog and releases to a file
+
   python3 -m backlogops_cli.estimate_ready_date
      Estimate ready dates for the backlog items
+
   python3 -m backlogops_cli.extract_keys
      Extract backlog keys at the given levels to a key list
+
   python3 -m backlogops_cli.list
      List all commands available in backlogops_cli
+
+  python3 -m backlogops_cli.migrate_cfg
+     Migrate a configuration file to the current file format
+
   python3 -m backlogops_cli.order_by_deps
      Reorder a backlog so that dependencies are fulfilled
+
   python3 -m backlogops_cli.order_by_keys
      Reorder a backlog so that key-list items come first
+
+  python3 -m backlogops_cli.order_by_release
+     Order the backlog to follow the release order
+
+  python3 -m backlogops_cli.order_releases
+     Order the releases by their planned or estimated date
+
   python3 -m backlogops_cli.plan_release_dates
      Set planned release dates from the estimated release dates
-  python3 -m backlogops_cli.teams_wizard
-     Create an AvailableTeams configuration file via a wizard
+
+  python3 -m backlogops_cli.preset_wizard
+     Create an input or output preset config file via a wizard
+
+  python3 -m backlogops_cli.version
+     Print version information for the backlogops_cli package
+
 ````
 
 ## Test summary
 
-- Test result: 1066 passed in 16s
+- Test result: 1545 passed in 32s
 - No flake8 warnings.
 - No mypy errors found.
 - No python layout warnings.
-- Built version(s): 0.1
+- Built version(s): 0.2
 - Build and test using Python 3.14.6

{backlogops_cli-0.1 → backlogops_cli-0.2}/README_pypi.md

@@ -2,16 +2,17 @@
 
 There are 3 related packages for backlog operations:
 
-- backlogops: a collection of library functions to manipulate backlogs
+- **[backlogops](https://pypi.org/project/backlogops/)** a collection of library
+  functions to manipulate backlogs
 
-- backlogops-cli: command line interface to use the functions in the library.
-  This is just a thin wrapper around the library functions. It serves a dual
-  purpose as both an example of how to use the library and as a tool for the
-  user to use the library.
+- **[backlogops-cli](https://pypi.org/project/backlogops-cli/)** command line
+  interface to use the functions in the library. This is just a thin wrapper
+  around the library functions. It serves a dual purpose as both an example of
+  how to use the library and as a tool for the user to use the library.
 
-- backlogops-gui: graphical user interface to use the functions in the library.
-  It is based on TkInter. The ambition is to keep it as a thin wrapper around
-  the library.
+- **[backlogops-gui](https://pypi.org/project/backlogops-gui/)** graphical user
+  interface to use the functions in the library. It is based on TkInter. The
+  ambition is to keep it as a thin wrapper around the library.
 
 ## Available functionality
 
@@ -40,6 +41,9 @@ The following functionality is available in all 3 packages:
   the key is at a higher level it will bring all items it is a parent of in
   front of it (recursively).
 
+- Reorder the backlog in release order, optionally taking dependencies into
+  account.
+
 - Set planned release dates from the estimated release dates.
 
 - Calculate the release dates from the backlog items estimated ready dates, with
@@ -47,7 +51,23 @@ The following functionality is available in all 3 packages:
 
 - Validate the backlog and releases for consistency.
 
-- A wizard to create an available teams configuration.
+- Convert a backlog and releases between table file formats.
+
+- Order the releases by their planned or estimated date.
+
+- Rename columns when reading a file and when writing a file.
+
+- Map custom status names in input files to backlog item statuses.
+
+- Choose how backlog item levels are written: by number, by name, or both, and
+  configure custom level names.
+
+- Create stand-alone input or output preset configuration files.
+
+- Migrate an older configuration or preset file to the current file format.
+
+- A wizard to create a backlog-ops configuration file with the workforce, named
+  input and output presets, level names, and status name mapping.
 
 ## The operating model
 
@@ -65,45 +85,45 @@ availability of the team members.
 Each backlog item has the following fields that are used by the algorithms in
 the library:
 
-- key: The key of the backlog item. Required. Must be unique. Must not be empty,
-  must not contain whitespace and must not contain any of the characters , . ; :
-  ( ) \[ \] \{ \}.
+- `key` The key of the backlog item. Required. Must be unique. Must not be
+  empty, must not contain whitespace and must not contain any of the characters
+  , . ; : ( ) \[ \] \{ \}.
 
-- level: The level of the backlog item. Required. Must be an integer.
+- `level` The level of the backlog item. Required. Must be an integer.
 
-- title: The title of the backlog item. Required.
+- `title` The title of the backlog item. Required.
 
-- story_points: The story points of the backlog item. Required.
+- `story_points` The story points of the backlog item. Required.
 
-- status: The status of the backlog item. Required.
+- `status` The status of the backlog item. Required.
 
-- parent_key: The key of the parent backlog item. Optional. Must exist as a key
+- `parent_key` The key of the parent backlog item. Optional. Must exist as a key
   in the backlog. Parent keys are used to build the hierarchy of the backlog.
   The parent key must be at a higher level than the current item. Parent keys
   introduce implicit dependencies between items: the current item cannot start
   before the parent item starts, and the parent item cannot finish before all
   its children have finished.
 
-- release: The release of the backlog item. Optional. Follows the same character
-  rules as the key. Must not be empty string.
+- `release` The release of the backlog item. Optional. Follows the same
+  character rules as the key. Must not be empty string.
 
-- team: The team responsible for the backlog item. Optional. Must not be empty
+- `team` The team responsible for the backlog item. Optional. Must not be empty
   string. Must be a valid team name. If None the item can be done by any team.
   If not None. the item can only be done by the specified team.
 
-- depends_on_f2s: The list of keys of the backlog items that must have been
+- `depends_on_f2s` The list of keys of the backlog items that must have been
   finished before the current item can start. May be empty.
 
-- depends_on_f2f: The list of keys of the backlog items that must have been
+- `depends_on_f2f` The list of keys of the backlog items that must have been
   finished before the current item can finish. May be empty.
 
-- depends_on_s2s: The list of keys of the backlog items that must have been
+- `depends_on_s2s` The list of keys of the backlog items that must have been
   started before the current item can start. May be empty.
 
-- planned_ready_date: The planned ready date of the backlog item. The date that
+- `planned_ready_date` The planned ready date of the backlog item. The date that
   is communicated to the customer. Optional.
 
-- estimated_ready_date: The estimated ready date of the backlog item. Optional.
+- `estimated_ready_date` The estimated ready date of the backlog item. Optional.
 
 Additionally each backlog item can have any number of other fields.
 
@@ -152,33 +172,59 @@ backlogops_cli serves 2 purposes:
 ### Currently available commands
 
 ````text
+
   python3 -m backlogops_cli.adjust_release_content
      Adjust release content to fit the planned release dates
+
+  python3 -m backlogops_cli.config_wizard
+     Create a backlog-ops configuration file via a wizard
+
   python3 -m backlogops_cli.convert
      Convert a backlog and releases between table file formats
+
   python3 -m backlogops_cli.demo_backlog
      Write a demonstration backlog and releases to a file
+
   python3 -m backlogops_cli.estimate_ready_date
      Estimate ready dates for the backlog items
+
   python3 -m backlogops_cli.extract_keys
      Extract backlog keys at the given levels to a key list
+
   python3 -m backlogops_cli.list
      List all commands available in backlogops_cli
+
+  python3 -m backlogops_cli.migrate_cfg
+     Migrate a configuration file to the current file format
+
   python3 -m backlogops_cli.order_by_deps
      Reorder a backlog so that dependencies are fulfilled
+
   python3 -m backlogops_cli.order_by_keys
      Reorder a backlog so that key-list items come first
+
+  python3 -m backlogops_cli.order_by_release
+     Order the backlog to follow the release order
+
+  python3 -m backlogops_cli.order_releases
+     Order the releases by their planned or estimated date
+
   python3 -m backlogops_cli.plan_release_dates
      Set planned release dates from the estimated release dates
-  python3 -m backlogops_cli.teams_wizard
-     Create an AvailableTeams configuration file via a wizard
+
+  python3 -m backlogops_cli.preset_wizard
+     Create an input or output preset config file via a wizard
+
+  python3 -m backlogops_cli.version
+     Print version information for the backlogops_cli package
+
 ````
 
 ## Test summary
 
-- Test result: 1066 passed in 16s
+- Test result: 1545 passed in 32s
 - No flake8 warnings.
 - No mypy errors found.
 - No python layout warnings.
-- Built version(s): 0.1
+- Built version(s): 0.2
 - Build and test using Python 3.14.6

{backlogops_cli-0.1 → backlogops_cli-0.2}/backlogops_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops-cli
-Version: 0.1
+Version: 0.2
 Summary: Command line interface for backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -24,7 +24,8 @@ Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
 Requires-Dist: argcomplete>=3.6.3
-Requires-Dist: backlogops>=0.1
+Requires-Dist: backlogops>=0.2
+Requires-Dist: versionreporter>=0.3
 Dynamic: author
 Dynamic: license-file
 Dynamic: requires-dist
@@ -34,16 +35,17 @@ Dynamic: requires-python
 
 There are 3 related packages for backlog operations:
 
-- backlogops: a collection of library functions to manipulate backlogs
+- **[backlogops](https://pypi.org/project/backlogops/)** a collection of library
+  functions to manipulate backlogs
 
-- backlogops-cli: command line interface to use the functions in the library.
-  This is just a thin wrapper around the library functions. It serves a dual
-  purpose as both an example of how to use the library and as a tool for the
-  user to use the library.
+- **[backlogops-cli](https://pypi.org/project/backlogops-cli/)** command line
+  interface to use the functions in the library. This is just a thin wrapper
+  around the library functions. It serves a dual purpose as both an example of
+  how to use the library and as a tool for the user to use the library.
 
-- backlogops-gui: graphical user interface to use the functions in the library.
-  It is based on TkInter. The ambition is to keep it as a thin wrapper around
-  the library.
+- **[backlogops-gui](https://pypi.org/project/backlogops-gui/)** graphical user
+  interface to use the functions in the library. It is based on TkInter. The
+  ambition is to keep it as a thin wrapper around the library.
 
 ## Available functionality
 
@@ -72,6 +74,9 @@ The following functionality is available in all 3 packages:
   the key is at a higher level it will bring all items it is a parent of in
   front of it (recursively).
 
+- Reorder the backlog in release order, optionally taking dependencies into
+  account.
+
 - Set planned release dates from the estimated release dates.
 
 - Calculate the release dates from the backlog items estimated ready dates, with
@@ -79,7 +84,23 @@ The following functionality is available in all 3 packages:
 
 - Validate the backlog and releases for consistency.
 
-- A wizard to create an available teams configuration.
+- Convert a backlog and releases between table file formats.
+
+- Order the releases by their planned or estimated date.
+
+- Rename columns when reading a file and when writing a file.
+
+- Map custom status names in input files to backlog item statuses.
+
+- Choose how backlog item levels are written: by number, by name, or both, and
+  configure custom level names.
+
+- Create stand-alone input or output preset configuration files.
+
+- Migrate an older configuration or preset file to the current file format.
+
+- A wizard to create a backlog-ops configuration file with the workforce, named
+  input and output presets, level names, and status name mapping.
 
 ## The operating model
 
@@ -97,45 +118,45 @@ availability of the team members.
 Each backlog item has the following fields that are used by the algorithms in
 the library:
 
-- key: The key of the backlog item. Required. Must be unique. Must not be empty,
-  must not contain whitespace and must not contain any of the characters , . ; :
-  ( ) \[ \] \{ \}.
+- `key` The key of the backlog item. Required. Must be unique. Must not be
+  empty, must not contain whitespace and must not contain any of the characters
+  , . ; : ( ) \[ \] \{ \}.
 
-- level: The level of the backlog item. Required. Must be an integer.
+- `level` The level of the backlog item. Required. Must be an integer.
 
-- title: The title of the backlog item. Required.
+- `title` The title of the backlog item. Required.
 
-- story_points: The story points of the backlog item. Required.
+- `story_points` The story points of the backlog item. Required.
 
-- status: The status of the backlog item. Required.
+- `status` The status of the backlog item. Required.
 
-- parent_key: The key of the parent backlog item. Optional. Must exist as a key
+- `parent_key` The key of the parent backlog item. Optional. Must exist as a key
   in the backlog. Parent keys are used to build the hierarchy of the backlog.
   The parent key must be at a higher level than the current item. Parent keys
   introduce implicit dependencies between items: the current item cannot start
   before the parent item starts, and the parent item cannot finish before all
   its children have finished.
 
-- release: The release of the backlog item. Optional. Follows the same character
-  rules as the key. Must not be empty string.
+- `release` The release of the backlog item. Optional. Follows the same
+  character rules as the key. Must not be empty string.
 
-- team: The team responsible for the backlog item. Optional. Must not be empty
+- `team` The team responsible for the backlog item. Optional. Must not be empty
   string. Must be a valid team name. If None the item can be done by any team.
   If not None. the item can only be done by the specified team.
 
-- depends_on_f2s: The list of keys of the backlog items that must have been
+- `depends_on_f2s` The list of keys of the backlog items that must have been
   finished before the current item can start. May be empty.
 
-- depends_on_f2f: The list of keys of the backlog items that must have been
+- `depends_on_f2f` The list of keys of the backlog items that must have been
   finished before the current item can finish. May be empty.
 
-- depends_on_s2s: The list of keys of the backlog items that must have been
+- `depends_on_s2s` The list of keys of the backlog items that must have been
   started before the current item can start. May be empty.
 
-- planned_ready_date: The planned ready date of the backlog item. The date that
+- `planned_ready_date` The planned ready date of the backlog item. The date that
   is communicated to the customer. Optional.
 
-- estimated_ready_date: The estimated ready date of the backlog item. Optional.
+- `estimated_ready_date` The estimated ready date of the backlog item. Optional.
 
 Additionally each backlog item can have any number of other fields.
 
@@ -184,33 +205,59 @@ backlogops_cli serves 2 purposes:
 ### Currently available commands
 
 ````text
+
   python3 -m backlogops_cli.adjust_release_content
      Adjust release content to fit the planned release dates
+
+  python3 -m backlogops_cli.config_wizard
+     Create a backlog-ops configuration file via a wizard
+
   python3 -m backlogops_cli.convert
      Convert a backlog and releases between table file formats
+
   python3 -m backlogops_cli.demo_backlog
      Write a demonstration backlog and releases to a file
+
   python3 -m backlogops_cli.estimate_ready_date
      Estimate ready dates for the backlog items
+
   python3 -m backlogops_cli.extract_keys
      Extract backlog keys at the given levels to a key list
+
   python3 -m backlogops_cli.list
      List all commands available in backlogops_cli
+
+  python3 -m backlogops_cli.migrate_cfg
+     Migrate a configuration file to the current file format
+
   python3 -m backlogops_cli.order_by_deps
      Reorder a backlog so that dependencies are fulfilled
+
   python3 -m backlogops_cli.order_by_keys
      Reorder a backlog so that key-list items come first
+
+  python3 -m backlogops_cli.order_by_release
+     Order the backlog to follow the release order
+
+  python3 -m backlogops_cli.order_releases
+     Order the releases by their planned or estimated date
+
   python3 -m backlogops_cli.plan_release_dates
      Set planned release dates from the estimated release dates
-  python3 -m backlogops_cli.teams_wizard
-     Create an AvailableTeams configuration file via a wizard
+
+  python3 -m backlogops_cli.preset_wizard
+     Create an input or output preset config file via a wizard
+
+  python3 -m backlogops_cli.version
+     Print version information for the backlogops_cli package
+
 ````
 
 ## Test summary
 
-- Test result: 1066 passed in 16s
+- Test result: 1545 passed in 32s
 - No flake8 warnings.
 - No mypy errors found.
 - No python layout warnings.
-- Built version(s): 0.1
+- Built version(s): 0.2
 - Build and test using Python 3.14.6

{backlogops_cli-0.1 → backlogops_cli-0.2}/backlogops_cli.egg-info/SOURCES.txt

@@ -10,14 +10,22 @@ backlogops_cli.egg-info/top_level.txt
 src/backlogops_cli/__init__.py
 src/backlogops_cli/__main__.py
 src/backlogops_cli/_command_io.py
+src/backlogops_cli/_migrate_warn.py
+src/backlogops_cli/_wizard_io.py
 src/backlogops_cli/adjust_release_content.py
+src/backlogops_cli/bloc_version_reporter.py
+src/backlogops_cli/config_wizard.py
 src/backlogops_cli/convert.py
 src/backlogops_cli/demo_backlog.py
 src/backlogops_cli/estimate_ready_date.py
 src/backlogops_cli/extract_keys.py
 src/backlogops_cli/list.py
+src/backlogops_cli/migrate_cfg.py
 src/backlogops_cli/order_by_deps.py
 src/backlogops_cli/order_by_keys.py
+src/backlogops_cli/order_by_release.py
+src/backlogops_cli/order_releases.py
 src/backlogops_cli/plan_release_dates.py
+src/backlogops_cli/preset_wizard.py
 src/backlogops_cli/py.typed
-src/backlogops_cli/teams_wizard.py
+src/backlogops_cli/version.py

backlogops_cli-0.2/backlogops_cli.egg-info/requires.txt

@@ -0,0 +1,3 @@
+argcomplete>=3.6.3
+backlogops>=0.2
+versionreporter>=0.3

{backlogops_cli-0.1 → backlogops_cli-0.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "backlogops-cli"
-version = "0.1"
+version = "0.2"
 authors = [
   { name="Tom Björkholm", email="klausuler_linnet0q@icloud.com" },
 ]

{backlogops_cli-0.1 → backlogops_cli-0.2}/setup.py

@@ -5,7 +5,7 @@ from setuptools import setup
 
 setup(
   name='backlogops-cli',
-  version='0.1',
+  version='0.2',
   description='Command line interface for backlog operations.',
   author='Tom Björkholm',
   author_email='klausuler_linnet0q@icloud.com',
@@ -15,6 +15,7 @@ setup(
   package_data={'backlogops_cli': ['src/py.typed']},
   install_requires=[
     'argcomplete >= 3.6.3',
-    'backlogops >= 0.1'
+    'backlogops >= 0.2',
+    'versionreporter >= 0.3'
   ]
 )