give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: To put the JSDoc how-to  (the word doc attached in DM-7224) at https://developer.lsst.io in this directory: https://github.com/lsst-dm/dm_dev_guide/tree/master/docs. So it will match up much better with the documentation system we're trying to build.      *Procedure to publish a developer's guide document to LSST:*            Follow https://github.com/lsst-dm/dm_dev_guide/blob/master/README.md          Use one example: Publish JSDocHowToShort.docx.    1. Clone the dm_dev_guide from git hub:                "git clone https://github.com/lsst-dm/dm_dev_guide"              "cd dm_dev_guide"    2. Create a branch. This can either be an informal user branch or a full-fledged ticket branch tracked in JIRA. See the DM Workflow guide (https://developer.lsst.io/processes/workflow.html#git-branching) for details.                "git branch tickets/DM-7554_publish_jsdoc_howto"              "git checkout tickets/DM-7554_publish_jsdoc_howto"    3. Make and commit your edits. Content is written in reStructuredText. Our reStructuredText Style Guide (https://developer.lsst.io/docs/rst_styleguide.html) covers the syntax you'll need.                Convert the docx file into rst file by pandoc:                    Install pandoc (http://pandoc.org/installing.html)                  Run pandoc in terminal:                         "pandoc -f docx JSDocHowToShort.docx -t rst -o jsdoc.rst"                View the rst file:                    Install restview: "pip install restview"                  Run restview in a terminal: "restview jsdoc.rst"                Need to hand edit the rst file to make sure it matches the docx format.                Add/commit the jsdoc.rst:                  "cp jsdoc.rst dm_dev_guide/docs"                  "git add docs/jsdoc.rst"                  "git commit"                Modify dm_dev_guide/index.rst and git add/commit:                  Add a line "docs/jsdoc.rst" after "docs/cpp_docs.rst"                  "git add index.rst"                  "git commit"    4. Push your development branch to GitHub and make a pull request. The pull request page will help you track the publishing and testing status of your branch. You can also track your branch's status directly on [Travis CI](https://travis-ci.org/lsst-dm/dm_dev_guide).                Squash all the commits:  "git rebase -i <commit number>" and more...              "git push -u origin tickets/DM-7554_publish_jsdoc_howto"                    (Note. Git push permit is required. Talk to J. Sick to add your github account into DM repos if you are not allowed to push.)                Goto https://github.com/lsst-dm/dm_dev_guide to submit a pull request.    5. If your build on [Travis](https://travis-ci.org/lsst-dm/dm_dev_guide) is successful, your branch will be published with LSST the Docs. You can review it even before merging to master.                If you have a ticket branch (`tickets/DM-NNNN`) the published URL is `https://developer.lsst.io/v/DM-NNNN`.              If you have a user branch (`u/username/name`) replace all `/` characters in your branch's name with `-` characters, e.g.: `https://developer.lsst.io/v/u-username-name`.                Or: Go to https://developer.lsst.io, click "Change edition" on the left and select the branch, go to Writing Docs session to see the published doc.    6. Once you're done, press the green button on your pull request to merge to `master`. Your changes will be automatically published to the main URL: https://developer.lsst.io. Don't worry about messing things up, GitHub branch protections will ensure that your edits build successfully, and that your branch is up-to-date with `master`.        This cheatsheet is added in https://confluence.lsstcorp.org/display/DM/Publish+DM+Develop+Guide+Document+Cheat+Sheet.              
Answer: 272013.0