Long, long time ago we released Plesk 1.0 and just continued counting the versions and redevelopments in the following years. 2015 has been the year of the Plesk 12.5 launch and the upcoming release has to be Plesk 13, no doubt. Really?
The new preview has arrived!
Plesk lovers and followers are already enjoying access to a preview called Plesk 17. Wow!!!!! That must be the next generation release which is due 2020! No, it’s not. Are we now all suffering from dyscalculia? And what is Plesk Onyx?
Good news is that all Pleskians are in good health. HR is not aware of any sudden arithmetical weakness. So, what’s going on @Plesk?
A lot of exciting stuff has happened over the past few months. Plesk is becoming an independent company with a focus on growth and best support for web professionals, developers and agencies. Driving Plesk evolution to the next level or even going for a revolution…. LOTS of tasks to consider and execute against!
Product versioning is becoming Plesky
One essential element of being Plesky is to look at more or less everything we’ve done in the past and ask ourselves whether it makes sense to keep it that way, or do it differently. As marketers we had no choice but immediately look into the concept of product naming conventions. Plesk 13 fell off the cracks quite quickly as it’s considered an unlucky number in many cultures around the globe (no, we’re not superstitious at all!!!). How about tying a version release to the year in which the new version is going to launch? Great idea! Let’s go for Plesk 16 which will be released in the autumn timeframe. What a pity that 2017 is already knocking at the door…. Doesn’t matter, we’ll call it Plesk 17 and we’re done. A truly logical conclusion, isn’t it? Enthusiastically, we started to spread the word and let the information leak to the public. Plesk 17 could be found in pre-release notes, blog posts, documentation and even the previews.
Improve the experience and everybody wins
A couple of months later we realized the idea of calling the upcoming version Plesk 17 is too confusing and old-fashioned. We are in the era of continuous delivery, continuous integration, micro services, containers, cloud, PaaS, SaaS and a lot of other fancy things coming down the road. In essence, the idea of product version numbering is crap. But what to do instead? A few Pleskians locked themselves into a room and started a passionate brainstorming session. After a while, supported by a few pizzas and beers, we found the answer. At least for now……
Starting with the upcoming release Plesk will drop version numbers completely as part of the new product naming convention and only relate to a version number for internal tracking purposes. If you’re right in the middle of making your website Plesky please disregard 12.5 and focus on Plesk only. Our goal to transform Plesk into a next generation cloud platform remains a top priority to all Pleskians. We will therefore continue to launch a major release each year complemented by a couple of micro releases and the ongoing growth of our extensions catalogue throughout the year to demonstrate ongoing evolution.
We therefore proudly present (drum roll):
Plesk Onyx
Onyx is used to defend against negativity that is directed at you. Black stones have protective energies in the sense that black is the absence of light, and therefore, can be used to create invisibility. For Plesk, that means that we are making web professionals more successful and handle your WebOps needs, nearly invisibly 🙂
Onyx is also associated with the following benefits: It fortifies self-confidence and responsibility, sharpens your senses and encourages a healthy egotism – fitting in nicely with most of our partners and customers as well as creating a nice balance in all our minds.
Plesk Onyx will be an important milestone on our roadmap to provide you with the best web development experience ever whilst adding significant value to your WebOps lifecycle – no matter which stage you’re in. Plesk Onyx (download the preview here) is including exciting things such as Docker Catalog integration, Git (Github, Bitbucket, local Git, others) support, WP Toolkit 2.0, Plesk Hub (multi-server management), http/2 and many other exciting stuff!
Which gem will follow Onyx next will stay a secret for now – stay tuned and follow us on Facebook and Twitter and don’t miss any of our exciting news!
Twitter: @PleskOfficial
Facebook: facebook.com/Plesk
with
13 Comments
Where can we find a bit more information on the HUB?
coming soon – stay tuned! Best if you follow @PleskOfficial and http://www.facebook.com/plesk 🙂
When will it be LIVE already?
thank you
“Supported by a few pizzas and beers” Based on a logical chain of construction of the versions, I guess there have been implicated not only these ingredients. 😉
Guys, tell me honestly, where you take this weed?
i like its, thanks for share
Please don’t do this.
Version NUMBERS provide an easily understandable way to know where you are at.
What is the current Debian version? Lenny? Sid? Jessie? Wheezy? It’s Debian 8. Even the official releases page (https://www.debian.org/releases/) puts numbers before hard to remember names.
Same thing with Ubuntu. Even in your own documentation you support Ubuntu 12.04 and 14.04, and not “Precise Pangolin” and “Trusty Tahr”.
Why would you do this? It’s stupid.
Ahmed, I love you how pick Ubuntu of why they shouldn’t use years instead of version numbers. Ever noticed how 12.04 was released in April 2012? 14.04 in April 2014? 14.10 in October 2014? They all specify not just the year, but also the month of release.
Good plan from Plesk going to 17!
@Ian: Ahmed was not referring to the version 17, and I assume he’s fine with that name. What he’s talking about is:
“Starting with the upcoming release Plesk will drop version numbers completely as part of the new product naming convention and only relate to a version number for internal tracking purposes.”
I agree with @Ahmed. Version numbers make more sense than a catchy name.
I agree! Please don’t put version numbers away. Everytimes I do changes to a Debian system I have to search for a list containing version numbers and names to know which name is the current version. Version numbers are easy, names make it harder.
So… using a correlative version number is “confusing and old-fashioned”… uhmm ….
Let’s invent a completely unrelated and random good-sounding, meaningless word as “Onyx” trying to make it “cool” for idiots. As if buying and keeping track of software were like buying a new vacuum-cleaner.
Can you recheck the plesk migrator in Plesk 18+? Confixx to Plesk migrations taking hours. It’s faster to use the one in version 12.0.