WordPress 4.2 is out. This release brings a whole lot of new features, bug fixes and improvements. One that I’m most excited about (and thus testing right now) is the updated Press This bookmarklet for faster sharing, which now also works on the mobile (I have yet to try it though).
From Geek & Poke.
WordPress 4.1 “Dinah” is out and available for download (this blog has just been updated). This release features a new default theme – twentyfifteen, Vine embeds, plugin recommendations, and complex queries for metadata, date, and terms – this one is for developers mostly.
It’s been a year or so since the release of Fedora 20 – an unusually long break which was needed for some restructuring of the project. Finally it’s over and Fedora 21, bright and shiny, is hitting the digital shelves right about now. Go get it!
A brand new and shiny version of the best CMS ever – WordPress – has been released. Version 3.9, code-named “Smith” brings quite a few noticeable improvements. Mostly, these are around the post editor – a new version of TinyMCE, previews for galleries and playlists for audio and video, in-editor image resize and drag-n-drop file uploads. Also, widget settings were much improved, especially with the live preview before save. Watch the quick release video and read more here.
Fedora community celebrates the release of Fedora 20 today. It is an anniversary release, marking 10 years since the birth of the project. Yes, that’s two releases per year, all according to the six month release cycle. Here, I’d like to do a little side tour.
Not many people understand what a Linux distribution is, much fewer comprehend how much work goes into making one. I have been following Fedora closely since it was born, and tried my hand at building a Red Hat based Linux distribution myself. Of course, it’s been years since, and many things got simpler and easier, but the overall effort, I’m sure, is still pretty incredible.
Let me break it down for you a bit. In it’s simplest form, a Linux distribution is just a collection of software. Pretty much anybody can take a Linux kernel, bash shell with a few tools, and throw together the simplest of all distributions. But Fedora is not that. Fedora is much larger. It consists of thousands of packages. Each package is not just thrown in, it is tested, packaged and maintained, to make sure upstream patches and updates are integrated properly, and all bug reports travel back upstream. All of these packages are tested both separately and together to make sure they work with each other. Often, custom patches have to be developed and applied. All of these are supported on multiple hardware architectures, in a numerous variety of scenarios.
Just that alone is a monstrous amount of work. But that’s not all of it. Fedora maintains a huge infrastructure to make sure tests can be executed, updates could be distributed, and community members can talk to each other.
Tonnes of help is provided to anyone in need. This includes wiki pages, mailing lists, IRC chats, etc. Help covers not only newcomers to Fedora distribution, but also seasoned users, system administrators, testers, and also marketing promoters. A lot of this has been translated into dozens of languages and distributed geographically.
And all of it is an ongoing process. Just think about it – today the new version is making its way around the world, and if you run “yum update” tomorrow, you’ll definitely find a few packages with freshly baked fixes and improvements.
Thousands and thousands of people are involved in this. Some write code, some administrate systems, some negotiate with upstream providers, some test software, some write documentation, some translate, some organize shows and conferences, some train people and answer silly questions. And in all of this havoc and madness, somehow, an original release cycle of once every six month is still being kept. Yes, true, an occasional schedule slip of a week or two occurs, but overall, it has been a solid two releases per year. Every year. For the last 10 years.
A lot of this is hard work. A lot of it is fun. But there are also sad chapters in this history. Fedora 20 is dedicated to Seth Vidal, who was tragically killed in a hit-and-run accident while he was riding his bicycle earlier this year.
On July 8, the Fedora Project lost Seth Vidal, a dedicated, tireless, and brilliant contributor. Seth was a lead developer of Yum and the Fedora update repository system. He worked to ensure that the technical and community infrastructure of Fedora worked well and consistently for users and contributors around the world. Seth touched the lives of hundreds of Fedora contributors directly and millions of others indirectly by improving the experience of using and updating Fedora.
The Fedora Project dedicates the Fedora 20 release to Seth and asks that you join us in remembering his generous spirit and incredible work that helped make Fedora what it is today. We miss you, Seth.
There are ups and downs, victories and losses. There is no other way in the project of this magnitude, in a crowd of people so huge, and in such a dynamic environment, all lasting for so long.
With all that in mind now, I suggest you give Fedora 20 a try, if you are not a Fedora user. If you are – happy upgrading! And let’s not forget to say a huge thank you to everyone who made this release possible. Good job, guys!
P.S.: If you are interested in the actual changes of this release – please have a look at the changeset document.
The bright new and shiny version – WordPress 3.8 – is available for download. As I mentioned previously, the biggest change is the reworked administration area that now scales well to smaller screens, like those of smartphones and tablets. It’s far from perfect, but at least it works now. I’m sure there will be more changes and improvements in the upcoming versions.
But that’s of course not the only change. The administration area has changed a lot – more contrast, different icons, improved typography, and now even with color schemes. Also, theme preview and management got changed quite a bit. With the new theme management interface, the screenshots are larger, which, unfortunately, makes them blur out a bit until theme developers will update with higher resolution versions.
By now you know that I can’t praise GitHub enough. It is one of the best tools for developers ever. Seriously. It’s up there with git itself, and even Vim. If you aren’t using it yet, stop whatever it is you are doing and rush there. Now. I’m not kidding.
So, anyways. Today GitHub added another awesome feature – Releases. These are basically git tags on steroids.
I’ve been already playing around with the idea of releases for our work projects. See, for example, phing-version branch of my sandbox repository. It worked, but it’s not perfect. With GitHub Releases however I’ll have pretty much everything I need – release notes, easy full diff reviews, binary attachments, etc.
A little side note for binary attachments: I mostly work with PHP, which doesn’t really need binary attachments. But I am a part of other, “heavier” projects, developed in C++ for example. This feature will come in handy. Also, as far as PHP goes, I was playing with the idea of using RPM and YUM as a mechanism for managing installation, upgrade, and downgrade process.
Back to GitHub Releases now. This is an excellent example of why you should use GitHub instead of setting up your own environment. You’ll waste more time and money. It will be ugly. And you’ll have to maintain it. With GitHub you’ll focus on your actual development work and will get excited every now and then when they add a new feature.
There’s been a stream of good news from the CakePHP headquarters recently. If you are as slow as me on catching up with these things, here is a quick summary.
- CakePHP 2.1.4 has been release, and that’ll be the last release for the 2.1 branch. It’s time to move on.
- CakePHP 2.2 stable has been released, and that’s what you should be using for your projects.
- CakePHP 3.0 has been mentioned, so if you are interested in contributing early, here is your chance.
CakePHP 3.0 will take a few month to develop. Mainly, the work is focused around the following:
- Drop support for PHP 5.2.
- Add and improve support of PHP 5.4+.
- Reorganized CakePHP classes to use namespaces to avoid collisions with other libraries and classes.
- Improve bootstrapping for better control by developers.
- Rewrite the model layer to support more drivers, object mapping, richer API, etc.
- Rewrite the routing to work faster and be more flexible.
Overall, it looks like some really healthy activity in CakePHP project.