On Wed, 19 Sep 2018 at 05:46, Kurt Jacobson <[email protected]> wrote:
> I agree with Chris. I don't think there could be a better time to release > master, 2.8, or whatever it will be called. At this point it has been > stable for some time and has been VERY heavily tested and a LOT of people > are using it in production. If anything it is more reliable than the > current stable. I am a strong proponent of merging Multi Spindle, External > Offsets, Revers Run and QtVCP, but I think we should seriously think about > releasing master beforehand. If we don't it will probably end up being > another year at least before it is released. That is beginning to sound all too prophetic. Around this time last year I seem to recall stating a hope that we could get 2.8 out by the New Year. I still think that would be good, but it's now a different New Year. What are the current roadblocks? As I see it: 1) Nobody knows how to make ISOs. This is only approximately true, I think I managed to make one, but not very well. 2) Python / GTK / that sort of stuff. Touchy / gscreen / gmoccapy don't work on my Stretch VM or my Stretch test machine (No Glade). Is that just me? 3) Some bugs. These are "milestoned" as 2.8 (not sure what that means) https://github.com/LinuxCNC/linuxcnc/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.8 These are tagged as "affects 2.8: https://github.com/LinuxCNC/linuxcnc/labels/affects%202.8 How many of those are truly blocking? I think that any that currently exist in 2.7 are unfortunate, but not blocking. But are there other opinions? -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1916 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
