I like the branch idea, unless the change can be tested. If you created a 2.3 9.04 branch does it get updated automagiclly with other 2.3 changes or would someone have to monitor that? I'm not exactly sure how everything works in git but I like it.
John On 23 Jun 2009 at 16:12, Jeff Epler wrote: > As a matter of policy, should I accept changes onto a stable branch > that > fix platforms other than the ones we package? > > My practice before now has been not to do this, because it poses a > needless risk that the platforms we do package for will have a bug > introduced. > > (One example of the kind of patch I feel uneasy about is > http://git.linuxcnc.org/gitweb?p=emc2.git;a=commit;h=eeb716dc > which fixes a visual problem on 9.04 but introduces new code that > is > totally unneeded on 6.06 and 8.04. On the other hand, I > cherry-picked > http://git.linuxcnc.org/gitweb?p=emc2.git;a=commit;h=4048fa9d > which is also to fix a 9.04 build issue because it's a build-time > item > and problems would show up right away before packages are > released) > > However, with a fair number of people wanting to build sim on 9.04 > and > the like, it's a pity to tell them they have to use TRUNK, which > creates > a bad experience when they hit bugs. > > An alternative is to create a separate branch which is v2_3_branch > + > patches for unsupported builds. (this is of course much easier with > git > than it was with cvs, specifically merging in new changes from the > v2_3_branch to the porting branch) > > Thoughts? > > Jeff > > -------------------------------------------------------------------- > ---------- > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
