Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Amiga Software News => Topic started by: Andre.Siegel on August 03, 2014, 09:45:20 AM
-
The MorphOS development team is proud to announce the public release of MorphOS 3.7, which features various bug fixes as well as other minor improvements. For an overview of the included changes, please read our release notes.
We strongly urge new users to carefully read our installation and troubleshooting guides before they attempt to install MorphOS for the first time. Existing users can upgrade via the familiar procedure but are encouraged to read the guides as well. MorphOS 3.7 is available for download in our files section.
Source: http://morphos-team.net/news
-
Cool! MorphOS runs great on my iBook and Mac mini machines.
-
Congratulations and thanks to the Morphos Team. Uber heros!
-
Simply the best, better than all the rest!
-
Great news! :cool:
Given the "Tick-Tock" model that the MorphOS Team seems to follow, this was mostly a smaller bugfix release while the next update will be a bigger "feature introducing" release (Sam460 support comes to mind?)...
Great work!
:D
-
Kudos to the developers and everyone else involved! :D
-
Didn't they just release 3.6?
-
Yeah this aint os4 ;) This update looks more like a bug fix/maintenance upgrade.
-
Yeah this aint os4 ;) This update looks more like a bug fix/maintenance upgrade.
Yes, that's the model they mostly have been following for some time now; FEATURE release - BUGFIX release, FEATURE release - BUGFIX release, and so on.
I like this model! Makes sense!
:)
-
Yes, that's the model they mostly have been following for some time now; FEATURE release - BUGFIX release, FEATURE release - BUGFIX release, and so on.
I like this model! Makes sense!
:)
If you have to do a bug fix release very shortly after a feature release,
doesn't this hint that the feature release was really not much tested?
-
Somebody's always gotta complain, lol. :roflmao:
-
They find unexpected bugs and fixes them, for free. Since when is this not a good thing?
-
If you have to do a bug fix release very shortly after a feature release,
doesn't this hint that the feature release was really not much tested?
No. It was tested quite well, but it makes a difference if some beta testers test stuff or an entire community in real live situations find things which slipped through.
So this update allows to fix urgent issues within a small timeframe, while all other new features get long term tested from adding till the next release.
Geit
-
Didn't they just release 3.6?
Yep, these guys are on FIRE at the moment, hardest working guys in the Amiga-sphere.
-
If you have to do a bug fix release very shortly after a feature release,
doesn't this hint that the feature release was really not much tested?
I guess it depends on your opinion of what amount of testing should be done before each new release, and how much of the developers time and effort you want spent on managing a large group of beta-testers, instead of spending that time on more future development.
I like the current model that the MorphOS Development Team uses, where a relatively small group of talented developers creates the new features, tests them on as many different hardware choices they have available to them, then releases a new version of MorphOS to the public. As others have said, each major release is usually followed shortly by a "bug-fix" release a few months later, as the team gets feedback from the MorphOS community.
It is a pattern that has worked out quite well and I believe that most MorphOS users are very happy with the results and the frequency of new releases of MorphOS. I know that I am extremely happy with the decisions that the MorphOS Development Team have made and the direction they have taken for the past several years. IMO, their choices always seem to make the best common sense.
-
If you have to do a bug fix release very shortly after a feature release, doesn't this hint that the feature release was really not much tested?
That is like asking if the mere release of software updates hints at developers not properly doing their job since perfect software would never need to be updated in the first place...
-
You know, they went from 2.7 to 3.0. Maybe the next one will be a major feature release 4.0.
-
Anybody who thinks it is possible to release bug free software with that many dependencies is either very badly informed or trolling. All testing can tell you is that expected bugs are not there. It can never find all bugs. There is no software house on this planet that releases 100% bug free software. It is just not possible. All you do is hope to minimize the bugs.
-
Thanks MorphOS team for your work and time development the OS!
-
If you have to do a bug fix release very shortly after a feature release,
doesn't this hint that the feature release was really not much tested?
This is one of the "problems" of release a real thing, not just vaporware like some projects.
-
Am I missing something or does this update NOT use an installer script? With past updates, I would just burn the iso and boot from it. 3.7 boots to a system but then complains that the img is too old and gives me an OK button to reboot.
Manual update of files then?
-
Am I missing something or does this update NOT use an installer script? With past updates, I would just burn the iso and boot from it. 3.7 boots to a system but then complains that the img is too old and gives me an OK button to reboot.
Manual update of files then?
You are failing to boot it from the CD if it complains about too old boot.img. It's loading old boot.img from the HD in that case.
If you're using a Mac, try booting with alt-key pressed and select the CD from the menu which is shown. Or if you were trying to boot with C key pressed, maybe connect keyboard directly to machine without hub.
-
Right you are! I do not know why I changed my normal pattern, but I did not use the C key this time around. Strange that it still attempted to boot from it but then used the 3.6 img.
All is well now! Thanks.
You are failing to boot it from the CD if it complains about too old boot.img. It's loading old boot.img from the HD in that case.
If you're using a Mac, try booting with alt-key pressed and select the CD from the menu which is shown. Or if you were trying to boot with C key pressed, maybe connect keyboard directly to machine without hub.
-
Strange that it still attempted to boot from it but then used the 3.6 img.
Yeah, if you don't force the machine itself to boot from the CD drive, normal boot procedure is taken in place. Boot.img is loaded from the HD, but then old MorphOS finds the boot device with the biggest boot priority, and a bootable CD in drive is it. And when it happens to be newer MorphOS installation CD it just doesn't work because it only accepts newer "kernel".