Timeline for Stopping developers committing to the wrong branch on DVCS
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Apr 23, 2014 at 18:49 | history | edited | user40980 | CC BY-SA 3.0 |
Don't need webarchive link.
|
| Dec 12, 2013 at 6:46 | history | edited | gnat | CC BY-SA 3.0 |
1) link is recovered now (wayback URLs are blocked by some firewalls) 2) mini-quote to help readers search if it goes away again // http://chat.stackexchange.com/transcript/message/12606174#12606174
|
| Dec 12, 2013 at 2:53 | history | edited | user40980 | CC BY-SA 3.0 |
Link to wayback machine for article
|
| Sep 10, 2013 at 14:10 | comment | added | user40980 | @imp25 (and some StackOverflow questions and answers about hgflow - stackoverflow.com/questions/14011921/… stackoverflow.com/questions/13021807/… ) | |
| Sep 10, 2013 at 12:28 | comment | added | user40980 | @imp25 you may find hg-flow useful for the hg side rather than git. | |
| Sep 10, 2013 at 12:22 | comment | added | imp25 | I've accepted this answer as it will form the basis of changes we are going to make to our SCM. The links to Advanced SCM Branching Stratagies and the git-flow model have been particularly appreciated. We'll also try and invest in training to improve our developers understanding of what they do with HG. | |
| Sep 10, 2013 at 12:18 | vote | accept | imp25 | ||
| Sep 6, 2013 at 19:10 | comment | added | user40980 | @mattnz There are more advanced branching (ghads, I'm going to use the word) patterns. However, the 'everyone commit to dev always' and 'when ready, branch a release from dev' should get you 90% of the way to the solution. Then the only oddball cases are the 'working on a patch' and then its a "I know I'm doing this on an old release, switch to that branch". | |
| Sep 5, 2013 at 4:53 | comment | added | mattnz | +1 Great technical answer, might work if he does not document it, probably won't. Problem is not likely to be fully solved unless the branching stratagy is documented with clear procedures. | |
| Sep 4, 2013 at 2:17 | history | edited | user40980 | CC BY-SA 3.0 |
minor rename link
|
| Sep 4, 2013 at 2:07 | history | answered | user40980 | CC BY-SA 3.0 |