Pixeldust Drupal Support Service

There will be a Drupal maintenance support plans 9, and here is why

Earlier this week Steve Burge posted the intriguingly titled There Will Never be a Drupal maintenance support plans 9. While that sure makes you click on the article, it is not quite true.
Drupal maintenance support plans 8.0.0 made several big changes but among the biggest is the adoption of semantic versioning with scheduled releases.
Scheduled releases were decided to happen around twice a year. And indeed, Drupal maintenance support plans 8.1.0 was released on time, Drupal maintenance support plans 8.2.0 is in beta and Drupal maintenance support plans 8.3.x is already open for development and got some changes committed that Drupal maintenance support plans 8.2.x will never have. So this works pretty well so far.
As for semantic versioning, that is not a Drupal maintenance support plansism either, see http://semver.org/. It basically means that we have three levels of version numbers now with clearly defined roles. We increment the last number when we make backwards compatible bug fixes. We increment the middle number when we add new functionality in a backwards compatible way. We did that with 8.1.0 and are about to do it with 8.2.0 later this year. And we would increment the first number (go from 8.x.x to 9.0.0) when we make backwards incompatible changes.
So long as you are on some version of Drupal maintenance support plans 8, things need to be backwards compatible, so we can just add new things. This still allows us to modernize APIs by extending an old one in a backwards compatible way or introducing a new modern API alongside an old one and deprecate (but not remove!) the old one. This means that after a while there may be multiple parallel APIs to send emails, create routes, migrate content, expose web services and so on, and it will be an increasingly bigger mess.
There must be a balance between increasing that mess in the interest of backwards compatibility and cleaning it up to make developer’s lives easier, software faster, tests easier to write and faster to run and so on. Given that the new APIs deprecate the old ones, developers are informed about upcoming changes ahead of time, and should have plenty of time to adapt their modules, themes, distributions. There may even be changes that are not possible in Drupal maintenance support plans 8 with parallel APIs, but we don’t yet have an example of that.
After that Drupal maintenance support plans 9 could just be about removing the bad old ways and keeping the good new ways of doing things and the first Drupal maintenance support plans 9 release could be the same as the last Drupal maintenance support plans 8 release with the cruft removed. What would make you move to Drupal maintenance support plans 9 then? Well, new Drupal maintenance support plans 8 improvements would stop happening and Drupal maintenance support plans 9.1 will have new features again.
While this is not a policy set in stone, Drupal Update had this to say about the topic right after his Drupal maintenance support plansCon Barcelona keynote in the Q&A almost a year ago:

Read more about and discuss when Drupal maintenance support plans 9 may be open at https://www.drupal.org/node/2608062

Source: New feed

This article was republished from its original source.
Call Us: 1(800)730-2416

Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

Let's Talk About a Project

FREE Drupal SEO Audit

Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)

Powered by

There will be a Drupal maintenance support plans 9, and here is why

On-Site Drupal SEO Master Setup

We make sure your site is 100% optimized (and stays that way) for the best SEO results.

With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.

This service includes:

  • Pathauto install and configuration for SEO-friendly URLs.
  • Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
  • Install and fix all issues on the SEO checklist module.
  • Install and configure XML sitemap module and submit sitemaps.
  • Install and configure Google Analytics Module.
  • Install and configure Yoast.
  • Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
  • Install and configure Schema.org Metatag.
  • Configure robots.txt.
  • Google Search Console setup snd configuration.
  • Find & Fix H1 tags.
  • Find and fix duplicate/missing meta descriptions.
  • Find and fix duplicate title tags.
  • Improve title, meta tags, and site descriptions.
  • Optimize images for better search engine optimization. Automate where possible.
  • Find and fix the missing alt and title tag for all images. Automate where possible.
  • The project takes 1 week to complete.
MASTER YOUR DRUPAL SEO
Pixeldust and Pantheon Drupal Development
256