Am Freitag, dem 09.10.2026 um 01:48 +0000 schrieb Chris Morley: > I see much talk and some code hints to major changes coming in the > code. > Should we not pause and consider releasing before upsetting the code > base. > The HAL changes them selves are a very large change. > > From previous experience, a major code change requires a minimum of 6 > months to more commonly a year before code settles again. And a > release candidate is at least 6 months for stabilization. > > IMHO we should release before any wholesale NML changes go in at the > very least.
I agree, IMO as soon as the HAL changes are done we should branch off 2.10 and put out a release candidate. NML replacement will take some time until it is even clear what and how to do. We will discuss this on sunday. https://github.com/LinuxCNC/linuxcnc/discussions/4615 Andy's list from january had 1) simplifying HAL types (32/64bit etc...) 2) getting rid of parameter limitations in HAL and 3) new tormach TP. IMO integration of the new tormach TP isn't going to happen, there seems to be more stuff going on regarding trajectory planning, and we should probably release 2.10 before any really major architectural stuff is changed. At the last video meeting I learned that sunday morning in US timezones is inconvenient for some people. Please suggest more convenient weekdays/times than what we do currently for regular online video meetings. _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
