Skip to content

Known issues (and next release) #41

Open

Description

@mdeff

Below are issues affecting the rc1 data release that cannot be fixed without a data update. As updating is disruptive (it'll break code and make results non-comparable), it should be done sparingly, e.g., to fix a fatal flaw or many small ones discovered over time.

Workarounds are explained in more details in the wiki.

Activity

  1. self-assigned this
    on Jun 13, 2020
  2. pinned this issue on Jun 13, 2020
  3. Repository owner locked and limited conversation to collaborators on Jun 13, 2020
  4. changed the title [-]Known issues and next release[/-] [+]Known issues (and next release)[/+] on Jun 13, 2020
  5. mdeff commented on Jun 17, 2020

    @mdeff
    OwnerAuthor

    Branches:

    • The master branch contains the code that produced the latest released data. The usage code and documentation can be updated but should work with the released data.
    • The next branch contains the code to produce the hypothetical next release of the data. The usage code is updated to any new data format.
    • The outputs branch is based on master and contains generated data (e.g., notebook outputs and figures) for convenience (most notably to run on binder).
  6. mdeff commented on Jun 17, 2020

    @mdeff
    OwnerAuthor

    Potential todos for a dataset update:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions