WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Release schedule / plan #21

@andreww

Description

@andreww

We should discuss the best way to release the code for when you submit the pyDis paper. I would aim to host a copy of the code on pypi and to put the documentation on readthedocs, while keeping track on versions etc. here on github. I think this means:

  1. Add a "tag" when you submit the code. Use this to generate a clean tarball for submission alongside the paper.
  2. After any revisions and on acceptance create a new tag (for version 1.0.0?). This could point to the same version, or a later version. Use this to generate a new tarball for the comp phys letters repo.
  3. In the meantime work out how to host a version of the code on pypi. This will mean that installation instructions can be "type pip install URL" and pydis will be installed.
  4. Look at how to host the documentation on readthedocs and / or github pages.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions