Replies: 3 comments
-
Yes, I would favor that.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Okay, I'll kill off the develop branch after the next release and see how it goes. Can always reinstate it latter if needed. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I've now removed the dev branch as discussed. Any future pull requests etc should now be done against master which should hopefully minimize friction and mean that more frequent small releases as time allows (pretty busy with other priorities these days unfortunately). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been thinking about this on and off now for a while now and thinking that it might be a good idea to stop using GIT flow workflow and revert to more common approach of just using main\master and releasing from that branch. New features can of course still be implemented in their own branches however future releases would just be done by creating a tag from main when ready.
This would also make it easier to see the current state of development and should prevent confusion around what branch should be used for pull-requests. I also have no interest in maintaining multiple versions (E.g. 4.1.1 and 5.0) so issuing of hotfixes etc isn't a problem.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions