Timeline for Using semantic version with trunk based development for Python package
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2019 at 11:14 | vote | accept | dcs3spp | ||
| Apr 12, 2019 at 11:14 | comment | added | dcs3spp | Thanks @Ewan, will try out versioning approach and accept answer..... | |
| Apr 12, 2019 at 10:36 | comment | added | Ewan | you have to do it twice | |
| Apr 12, 2019 at 10:22 | comment | added | dcs3spp | Thanks for responding @Ewan, appreciated. Ok, I think I understand... so version held in version.py file would be patch bumped on each release branch and not merged back to trunk. On the trunk, version.py would be bumped for major/minor changes. Trying to understand the cherry-picking issue though....what happens if fix needs to be available on trunk and future releases also? | |
| Apr 12, 2019 at 9:58 | history | answered | Ewan | CC BY-SA 4.0 |