[Nexus 6 Android Development] chairshot215:
OK so my solution to a history and odd and seemingly jumbled release version numbers is obviously to come up with something new to keep in line with the odd and seemingly jumbled release version number history. Not to mention a bad attempt at being clever in the process.

In the past the cause was that I continued with the numbering of builds that for some reason or other never came out of testing and had not been actual releases but used the next line of release numbers anyway for my own way of tracking things across not only posted releases but also builds from a variety of other branches for staging and testing. Because I had done this actual posted releases seemed to jump numbers or looking something like #.#.#. For the most part if I had 10 changes staged to test then after some days of testing the number of changes would slowly drop so may have started with a build with 10 changes I over a few days of testing may have done some weeding and only 3 changes would end up in a posted build so if say the last posted release was "r1" I would call my first build for testing the 10 changes "r1.5". Then it may have taken 3 more builds to decide on not including 7 of the 10 changes so would end up with something that looked like "r1.5.3" in the ens when posting if any of this makes any sense. Really just trying to put some defence into the method to the madness thing I am going with even though its probably more not recognising my laziness and coming up with excuses for the confusing numbering for build numbers that have been posted.

If you think what I wrote above is confusing just wait for the description of the new numbering, owe its good and a bad attempt at being clever with the Starship thing. Now that the Stock/AOSP Kernel is about to hit number 10 I have changed the Class numbering combining the release number. Now instead of M-Class, M of curse for Marshmallow the new Class is "SMRX#" S for Shamu, M for Marshmallow, R for release, X keeping with the last release number using the old numbering system that would have been numbered 10, and # for yup the actual release number. I said it would be good and confusing and with other famous Starships like say the Enterprise using Class names and numbers like NX17 or whatever is also a failed attempt at being clever, YUP! Making it even worse is the CM Kernel is starting the new system as "CMSX1". Not going to explain but if wanted could use the above abbreviation explanations to figure it out. Only this time am going to fight being lazy but updating both Kernels at the same time and keeping the release number the same for both even though the other abbreviations may differ.

All and all I made the explanation rant above not just for some justification and an explanation but to dig up the Kernel for the new releases. Its funny how it works as I may be on page 3 when posting a new release with not so much activity. From there I may post something like a reply after posting the new links and will spend some time on page one and see a spike in downloads. Shortly after someone may post that they like or have had no problems with the Kernel. Again will jump back to page one and see another download spike. Otherwise the thread bounces from page 1 down to 3 then up again. Thinking about it I guess I should be somewhat thankful the thread does not spend its life on page one as it would probably be because I am getting posts about complaints or bugs. Thankfully to those who give feedback it is for the most part always positive. I don’t see much asking for help or complaints about bugs and I would rather see few posts from happy campers than a barrage of not so happy users. So again other than the first few releases having the encryption mix-up, still sorry about that but otherwise thankful to see posts from people who are happy with how things are turning out. Always nice to bring just a bit of sunshine into someone life probably halfway on the other side of the country possibly even planet even if the number is small.

Otherwise is late have some energy that needs to be burnt and thought I would give an explanation, a little thanks even though I am now so jinxed and pop up the view ability of the thread after updating the Kernels.

In the immortal words of Sean Price, P!