09-30-2016, 03:22 PM
Have y'all ever considered moving all your source code into github (or another similar)? It would make life so much easier in terms of keeping bug fixes updated in each minor release, ease moving new features developed in an earlier release into the latest release, etc.
For example, I am ready to move forward on nested groups. But should I do it on 4.4 or 5.0? The easy answer is 5.0,but I don't want to wait for 5.0 release. So I develop it in stable 4.4 but how will it get into 5.0 without a horrendous, manual process of editing the changes into the new code 1 by 1.
Another example. I messed around with db.php and then wanted to upgrade to the next release. If it was in github it would simply be a question of checking out the next version and letting it handle the merging of changes. If there are conflicts then it tells you and you have to do the laborious manual editing, but with access to some tools that help...
Thoughts? Or maybe y'all already have it in some other source code mgmt system...?
For example, I am ready to move forward on nested groups. But should I do it on 4.4 or 5.0? The easy answer is 5.0,but I don't want to wait for 5.0 release. So I develop it in stable 4.4 but how will it get into 5.0 without a horrendous, manual process of editing the changes into the new code 1 by 1.
Another example. I messed around with db.php and then wanted to upgrade to the next release. If it was in github it would simply be a question of checking out the next version and letting it handle the merging of changes. If there are conflicts then it tells you and you have to do the laborious manual editing, but with access to some tools that help...
Thoughts? Or maybe y'all already have it in some other source code mgmt system...?