Chris has a point. I use master because of the change in behavior of using double homing on my lathe (prox pulse and mechanical switch). The added ini flag allowed me to do this without a hiccup and I've been using it reliably ever since. I'm sure others are using it for the beta stuff that is working and just salivating for a new feature every time they do a sudo upgrade.
I'm probably speaking out of turn here, but I think doing something as dramatic as changing so much of the source code that it could essentially brick a lot of machines (at least for the short term) should come with a major release rather than a 2.x release. Linuxcnc 3.0 rather than 2.9. roll it out as a fresh start and let people pause and make the decision to change over, knowing full well that there will be little to no backwards compatibility while the current product maintenance tapers off, as there will need to be concurrent development of the py3 product and what would eventually become the "legacy" release. Case in point, mastercam went from v9 to X and from X to 20xx naming conventions when they went from the old clunky dos screens to the X windows interface and from the x interface to the ribbon. They continue to put out new "versions" of the same base software with incremental tweaks every year, but every major change results in a new naming convention. Esprit cam is the same way. Two different software products, but a lot of crossover in development until the TNG product is finished and they finally phase out esprit 20xx. Just my 0.000000002btc Phil T. The Feral Engineer Check out my LinuxCNC tutorials, machine builds and other antics at www.youtube.com/c/theferalengineer On Wed, May 12, 2021, 1:52 PM Chris Morley <[email protected]> wrote: > > > ________________________________ > From: Nicklas SB Karlsson <[email protected]> > Sent: May 12, 2021 4:45 PM > To: Rene Hopf via Emc-developers <[email protected]> > Subject: Re: [Emc-developers] Fwd: Re: Proposal: Stop supporting Py2 and > GTK2 in Master. > > Den 2021-05-12 kl. 11:56, skrev Rene Hopf via Emc-developers: > > > > On 12.05.21 11:51, andy pugh wrote: > >> On Wed, 12 May 2021 at 08:00, Chris Morley <[email protected]> > >> wrote: > >> > >>>> I meant a 2.9 python 2 release before switching master to python3 > >> > >> I can see the argument, but I don't think that 2.9 is ready to be a > >> proper > >> release. And we don't have a 2.9 release manager. > >> > >> We could consider archiving a set of buildbot .debs as a rollback option > >> for anyone caught out by the switch, but master isn't called "2.9" > >> for a > >> reason, it is not intended for use on any machine where continued > >> operation > >> is critical. > > > > is there anything currently in master that isnt in 2.8 that people who > > dont want to update their os might need? > > Use 2.8 because I know 2.9 is a moving target and that works great. > > > Nicklas Karlsson > > > There are people who use master because it has functions that 2.8 doesn't. > Otherwise I agree, use 2.8. > > > > > _______________________________________________ > 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
