Website has been further simplified and should be easier to use and navigate.

Considering the sheer number of distributions out there I have decided that there is little reason to be completely generalized.
From this point forward I will be spending time and effort on giving the system a specific look and feel.
This means that only certain applications will be supported.
Doing this will also simplify management.
Once there is a package management system in place, other flavors of kevux can be supported in the same way ubuntu has different flavors.

After experimenting with uClibc-nptl branch I discovered that it is overall more stable than any of their stable releases.
I have now switched to the uClibc-nptl branch.
A large number of random crashes vanished and even some performance improvements have been noticed.
However, there have been regressions (though very few).
With such wonderful overall improvements, I decided to make an early release.
I will be releasing version 0.9.0 very soon.

Happy New Years.
This year will begin with the release of Turtle Kevux 0.8.12 (at long last).
The files will be uploaded shortly, but they will take a few hours and so by next year the files will be ready.

I have recently been pondering about a common issue that seems to affect many open source projects.
The issue is one of versioning, releases, and communication.
There are simply too many projects out there that have rarely had normal releases.
For example, grub never got to 1.0 and a 2.0 was being worked on which also never happened.
The community has been using a grub 0.9.whatever for so long that many consider 0.9.whatever a stable version.
The same goes for the grub 1.9.whatever.

I see this problem happening to my projects as well, so I intend to change that.
I have fallen behind my development of the Featureless Linux Library on numerous occasions.
I am currently updating my FLL code and will include this code in my next Turtle Kevux Distribution release.
The versioning system of the Featureless Linux Library has seemingly scared away potential users so that will also change.
The overall goals will remain the same, but the major versions will happen more often.
This means a FLL-1.0 is much more likely to appear in the next 6 months.
This versioning system will be drafted following my next Turtle Kevux release.

These plan changes have pushed my Turtle Kevux release slightly behind schedule.
I currently have a decently stable release all but ready to go out the door that has only a small number of observed bugs and regressions.
I intend to attempt to fix these bugs, but will not let them prevent me from making a release.
When I finish writing my FLL code, and the small number of programs that will utilize the library, I intend to release the Turtle Kevux 0.8.12.
Along with this I will attempt to provide an OLPC optimized version.

After Turtle Kevux 0.8.12 is released, I will begin working on Turtle Kevux 0.9.0.
Turtle Kevux 0.9.0 should be a very short release whose entire focus is on adding a package manager support.
Shortly following this, hopefully no later than a 0.9.2 release, I will release Turtle Kevux 1.0.0.

I have to admit that the Ubuntu distribution release numbering system is a good idea and so I shall incorporate their release versioning concept into my own.
When a distribution is released as a stable version (aka: 1.0.0), I will then append two version numbers that represent the year and the month of the release.
This means that a stable Turtle Kevux release that happens in March of 2014 will be: Turtle Kevux 1.0.0 14.03. (Major.Minor.Micro Year.Month)

The release early and release often is a good concept and I will attempt to stay as close to the idea as I can.
To this end, I am releasing all of my website and documentation changes now even though the Turtle Kevux release has not been finalized.
Once I finish my documentation and make my release, this website and documentation will be updated again.

The kevux website has been updated to a more simplified and static design.
The reason behind this is due to how busy I am and how little time I have to maintaining the website.
This should be an easier and more secure website to maintain.