As you all may have seen, I’ve been really busy lately producing some very awaited new releases together with our small but powerful development team.
So, we’re close to 2010 and Entropy is about to celebrate its third birthday. It’s been a very long road, full of obstacles but hey, we’re getting closer to 1.0! 2010 will be the year of Entropy 1.0 bringing a basic set of features and ideas tossed into the wild software jungle.
What can we all expect from Entropy 1.0 and perhaps, 1.0+? Well, first of all let’s list some features that are not yet available for public consuption which I am working on, I mean, minor and major things. Of course, everybody could read my cryptic TODO file inside the Entropy git repo, but as written, it’s cryptic because it only has to fit my purposes, not yours
.
During the end of 2009, Entropy went through a lot of refactoring and speed improvement work, not yet complete though. All the core modules have been redesigned, a lot of code (around 2 millions of line changes, I’m close to the 5000th commit) has been rewritten with beauty, coolness and ZOMG in mind. Starting from the latest entropy.graph code to entropy.cache (Entropy async on-disk cacher there). Even the equo old and dusty codebase got a rewrite. The only parts missing are Sulfur (usability & speed), entropy.client and entropy.server modules, which are set for rewrite during Entropy 0.99.40 development cycle (we’re at 0.99.19 now, getting closer to the 0.99.20 milestone).
During Christmas holidays, while studying Calculus and Algebra for January exams spin, I am focusing on adding GPG support to Entropy, which is almost complete already, I need to commit some last bits to connect my newly created entropy.security.Repository class to the rest of the world
. So yeah, another cool feature is coming to town! For the paranoid part of you!
A few lines above I mentioned Sulfur, what is going to happen in 2010? Let me tell you in a few words, bring {Google Market, Apple AppStore, Nokia Ovi, You-Name-It} apps design and concept to the Linux Desktop, defining a protocol for producing $HOME resident applications and a service platform hosted @sabayon.org.
I spent 3 years to make an almost perfect rocket-science-ready package manager, now it’s time to innovate (funds apart).