Sebastian,

Thank you for clarification.
I will take a look at the current state.

Am I correct in saying that I will need to do the following:

Build, test and perhaps fix the UI's on the master branch.
Backport this work into joints-axes branch, if any issues fix, and retest
on both branches.

Thank you,
-Tom


On Mon, Dec 21, 2015 at 11:08 AM, Sebastian Kuzminsky <[email protected]>
wrote:

> On 12/21/15 3:35 AM, Thomas Gambone II wrote:
>
>> What would one need to do the required testing after the maintenance?
>>
>
> I think you should make sure it compiles and runs with some fairly
> standard sim configs, and that at least the basic features work (come out
> of estop, home, jog, mdi, run programs, single step). I'd consider that a
> basic "good enough to ship" test.
>
> Then of course the maintainer's main responsibility is to respond to
> feedback from users and fix bugs as needed. Though based on the lack of
> feedback for the past many years, I don't think those UIs have a lot of
> users.
>
> --
> Sebastian Kuzminsky
>
>
>
>
>> Thank you,
>> -Tom
>>
>> On Sun, Dec 20, 2015 at 9:42 PM, Jeff Epler <[email protected]>
>> wrote:
>>
>> In his curent joints-axes branch, dgarr/ja10v2, Dewey Garrett has
>>> removed the keystick (curses) and mini (sherline tcl/tk) user
>>> interfaces, because they need significant maintainance to be compatible
>>> with that branch.
>>>
>>> We have repeatedly stated that we hope that one major item in the next
>>> major LinuxCNC release is joints-axes.  This means that if no maintainer
>>> steps forward for these components, they will not be in the next version
>>> of LinuxCNC after the 2.7.x series.
>>>
>>> Please let us know if you are a developer (current or new) who hopes to
>>> maintain one of these UIs.  We can help you with advice and information,
>>> but right now I'm not aware of anyone who is planning to take the time
>>> to do the work and more importantly test keystick and mini once they're
>>> rehabilitated.
>>>
>>> Jeff
>>>
>>
------------------------------------------------------------------------------
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to