Since being acquired by Autodesk, eagle has never had a stable version available

[S0me0neUQ5N5]

what do you think?Stable priority, it is not blindly speed up the progress

[matt.berggren]

Thanks for the post however you provide no details. What issues have you had so we can resolve them? Posts like these don’t assist us in identifying issues and fixing them which, we have done MANY times since Autodesk’s acquisition. Do you have a specific issue? Do you have something we can verify and test against? If you can supply details, we have fixed nearly every issue we have introduced within one or two “point-point” releases. Unless I have something I’m missing?

Cheers,

Matt - Autodesk.

[Anonymous]

It§s simple, he asks for the differentiation between a "STABLE VERSION" vs the "DEVELOPMENTAL VERSION"

A stable version certainly doesn't have an update 24 hours after releasing said stable version.

The user said he is tired of constantly having to manually update the software, etc.

[one-of-the-robs]

A common model in the open source community (who are more accustomed to rapid release cycles than others) would be to maintain the last semi-major version tree as the "stable", getting only bug fixes, while the current "bleeding edge" gets features. So for the current state of Eagle, you would provide both of:

     v8.4.x       is the stable, bug fixes only path

     v8.5.y       has all the latest features

Then at some point you would decide that 8.5 is now feature-stable, create 8.6.0 for new feature stuff and obsolete 8.4 because 8.5 has become stable.

As a minor variation of that, the Linux kernel used to run a scheme where the middle number was even if stable and odd if development. Hence v2.24.x was a stable version, v2.25.y was development, and when that series got stabilised it became v2.26.0 making v2.27.x the new development branch.

This approach allows your users to choose (gosh, what radical concept) whether they want to play with the latest features or get on with work on a stable platform.

[mats.engstrom]

I have to agree about the "crashiness". The last few releases have been crashing quite a lot. Mostly after a lengthy editing session when exiting the app or when closing the schematic/board window with the (X) in the window chrome. Once or twice when actually routing the board....

[Anonymous]

I have to say that while I appreciate the rate of feature development Eagle is showing these days, it does seem to have come at a cost of extra bugs.

I have experienced at least two bugs related to DRC in the past 6 months, and worse multiple instances of hard crashing. They do seem to get fixed, but then the next version introduces new issues. In pre-Autodesk days I saw very few bugs in a decade of use.

Personally I would also appreciate seeing a more stable version available separately to the bleeding edge version.

I do also wonder if the testing setup the developers use should catch more of this kind of thing.

[mats.engstrom]

Two hard crashes even before lunch today .  I do hit save every 5 minutes so I don't lose that much, but it's rather annoying. I guess (or at least hope) that you guys get the crash report data that is automatically sent to Apple - or do you want them uploaded to the forum?

With all the new time-saving features like P&S and the toggle layer with <space> while routing I still feel that the pros outweighs the cons, but the frequency of crashes are making the cons side rapidly approaching the pros. ;-(

[jorge_garcia]

Hi @mats.engstrom,

I think we need to explore this a bit more. If you want go ahead and post the crash report and if you can post a screencast of the crash happening that may help.

Let me ask, are you saving your files to a network drive or some sort of other setup?

Let me know if there's anything else I can do for you.

Best Regards,

[mats.engstrom]

Hi @jorge_garcia - No, it's just a regular local folder on the macbook, so nothing special there.  The drive is kinda full but still got 16GB space left, so that should hopefully not be a problem.  I'm still running on 10.11.6 (El Capitan) but I guess that's quite common.

I'd be happy to supply logs and recordings, butI must admit that after five years of being a mac user I don't know how to make a screen recording.  Is there any nice software I can run in the background that keeps a recording of the last 5 minutes or so - just like those videorecorders for cars? Or else the recording will just keep on filling up all available disk space... 

[jorge_garcia]

Hi @mats.engstrom,

Thanks for the follow up. The few times I've needed to record on a Mac I've used Quicktime.

There's something I'd like you to try to see if the crashes go away. Go to options > Backups/File Locking. Set the backups interval to something long like 20mins.

Does the frequency of crashes change? It might be something related to the backup system.

Let me know if there's anything else I can do for you.

Best Regards,

[mats.engstrom]

I'll change the interval to 20 minutes and see whats happening during the next few days. I'll also try to remember to make screen recordings top capture what I'm  doing...  Thanks.