I believe the problem with patches is not that they have no one to
review them, but they have no where to go. Anything but trivial and
obvious fixes generally gets relegated into the "that could break
things" category and are silently shunned until they are forgotten or
otherwise go away. This leads to the splintering of LinuxCNC, since
there is no forward-looking "official" branch the community can make
significant contributions to.
For examples, see the Arais Robot folks, the joints-axis branches,
Michael and John's unified build code, the PREEMPT_RT patches that UBC
grew out of, etc.
I have said before and continue to feel that LinuxCNC needs a "Sid" or
"Fedora" branch where it's OK to break things and put new code
submissions. There they can be tested by the brave and cleaned up until
they're ready to fold into a stable release.
IMHO, without a change to where the patches go, no amount of patch
herding will make a bit of difference.
Again, I'm being Devil's Advocate here...PLEASE prove me wrong! :)
--
Charles Steinkuehler
char...@steinkuehler.net
Charles
I agree to lots of what you are saying there.
But I am not sure not having a lcnc_sig branch is the major problem either.
If a non-push access developer can't get their patch put in fairly easy, then
we are in the same boat.
eg UB3 (the closest to a linuxcnc SID) is on the linuxcnc repo but still has
limited access.
I think Michael updates it from time to time from others work.
In fact master was the unstable branch. It just that the releases are somewhat
slow, to the
point it's being used a fair amount in production machines (based on
forum/maillist questions)
It almost to the point of considering stopping development in 2.6 and open 2.7
for unstable work.
To destabilize 2.6 now seems a waste of months that people have spend using it
and reporting
/ fixing issues.
To me the real problem is a clear plan how it should all work.
I think it's a scaling problem as the project gets a development 'bubble'.
IMO a liaison is a good start. Given a little time they could also give us
feedback
on what would help and what is not helpful.
We have a release manager, why not a patch manager -both are very important.
Chris M
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
