it sounds like quite a bit more work to have multiple SVN for multiple branches.
it would be slick though to saved the SVN timestamp / revision for old releases somewhere. even upbge is based on the same SVN (we have a upbge eevee branch that stays current w/master) On Fri, Mar 15, 2019 at 10:11 AM Brecht Van Lommel < [email protected]> wrote: > There is no 2.79c planned currently. > > The main issue here is naming. The changes in this branch are not just > bugfixes on top if 2.79, there are also new features and a few > compatibility breaking changes. We can't undo those, users of that branch > are already relying on them. > > In the future we should two things different (that I have argued for > before): > * Increase Blender version immediately at the start of the release cycle, > not at the end. > * Avoid long release cycles like for 2.80, so there is no need to add new > features in both branches. > > > On Fri, Mar 15, 2019 at 5:30 PM Brian Savery <[email protected]> > wrote: > > > First of all, not sure if a 2.79C build is planned. But we've noticed > > something odd recently. Namely, that nightly builds of 2.79 use python > > version 3.7.0, whereas the "released" 2.79b build uses 3.5.3 > > > > Not a big deal, it's python right? Well except there are plenty of > addons > > that use C-Extensions for python. On certain platforms (windows > > particularly) a python C-Extension is not forward compatible (unless you > > use some particular limited feature set). So addon users get errors when > > trying to use "2.79" versions of addons that use c-extensions. > > > > Furthermore, I would claim from a release management standpoint, if > you're > > calling something a 2.79 build of Blender, it should not be switching > > python versions. Basic api compatibility. I'm assuming the reason this > > was done was that you're using the same build machines for 2.80 which > uses > > python 3.7, but it is possible to run multiple versions of python on one > > machine. Can this be fixed please? > > > > Brian > > _______________________________________________ > > Bf-committers mailing list > > [email protected] > > https://lists.blender.org/mailman/listinfo/bf-committers > > > _______________________________________________ > Bf-committers mailing list > [email protected] > https://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] https://lists.blender.org/mailman/listinfo/bf-committers
