|
|
|
|
|
by VLM
3731 days ago
|
|
Jenkins should always pass master. develop is for things that need to be done but necessarily mean Jenkins is at least temporarily very unlikely to succeed and thats "OK" or even "normal". Or another way to put it is develop doesn't even have to compile. I mean, it would be nice if it does, but its OK if it doesn't. master might not do what the end users think its supposed to do, but at least it compiles. Or another way to put it is develop is for big revolutions and master is for small evolutions. git flow releases are supposed to actually do what the end users think its supposed to do. Or it actually does what they've been told to expect. It provides a natural flow of code, from a feature doesn't work but its worth a share, to it compiles but doesn't implement business required feature #1243 or feature #531, to we think it correctly meets the business needs at least as of one definition of need at one point. Or another way to put it is a separation of development process of develop to master from the business requirements of master to a release branch. I suppose everyone uses it a little differently. |
|