Rod, Part of the reverse run incompatibility is my fault; I often developed individual features based on the latest 2.7, to solve a particular user's needs (like UVW blending, reverse run, spindle sync improvements). By maintaining them as separate branches for so long, it was easy to let small incompatibilities grow as each feature got more complex. My goal was to keep the features independent so they could be merged or kicked back individually. I think in general this is the right way to work if merges are timely, but if they aren't, we end up here.
I want to devote some time to getting all the TP branches into master, so I'm glad that Phill did the legwork to get reverse run up to date! Can you send me a link? I'd like to do the other merges on top of that branch. Best, Rob On Tue, May 21, 2019, 6:45 PM Rod Webster <[email protected]> wrote: > Chris/Rob/Andy > > I don't want to sound negative or a whinger. You guys are the custodians of > an amazing bit of software. I don't have the history of the project in my > head but I have only ever used master branch compiled from source and I > first did that about 3 years ago because I wanted to to build a gantry > machine. > > Reverse run is not even in master yet - so how could we release it? > > Come on Chris, This video by samco demonstrates reverse run working on a > machine in September 2015 > https://www.youtube.com/watch?v=3aYaHxT6ZnQ > Its been sitting there as a branch in git languishing with the last commit > being made in December 2015. > So the question really is why did Phill have to start again? All he did was > update that branch. It should have been in master by now. > Why don't you at least get his work into the official repository? > > The last commit to the state tags branch was in February 2015 and I > understand its been in use commercially since around then. > What causes this paralysis? > > Why did I see Andy's multi spindle sneak into master and I knew nothing > about it? Yeh, I know I don't use a spindle but I do follow progress pretty > closely > You might recall that was not entirely bug free on its debut. > > I think what Phill has done with his plasma component and GU's is amazing. > It opens up LinuxCNC to a whole new class of machine that is growing in > popularity in industry everywhere. Andy might be right plasma does need a > new task module but for now there is a high class working solution. But he > should not need to maintain the core code for a 4 year old feature on a > private repository to achieve it. > > > Rod Webster > *1300 896 832* > +61 435 765 611 > Vehicle Modifications Network > www.vehiclemods.net.au > > > On Wed, 22 May 2019 at 07:53, Robert Ellenberg <[email protected]> wrote: > > > Hi Randy, > > > > Welcome to the community! It's great to hear that you've been a long time > > user and want to contribute. If you have any interest in motion / TP, I'm > > happy to answer questions (since there's a lot of history there). > > > > Andy / Chris / Rod / Phillip, I agree that the languishing release > schedule > > and slow uptake of contributions has caused many headaches, in particular > > the incompatibilities in various TP branches. I also like the idea of a > 2.8 > > release with current features (+bugfixes), and re-open master for new > > features. > > > > FWIW, I would also like a more formal release schedule. The team has > done a > > good job of pushing out point releases for 2.7, but it seems like 2.8 is > an > > ever-receding goal. Some ideas for how to improve: > > > > - Periodic dev meetings (IRC or via videoconference) to set milestones > > and document our decisions (so we're not constantly second guessing > > ourselves or having to re-answer the same questions). > > - Identify some areas of expertise and/or responsibility (and list > them > > publicly) so that contributors know who to include in their pull > > requests / > > code reviews. Bugs in can be assigned to experts to triage / fix, or > > delegate to someone who can. > > - Expand test coverage, particularly unit tests. I have some tests > > implemented in my branches (basic tests for TP and interp), but this > > would > > be a long-term effort to get wide coverage, particularly in > > rarely-touched > > code > > > > -Rob > > > > On Tue, May 21, 2019 at 5:45 PM andy pugh <[email protected]> wrote: > > > > > On Tue, 21 May 2019 at 22:17, Chris Morley <[email protected] > > > > > wrote: > > > > > > If we make a 2.8 stabilization branch right now then master is open to > > > > merge reverse run, python 3 work, state tags etc. > > > > And hopefully we won't wait three years to release again... > > > > > > > > > I think this might be the way to go. Lets get 2.8 frozen now, squash > the > > > (known) bugs and aim to release ASAP. > > > > > > Then we open up master to cool new stuff, as we will be less concerned > > > about breaking it. And then aim to have 2.8.1 (or 2.9) come out some > time > > > this year with reverse-run etc. > > > (This doesn't actually change much from the point of view of those > using > > > the feature, they will still be on an experimental branch, but at least > > it > > > isn't a reversion for them) > > > > > > With Wheezy EOL and the current LiveCD not really working at the > moment I > > > think that there is some urgency. > > > > > > (As a stopgap I am trying and failing to make a Wheezy / RTAI liveCD > that > > > works, and we have a patch already lined up to switch to preempt-rt and > > > Stretch for 2.7.14, but that leaves parallel-port users potentially in > > > trouble) > > > > > > -- > > > 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 > > > > > > > _______________________________________________ > > 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 > _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
