Re: [Emc-developers] NOTICE: Feature freeze pending in view of a new release
From: Moses McKnight Sent: June 28, 2016 2:43 PM To: EMC developers Subject: [Emc-developers] NOTICE: Feature freeze pending in view of a new release Hi all, In accordance with the recommendation from the last IRC meeting, I plan to make a "feature freeze" and make a new branch for the next release in the near future. The joints/axes project merge is a pretty major thing and we would like to release this sooner than later. So does anyone that have a feature or something you are working on that you would like to get in before the release? After the branch for the new release, mostly only bug fixes and stabilizing commits will be accepted on that branch, but also allowed are things such as new drivers or hal comps and similar which usually can't break existing things. My tentative plan is to wait a couple of weeks before branching, but I'm open to suggestions. It seems a bit premature to pull out a new branch right after merging with master. Why not let it sit in master for a couple months first to see if any problems come up immediately. I would bet (arguably) master gets used wider then a new branch will. For instance has anyone made a config with stepconf and pncconf to see if they work properly in more then basic options? These two programs are notoriously under tested before a new release and JA was a big change. Since JA doesn't really add anything for the majority of users (trivial kins) waiting a bit wouldn't seem to hurt much. Just putting the thought out there. Chris M -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] NOTICE: Feature freeze pending in view of a new release
... I would like to see the reverse run branch. What is its status? On Jun 28 2016 11:43 AM, sam sokolik wrote: > I think the reverse run branch should get merged after the freeze. > > On 6/28/2016 11:08 AM, Chris Radek wrote: >> On Tue, Jun 28, 2016 at 11:36:40AM -0400, John Kasunich wrote: >>> It is only monotonically increasing if you interpret it as two >>> integers >>> separated by a dot. Humans can interpret it any way they want, but >>> how do programs interpret it? >> for debian packages this is really well defined, but also very >> complicated, so dpkg has a way you can ask: >> >> % dpkg --compare-versions 2.9 lt 2.10 && echo yep it is >> yep it is >> >> >> >> -- >> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in >> San >> Francisco, CA to explore cutting-edge tech and listen to tech >> luminaries >> present their vision of the future. This family event has something >> for >> everyone, including kids. Get more information and register today. >> http://sdm.link/attshape >> ___ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers >> >> > > > > -- > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in > San > Francisco, CA to explore cutting-edge tech and listen to tech > luminaries > present their vision of the future. This family event has something > for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > ___ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] NOTICE: Feature freeze pending in view of a new release
I think the reverse run branch should get merged after the freeze. On 6/28/2016 11:08 AM, Chris Radek wrote: > On Tue, Jun 28, 2016 at 11:36:40AM -0400, John Kasunich wrote: >> It is only monotonically increasing if you interpret it as two integers >> separated by a dot. Humans can interpret it any way they want, but >> how do programs interpret it? > for debian packages this is really well defined, but also very > complicated, so dpkg has a way you can ask: > > % dpkg --compare-versions 2.9 lt 2.10 && echo yep it is > yep it is > > > -- > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > ___ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > > -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] NOTICE: Feature freeze pending in view of a new release
On Tue, Jun 28, 2016 at 11:36:40AM -0400, John Kasunich wrote: > > It is only monotonically increasing if you interpret it as two integers > separated by a dot. Humans can interpret it any way they want, but > how do programs interpret it? for debian packages this is really well defined, but also very complicated, so dpkg has a way you can ask: % dpkg --compare-versions 2.9 lt 2.10 && echo yep it is yep it is -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] NOTICE: Feature freeze pending in view of a new release
On 28 June 2016 at 15:43, Moses McKnight wrote: > So does anyone that have a feature or something you are working on that you > would like to get in before the release? I have a patch that supports multiple spindles. I do not expect to merge that immediately, but would like to see it go into Master for shake-down after 2.8 has branched off. The only thing that I am thinking of for the imminent release is some sort of sticky-tool-in-spindle config switch. -- 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 -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] NOTICE: Feature freeze pending in view of a new release
On Tue, Jun 28, 2016, at 11:23 AM, Sebastian Kuzminsky wrote: > On 06/28/2016 08:43 AM, Moses McKnight wrote: > > Another item I'm considering is changing the version to 3.0 for the next > > release. Any thoughts pro or con? If we don't change it this time, I would > > recommend using 2.8 now, 2.9 for the next major release and then 3.0 > > (instead of > > 2.10 etc) > The version is just a number to me, as long as it's monotonically > increasing I'm happy. > > I see no reason that .10 should be disallowed or should trigger the > change to 3.0. If 3.0 follows 2.9 by policy, then we should just drop > the decimal point, it doesn't add anything at that point. Depends on how you define "monotonically increasing". Interpreted character-by-character as a string, 2.10 sorts before 2.2 Interpreted as a floating point number, 2.10 sorts before 2.2 It is only monotonically increasing if you interpret it as two integers separated by a dot. Humans can interpret it any way they want, but how do programs interpret it? -- John Kasunich jmkasun...@fastmail.fm -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] NOTICE: Feature freeze pending in view of a new release
On 06/28/2016 08:43 AM, Moses McKnight wrote: > In accordance with the recommendation from the last IRC meeting, I plan to > make > a "feature freeze" and make a new branch for the next release in the near > future. The joints/axes project merge is a pretty major thing and we would > like > to release this sooner than later. This is a good plan. I'm looking forward to the next stable release. > So does anyone that have a feature or something you are working on that you > would like to get in before the release? Francis Tisserant and i started work on revamping how our translations are handled, but it's not going to be ready for this release. Once it's ready I'll merge it into master (this will be after you make the stable branch). So what i'm saying is, i've got nothing special that i want to get in to the next stable release. I'll focus on stabilizing from here on. > Another item I'm considering is changing the version to 3.0 for the next > release. Any thoughts pro or con? If we don't change it this time, I would > recommend using 2.8 now, 2.9 for the next major release and then 3.0 (instead > of > 2.10 etc) The version is just a number to me, as long as it's monotonically increasing I'm happy. I see no reason that .10 should be disallowed or should trigger the change to 3.0. If 3.0 follows 2.9 by policy, then we should just drop the decimal point, it doesn't add anything at that point. $0.02 -- Sebastian Kuzminsky -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] NOTICE: Feature freeze pending in view of a new release
I vote 3.0 for JA. The integrator concepts and Ini changes are large enough to warrant it. Chris M - Reply message - From: "Moses McKnight" To: "EMC developers" Subject: [Emc-developers] NOTICE: Feature freeze pending in view of a new release Date: Tue, Jun 28, 2016 7:42 AM Hi all, In accordance with the recommendation from the last IRC meeting, I plan to make a "feature freeze" and make a new branch for the next release in the near future. The joints/axes project merge is a pretty major thing and we would like to release this sooner than later. So does anyone that have a feature or something you are working on that you would like to get in before the release? After the branch for the new release, mostly only bug fixes and stabilizing commits will be accepted on that branch, but also allowed are things such as new drivers or hal comps and similar which usually can't break existing things. My tentative plan is to wait a couple of weeks before branching, but I'm open to suggestions. Another item I'm considering is changing the version to 3.0 for the next release. Any thoughts pro or con? If we don't change it this time, I would recommend using 2.8 now, 2.9 for the next major release and then 3.0 (instead of 2.10 etc) Moses -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] NOTICE: Feature freeze pending in view of a new release
I do not have much of a dog in this fight (as the saying goes), but here are my 2c... JA a sufficient change to warrant a full version bump, BUT are enough of the internals changed to compare from EMC-1.* to EMC-2.* => LinuxCNC-2.*? That I am not sure of. If we are going to switch to LCNC-3.0, then when will we start talking about cleaning up some of the underlying infrastructure and move to 4.0? Are there any plans for what that might look like? I guess that might all seem like pie-in-the-sky talk, but having some idea for what we want in 2.8/9, 3.0, and 4.0 would help the overall plan. Just my 2c... EBo -- On Jun 28 2016 8:43 AM, Moses McKnight wrote: > Hi all, > > In accordance with the recommendation from the last IRC meeting, I > plan to make > a "feature freeze" and make a new branch for the next release in the > near > future. The joints/axes project merge is a pretty major thing and we > would like > to release this sooner than later. > > So does anyone that have a feature or something you are working on > that you > would like to get in before the release? > > After the branch for the new release, mostly only bug fixes and > stabilizing > commits will be accepted on that branch, but also allowed are things > such as new > drivers or hal comps and similar which usually can't break existing > things. > > My tentative plan is to wait a couple of weeks before branching, but > I'm open to > suggestions. > > Another item I'm considering is changing the version to 3.0 for the > next > release. Any thoughts pro or con? If we don't change it this time, > I would > recommend using 2.8 now, 2.9 for the next major release and then 3.0 > (instead of > 2.10 etc) > > Moses > > > -- > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in > San > Francisco, CA to explore cutting-edge tech and listen to tech > luminaries > present their vision of the future. This family event has something > for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > ___ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
[Emc-developers] NOTICE: Feature freeze pending in view of a new release
Hi all, In accordance with the recommendation from the last IRC meeting, I plan to make a "feature freeze" and make a new branch for the next release in the near future. The joints/axes project merge is a pretty major thing and we would like to release this sooner than later. So does anyone that have a feature or something you are working on that you would like to get in before the release? After the branch for the new release, mostly only bug fixes and stabilizing commits will be accepted on that branch, but also allowed are things such as new drivers or hal comps and similar which usually can't break existing things. My tentative plan is to wait a couple of weeks before branching, but I'm open to suggestions. Another item I'm considering is changing the version to 3.0 for the next release. Any thoughts pro or con? If we don't change it this time, I would recommend using 2.8 now, 2.9 for the next major release and then 3.0 (instead of 2.10 etc) Moses -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
