Skip to content

Switch to four-branch-wf #19

Open
Open

Description

@matthiasbeyer

We should switch to the four-branch-workflow as soon as possible. I suggest to switch as soon as the paper gets ready, which should be as soon as possible, too.

Four branch workflow means:

  • master for release-merges only
  • release for preparing releases (updating version numbers etc.)
  • develop for development
  • hotfix for hotfixes (optional)

Activity

  1. neithernut commented on Aug 29, 2014

    @neithernut
    Member

    Same regressions as last time: release- and hotfix branches should be ad-hoc and version specific.
    As for when to change the wf: the build setup should be finished, too.

  2. matthiasbeyer commented on Aug 29, 2014

    @matthiasbeyer
    MemberAuthor

    👍

  3. modified the milestone: v0.0.1 on Sep 5, 2014
  4. matthiasbeyer commented on Sep 12, 2014

    @matthiasbeyer
    MemberAuthor

    The build setup is finished, but I would like to keep the current workflow until v0.0.1. So we do not have to re-open all the PRs and so on.

  5. neithernut commented on Sep 12, 2014

    @neithernut
    Member

    ACK.

  6. neithernut commented on Sep 13, 2014

    @neithernut
    Member

    I'd suggest that, we aim for simple insertion, deletion and retrieval in v0.0.1, switch the WF and then add the "fancy" stuff.

  7. matthiasbeyer commented on Sep 13, 2014

    @matthiasbeyer
    MemberAuthor

    👍

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions