As we get closer to the end of the "Ascot" project we are starting to think about the beta program. As normal we are running a closed beta program, though this time around there will not be a public beta. For our engineers it's an interesting time, because they are winding down from the excitement of writing all the new code, and they get into the realities of fixing the stuff they just wrote - but the beta program certainly signals the home stretch.
On the closed beta we invite a number of customers to work closely with us to ensure that we are meeting the mark on a number of criteria - we look at feature usability, scalability, stability, quality and so on.
So, if you are interested in participating then please go to this blog entry and make sure that you are up to fulfilling the requirements and then complete the survey listed on that page. We always get way, way more applications than places on the program so, sadly, we can't accept you all. When I evaluate the survey responses I generally try to get a good cross section of industries, geographies, installation types and customer sizes. I also select customers who will be able to join the calls and participate on the forums.
To finish off I'll tell you why I called the project "Ascot". Most Americans wonder why I named it after a tie, and then wonder if the next release is named after some other obscure item of clothing. Those of you that know me know that I am British, so I am naming the projects with a British theme. Ascot is a town in England, just outside of Windsor (where the Royal Castle is). It's also close to Bracknell where Novell's UK headquarters are. Ascot is famous for the racecourse and the annual Royal Ascot races. So, no - I have not named the next release Cummerbund. It's "Windermere" which is the largest lake in England. We also have "Buxton" (a town close to where I grew up) and "Cardiff" projects in the hopper.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.