Changes between Version 26 and Version 27 of R1/Alpha4/ReleaseNotes
- Timestamp:
- Nov 14, 2012, 10:49:09 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
R1/Alpha4/ReleaseNotes
v26 v27 1 = HAIKU R1 Alpha 4 Release Notes =1 = HAIKU R1 Alpha 4.1 Release Notes = 2 2 3 These are the release notes for HAIKU R1 Alpha 4 ,our fourth official release. For this fourth alpha release, we strove to provide an improved version of Haiku that is more stable, introduces more features for both the end-user and developer, and has a greater chance of properly booting on more hardware.3 These are the release notes for HAIKU R1 Alpha 4.1, a critical bugfix update for our fourth official release. For this fourth alpha release, we strove to provide an improved version of Haiku that is more stable, introduces more features for both the end-user and developer, and has a greater chance of properly booting on more hardware. 4 4 5 5 We have tried hard to make this release as good as possible. Still there are a few known issues and missing features, some of them collected below. Please keep in mind that this is alpha software, which means it is not yet feature complete and still contains known and unknown bugs. While we are mostly confident in the stability of this release, we do not provide any assurances against data loss. 6 6 7 Another goal that has driven the release of the Alpha 4 was to provide current and future Haiku developers an updated and (mostly) stable operating system to work on their software projects. Therefore we have included the basic build tools. This release of Haiku is capable of building and running binaries using either GCC 2 or GCC 4. The use of GCC 4 is discouraged however if not absolutely necessary, as no API compatibility is guaranteed with future versions of Haiku. 7 Another goal that has driven the release of the Alpha 4.1 was to provide current and future Haiku developers an updated and (mostly) stable operating system to work on their software projects. Therefore we have included the basic build tools. This release of Haiku is capable of building and running binaries using either GCC 2 or GCC 4. The use of GCC 4 is discouraged however if not absolutely necessary, as no API compatibility is guaranteed with future versions of Haiku. 8 9 Due to the immediate testing efforts of Release 1 Alpha 4, we are able to release this critical bugfix version. The specific bugs fixed in this point release are http://dev.haiku-os.org/ticket/8684 and http://dev.haiku-os.org/ticket/9128. Both of those issues prevented Haiku from booting properly on several hardware configurations. 10 11 Thank you all who reported the issues on the bug tracker and we appreciate your understanding. 8 12 9 13 == System Requirements == … … 53 57 LiveCD and first boot performance: After an initial installation or a boot into LiveCD mode, some background tasks are executed to finish the installation setup. This is known to degrade performance. On hard disk installs this usually is not a problem as the tasks are done quickly. In LiveCD mode the performance hit is more prominently visible due to the usually bad seek performance on CDs. Since the CD is read-only, this setup takes place on every start of the LiveCD. On writable media it will only be done once, so further boots shouldn't experience the same delays. 54 58 55 On single core machines, booting into safe mode on the first boot (e.g. every boot of a LiveCD) may result in Deskbar ending up in a dead lock. This is believed to be caused by NetworkStatus attempting to install itself in Deskbar while net_server is not running.56 57 59 Font rendering, while improved due to the expired font hinting patent, is still not optimal. Due to the uncertain situation about patents, the official release has disabled code, which is known to be patented. This sadly includes the subpixel code used by FreeType. Once the situation is better understood and a decision has been made, subpixel font rendering may get re-enabled for official releases. 58 60