The Joomla!® Community Magazine

Issue 2011 August >

The Joomla Version Strategy Explained

Written by Community Videos | Monday, 01 August 2011 00:00 | Published in 2011 August

Related Video

Since the Joomla development cycle has changed to reflect industry best practices, the naming convention of releases has also changed. Ron Severdia breaks it down for us.

Social sharing is caring ;)

Leave a comment

Make sure you enter the (*) required information where indicated.

[b] [i] [u] [s] [url] [quote] [code] [img]   

Comments (5)

  • avatar
    • 0
    • 0
    Nick Savov

    Nice video, even better explanation! :)

  • avatar
    • 0
    • 0
    Marni Derr

    When explained in this manner, I think the new release cycle numbering could make it easier on everyone.

  • avatar
    • 0
    • 0
    Alex Stylianos

    Instead of that, we don't you use bigger font sizes for the LTS versions, and tiny little ones for the STS ones? It would make much better sense.

    Overall, I think you have lost your touch with reality. There are so many things I see as funny, but as a Joomla! contributor I think I have to try to wake you up. I would like to do that in the people.joomla.org page for this discussion, but I guess it is open only for some people.

    Why don't you just use the entire major number series as an LTS? Are you going to have such dramatic changes from say 3.0 to 3.1 that makes you support one and not the other? Even if you do, why don't you decide to keep the major changes for a new major version. After all, the word "major version" is spoken this way because it reflects major changes. Minor version is called minor because it reflects minor changes.

    I see you definitely want to copy the Ubuntu version model. If you copy, then make it a good copy. Ubuntu version numbers are not major.minor numbers. They are year.month numbers. Do that. It would make much more sense.

    And another question. If there are critical security problems in say 3.2, won't you be forced to relase a 3.3? Merphy's law is not a fantasy, so what if you will be forced to release three more versions like this one. What will you do then? Jump 3.5 because it will be reserved for LTS?

    In my mind it would be so easy to have a v2.0 which will be supported as an LTS. I wouldn't mind time based MINOR releases, but why not use the notion of major version for major support? #justsaying

  • avatar
    • 0
    • 0
    N2H

    UNACCEPTABLE and UNBELIEVABLE!
    Alex Stylianos is RIGHT
    The Major number should be the number that define the long term version!!!

    So with your Version Strategy, the manifest file of Extension will be :

    2.4.x" type="extension" client="site">
    or


    Instead of

    tension version="3.x" type="extension" client="site"

    RIDICULE!

  • avatar
    • 0
    • 0
    Peter van Westen

    Discussion on this going on here:
    http://groups.google.com/group/joomla-dev-cms/browse_thread/thread/ 1c8daac86fcef98a

Powered by Compojoom comment
English

Join our community!

Recommend us on Google+