Timeline for How to manage two major versions using SVN?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2011 at 10:33 | comment | added | Geerten | True. Thanks for the compliment about the OK structure :) | |
| Oct 26, 2011 at 10:29 | comment | added | mouviciel | This is what I understood. The way you proceed allows to choose which bugs from release version are to be injected to new version. Not every bug fix is relevant for the next release. | |
| Oct 26, 2011 at 10:26 | comment | added | Geerten | No, it's not about the merging from the branches. It's like the following: there is a bug in the released version. A branch is made from the released version trunk. Bug is fixed. Branch is merged in trunk of released version, and branch is merged in new version. | |
| Oct 26, 2011 at 10:24 | history | answered | mouviciel | CC BY-SA 3.0 |