With the large number of changes to the architecture, will there be a jump
to 3.0 after 2.7?
On Wed, Apr 2, 2014 at 4:25 AM, sam sokolik <sa...@empirescreen.com> wrote:
> Yay! This is a good decision. Just a stepping stone to 2.7. (which
> won't be as long as 2.6 was)
>
> I have seen all the sausage making - with the relatively few people
> actively working on linuxcnc - big features/improvements are in the
> works. (and this takes time) (but thing are coalescing..)
>
> I just wish I could do more than play with {cough} I mean test linuxcnc.
>
> Keep up the great work!
>
> sam
>
>
> On 04/02/2014 01:50 AM, Sebastian Kuzminsky wrote:
> > I am pleased to announce the creation of a branch for stabilizing and
> > releasing LinuxCNC 2.6. This marks the beginning of the 2.6 release
> > process. Look for a 2.6.0~pre1 pre-release in the near future.
> >
> > The 2.6 branch does not contain either of the two big, hotly anticipated
> > merge candidates, joints-axes and unified-build-candidate. It is my
> > (unpopular) opinion that both of these branches require additional work
> > to be release-ready, and i don't want to hold up the 2.6 release any
> > longer. It's been two years since 2.5.0 and that's way too long. There
> > are good features that are ready to release today, so I want to get
> > those out to users while we finish up the next round of features for the
> > next release.
> >
> > Both branches are candidates for a future 2.7 release (as is Robert
> > Ellenberg's new trajectory planner). I intend for the 2.7 release cycle
> > to be much shorter than 2.6 was, and i intend to keep working with
> > everyone's help to make ready the features in the pipeline for 2.7. But
> > for now I ask for everyone's help in getting 2.6 out.
> >
> > Breaking with tradition, the 2.6 branch is called, simply, "2.6". Bug
> > fixes are welcome in 2.6 (or in v2.5_branch if appropriate), as are new
> > components and drivers, but commits that potentially destabilize
> > existing functionality should be reviewed before being pushed to the
> > release branch.
> >
> > The 2.6 release is targeting the following platforms:
> >
> > Realtime (RTAI):
> >
> > Ubuntu Lucid (32-bit, Linux 2.6.32)
> > Ubuntu Precise (32-bit, Linux 3.4)
> > Debian Wheezy (32-bit, Linux 3.4)
> >
> > Simulation:
> >
> > Ubuntu Lucid
> > Ubuntu Precise
> > Debian Wheezy
> >
> > Ubuntu Hardy (RTAI and simulation) is not currently supported because of
> > a build dependency of the new xhc-hb04 driver. If there is user desire
> > for 2.6 on Hardy we can disable that driver on Hardy (while still
> > shipping that driver on the newer platforms).
> >
> >
> > Work remaining/request for help:
> >
> > Testing - especially be on the lookout for any needed config changes
> > Squashing of bugs (https://sf.net/p/emc/bugs/milestone/2.6/)
> > Building of new Live CDs (for both Precise and Wheezy)
> > Proof-reading the docs
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
------------------------------------------------------------------------------
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
