We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 22668
    • 718 Posts
    Where to commit?
      • 22303 MODX Staff
      • 10,725 Posts
      New features always go in 1.1; bug fixes go in 1.0.x and get merged to 1.1. This is so we can release a 1.0.x patch release at any time while continuing on 1.1 feature development.
        • 16702 ☆ A M B ☆
        • 536 Posts
        Quote from: Paprikas at Apr 05, 2010, 09:12 AM

        Where to commit?

        good question smiley but maybe right question is:

        what is the plan for NEW features for next release?
        What new could have the new version...
          palma non sine pulvere
          • 22668
          • 718 Posts
          hm. When planning to work on 1.0.4? (or release)
            • 22668
            • 718 Posts
            So, this is a bug. But commited to 1.1 branch
            http://svn.modxcms.com/jira/browse/MODX-1455

            This is fixed in 1.0.3 but marked for 1.1
            http://svn.modxcms.com/jira/browse/MODX-1456

            There a bit more tickets.

            What features will be in 1.1?
            Solved all language issues (all string translated)
            New caching system
            New file manager
            New core components
            New html layout for manager
            Jquery vs Mootools
            Tokenize requests
            more...

            I think that it’s not real for this year (if we look at working speed for 1.0.1 1.0.3)
            But some of improvements we need now.
            So.. still just slowly fixing bugs, or we can implement some new in 1.0.x branch?

            For example, I think we need to refactor "System Events" and finally translate modx.

            So what do you think? Plan?
              • 22303 MODX Staff
              • 10,725 Posts
              No features should ever be released in patch releases, so no features in 1.0.x. New features will go in 1.1 and this will not be released until after Revolution 2.0.0 is final.

              IDK what is going to be in 1.1 at this point; I’m focused on Revolution to be honest, but we need to start finding a way to build consensus among contributers and other interested parties when determining what features to accept or reject and how to prioritize them. I’ll find some time later this week to review the current Evo tickets, discuss some future directions and plans for Evo (and Revo) development, and generally update everyone on the status of the entire MODx project.

              If a bug fix is committed to 1.1 and needs to go into 1.0.x, then merge it. wink
                • 22668
                • 718 Posts
                Ok.
                Where I need to discuss (create thread) new features?
                  • 25663 MODX Staff
                  • 12,272 Posts
                  Open a thread in General MODx Discussions for 1.1. Technically, 1.1 should be what we’re working on now.
                    Ryan Thrash, MODX Co-Founder
                    Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                    • 22668
                    • 718 Posts
                    Looks like 1.0.4 release inevitable?
                      • 25663 MODX Staff
                      • 12,272 Posts
                      I believe we’ll have in interim 1.0.4 release to resolve some minor installation and error warning messages. If 1.0.3 is working then it should be fine to carry on as is.
                        Ryan Thrash, MODX Co-Founder
                        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me