You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
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.
Activity
neithernut commentedon Aug 29, 2014
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.
matthiasbeyer commentedon Aug 29, 2014
👍
matthiasbeyer commentedon Sep 12, 2014
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.neithernut commentedon Sep 12, 2014
ACK.
neithernut commentedon Sep 13, 2014
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.matthiasbeyer commentedon Sep 13, 2014
👍