> I think we should merge JA into master before the 2.8 branch. We just
> released 2.7, so this is a fine time for big experimental features.
>
> But i strongly disagree that we should merge it while it has such
> glaring known problems. JA does not not currently work on lathes, or on
> other machines with non-consecutive axes! That's unacceptable in
> master, IMO.
>
> When someone volunteers their time and fixes this bug, it will be closer
> to mergeable. But "forcing" has no place in a volunteer organization.
>
>
> --
> Sebastian Kuzminsky
Well we force people all the time - that's how we more forward.
switching to debian from ubuntu forced me to do work.
any changes to config forces me to do work on stepconf or pncconf.
Changes to hostmot2 usually forces me to do work.
force is a strong word but I wasn't sure what word fit properly.
Do you mean you someone will update stepconf and pncconf and all the guis
(I assume they will need work) before JA will be merged?
If you pull out 2.8 now (maybe be liberal with what can go in it for a while)
and then merge JA into master that gives plenty of time to fix the issues.
But until it's in master it will take forever to get it mergeable - whats it
been 6 years?
It's one of those features that is hard to move forward on it's own because few
people _need_ it right now but after it's in it opens up possibilities.
If you put it in master then It _needs_ to be fixed and it will be fixed.
If you and others think it is _way_ to far from being fixable or has unfixable
issues
then that is different altogether - but that doesn't seem to be the case.
If JA is a worthwhile feature then IMHO its time to make it happen, not another
5 years
down the road.
But that's just my opinion of course maybe no one feels the same.
Chris M
------------------------------------------------------------------------------
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
