These days, there are
lots of open source projects that are working together and learning
from each other. At the Joomla World Conference, the Joomla community
very happily welcomes to Matt Mullenwag and Andrew Nacin, where Matt
served a keynote address. When it comes to talk about this event, it
has been opened up with some interesting cross-platform discussions
on development.
Lots of people at
WordCamp Miami are welcoming Joomla users as well as developers in
order to attend their event next year to foster more shared
experiences. However, Drupal leaders are also interested in learning
from other projects’ approach to development.
The founder and project
lead of Drupal “Dries Buytaert” declared that the project will be
moved towards more agile development method to serve small changes
quickly. Buytaert websites have lots of problems with Drupal core
development – “not innovating fast
enough, insufficient commercial incentive to contribute, contributor
burnout, and unpredictable release cycles”.
Any
type of open source project will always have its own dynamic barriers
to conquer. However, at the time of investigating how Drupal’s
current development method can be enhanced, the entire team started
comparing and contrasted release strategies employed by other similar
projects such as FireFox, WordPress, PHP, Joomla, Symfony, Typo3,
Ubuntu and more. All the data, which has been collected, shows that
WordPress trends to iterate more quickly compare to others, but it
only providing security support for the current release. But, it only
provides security support for the current release.
Mainly,
the difference is that WordPress tries very hard to never break
backwards compatibility. There are some other projects as well that
surveyed longer waits between important releases with less importance
on backwards compatibility but still maintain security support, or
what they term LTS, for older releases. To manage the Druapl 8
unveils cycle, the proposal of Buytaert takes the wonderful ideas
from these projects and applies them in a way that it will work for
the Drupal community.
The news are coming that
it will adopt a new and important strategy of preserving backyards
compatibility that mainly aims for excellent release every six months
that is much like to the project surveyed. Drupal will offer a single
LTS release as the final minor release, similar to Joomla. Drupal is
offering a single LTS release as the final minor release that is
similar to Joomla and support LTS release until two additional ones
have been launched. The planned changes are completed best and it
will be also interesting to watch as how it releases cycle changes
things for Drupal.
Recently,
Drupal also launched Drupal cycle improvements by encouraging
WordPress as well as by other platforms. If you want to get more
information on the cycle improvements, you can continue reading this
blog and make yourself familiar with the changes.
Visit Open Source Portfolio link click here.
Visit Open Source Portfolio link click here.
1 comments:
Its really Informative post about Drupal, I always want to learn learn more and more about CMS and I am follow your blog.
Thanks,
Open Source Development