简体   繁体   中英

Gitflow: One feature per release?

Does the git-flow workflow intend for one feature per release, so that as soon as a feature is merged into develop , a corresponding release branch is made? Or can a release branch contain multiple features (each of which were merged into develop that subsequently became a single release branch)?

I understand what's possible with git-flow. I'm asking what was the intention of git-flow regarding features and releases...what is the best practice , not all that is possible.

First of all, GitFlow permits you do so much features as you want.

Now, it's your decision how you'll work with it.

Some developers develop one feature and when finish this feature creates a release.

Some developers develop many features and times in times (eg each two weeks) they creates a new release with all features that they have in the develop branch.

只要您遵循正确的合并策略,Gitflow就可以在每个版本中包含多个功能,这听起来就像您一样。

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM