We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 39251
    • 53 Posts
    Woah, new forum layout!

    I have a new project I'm working on where I finally get to go back to MODX custom coding. We're not sure what we're looking at for a due date just yet, but at the very earliest, maybe March of next year, possibly more toward June. I've been working for a while on getting my machine set up so I can start submitting patches I've made (and thanks to Bob for all of the advice there). My life keeps exploding and I got distracted, but I thought this project might be a good one to use for beta testing a newer version because I can't wait to see what's coming up! (And it'll also give me the excuse to FINALLY finish setting up my machine...)

    So we're at 2.2.5 now, with 2.2.6 being released in the next few days? How stable is 2.3.0? I'd be going into it with the idea of finding and possibly even fixing bugs, so obviously I'd be expecting them, but can I assume it's far enough along (including add-on compatibility) to start developing a basic real site as opposed to a testing-only site? My normal list of standard add-ons are ones like FormIt, getResources, Login (for this particular project), Gallery (optional), Wayfinder, and TinyMCE (optional). And has anything changed drastically enough that would prevent me, worst case, from being able to copy the code for my templates, snippets, etc, back into an older version of MODX if the project needs to go live before 2.3.0 is quite ready?

    And did I see a mention somewhere of version 3.0?!
      If there's a better way to do it, I'll find it.
      • 22303 MODX Staff
      • 10,725 Posts
      Quote from: ocdcoder at Nov 12, 2012, 12:15 PM

      So we're at 2.2.5 now, with 2.2.6 being released in the next few days?
      Yes.
      Quote from: ocdcoder at Nov 12, 2012, 12:15 PM

      How stable is 2.3.0? I'd be going into it with the idea of finding and possibly even fixing bugs, so obviously I'd be expecting them, but can I assume it's far enough along (including add-on compatibility) to start developing a basic real site as opposed to a testing-only site? My normal list of standard add-ons are ones like FormIt, getResources, Login (for this particular project), Gallery (optional), Wayfinder, and TinyMCE (optional). And has anything changed drastically enough that would prevent me, worst case, from being able to copy the code for my templates, snippets, etc, back into an older version of MODX if the project needs to go live before 2.3.0 is quite ready?
      I don't believe it's stable enough at this point, but that is of course relative. However, do not bet on being able to go back to older versions, at least if you use any of the features that may be added/changed in 2.3.x

      Quote from: ocdcoder at Nov 12, 2012, 12:15 PM

      And did I see a mention somewhere of version 3.0?!
      No. It must have been a figment of your imagination. smiley
        • 39251
        • 53 Posts
        Quote from: ocdcoder at Nov 12, 2012, 12:15 PM

        I don't believe it's stable enough at this point, but that is of course relative. However, do not bet on being able to go back to older versions, at least if you use any of the features that may be added/changed in 2.3.x

        I was about to make a case for how we're curious enough to try it anyway, but looking around at the different release branches, is the 2.3 build developed to a point where you're just working out piles of bugs, or did I manage to stumble into something that's in the middle of a total rewrite? I can't seem to find much info at all on it except for the download links on your nightlies page.

        Not that I still wouldn't enjoy checking it out... Is it in active development or is it more of a side project with the focus still on the 2.2.x releases? If it's not expected to be released for another year or two, yeah, sticking with 2.2.x is probably the best idea. smiley

        To ask a slightly different way, part of my motivation is to start testing out these versions and hopefully contributing to the project. If it would be more useful to the development team to have us poking around 2.2.x versions rather than 2.3, then I definitely want to put our energy where it's most helpful.
          If there's a better way to do it, I'll find it.
          • 36457 ☆ A M B ☆
          • 100 Posts
          Quote from: opengeek at Nov 12, 2012, 01:20 PM
          Quote from: ocdcoder at Nov 12, 2012, 12:15 PM

          So we're at 2.2.5 now, with 2.2.6 being released in the next few days?
          Yes.
          Quote from: ocdcoder at Nov 12, 2012, 12:15 PM

          How stable is 2.3.0? I'd be going into it with the idea of finding and possibly even fixing bugs, so obviously I'd be expecting them, but can I assume it's far enough along (including add-on compatibility) to start developing a basic real site as opposed to a testing-only site? My normal list of standard add-ons are ones like FormIt, getResources, Login (for this particular project), Gallery (optional), Wayfinder, and TinyMCE (optional). And has anything changed drastically enough that would prevent me, worst case, from being able to copy the code for my templates, snippets, etc, back into an older version of MODX if the project needs to go live before 2.3.0 is quite ready?
          I don't believe it's stable enough at this point, but that is of course relative. However, do not bet on being able to go back to older versions, at least if you use any of the features that may be added/changed in 2.3.x

          Quote from: ocdcoder at Nov 12, 2012, 12:15 PM

          And did I see a mention somewhere of version 3.0?!
          No. It must have been a figment of your imagination. smiley

          @opengeek:
          I think I did see a mention from splittingred about 3.0: https://forums.modx.com/thread/?thread=3562&page=3
          Well, I know that'll be too long to wait, but I'm still longing for smiley
            • 18373 ☆ A M B ☆
            • 3,141 Posts
            I've started a side project on 2.3, but I guess the biggest reason to use 2.2 at this point in time would be that you may need to rewrite part of your application if it's decided to change how stuff works. It's not yet in a "fix bugs" phase, but more in a "work on new stuff" phase.
              Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

              Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
              • 22303 MODX Staff
              • 10,725 Posts
              Quote from: ocdcoder at Nov 12, 2012, 04:48 PM

              I was about to make a case for how we're curious enough to try it anyway, but looking around at the different release branches, is the 2.3 build developed to a point where you're just working out piles of bugs, or did I manage to stumble into something that's in the middle of a total rewrite? I can't seem to find much info at all on it except for the download links on your nightlies page.

              Not that I still wouldn't enjoy checking it out... Is it in active development or is it more of a side project with the focus still on the 2.2.x releases? If it's not expected to be released for another year or two, yeah, sticking with 2.2.x is probably the best idea. smiley

              To ask a slightly different way, part of my motivation is to start testing out these versions and hopefully contributing to the project. If it would be more useful to the development team to have us poking around 2.2.x versions rather than 2.3, then I definitely want to put our energy where it's most helpful.
              I guess it depends on your intentions. Are you expecting to fix bugs or wanting to contribute new features? Generally, when we start a minor release cycle, we create a release branch (e.g. release-2.2 for 2.x) where bug fixes that are rolled into patch releases are applied and then merged back into develop. The develop branch is where we integrate new features that do not break backwards compatibility; IOW it represents the next minor release. Major changes, rewrites, or features which do break backwards compatibility will be done in temporary branches and integrated with develop after the last minor release for a major release cycle is branched into it's own feature branch.

              So if you want to fix bugs, I would work with the release-2.2 branch or one of the pre-release dev builds that are produced regularly from this branch (see https://forums.modx.com/thread/80074/help-ready-revolution-2-2-6-for-release for the current example). Otherwise, if there is some compelling feature being developed for the next minor release you want to try out, go for develop.
                • 39251
                • 53 Posts
                As much as I'd love to work on new features, since my plan right now is to submit bug patches for things I find while working on a real project that has to be released at the very least before next summer, it's probably best for now I stick with 2.2.x.

                But once I get comfortable using Git (as advanced of a programmer as I am, I hate that trying to figure out how to fit it into my workflow makes me feel like I'm back at "Intro to Computing"), I would like to start getting involved with new features. If input is welcome there, I'd especially love to get involved with form customization. I use it constantly, and I patched a nasty (to me, at least) bug there a while back, which is what got me started poking around Git trying to figure out how to submit it, but I've had quite a few ideas on ways that particular function could be made so much easier to use and understand, so I'd like to hear what direction the developers on that part see it heading.
                  If there's a better way to do it, I'll find it.
                  • 39251
                  • 53 Posts
                  Quote from: opengeek at Nov 13, 2012, 09:25 AM

                  So if you want to fix bugs, I would work with the release-2.2 branch or one of the pre-release dev builds that are produced regularly from this branch (see https://forums.modx.com/thread/80074/help-ready-revolution-2-2-6-for-release for the current example). Otherwise, if there is some compelling feature being developed for the next minor release you want to try out, go for develop.

                  So we'd want the October 29 version from your link, or is there a more recent stable(ish) build?
                    If there's a better way to do it, I'll find it.
                    • 22303 MODX Staff
                    • 10,725 Posts
                    We keep the most recent build linked there. There should be a new one today or tomorrow.
                      • 39251
                      • 53 Posts
                      Quote from: opengeek at Nov 13, 2012, 11:23 AM
                      We keep the most recent build linked there. There should be a new one today or tomorrow.

                      If you notice a million refreshes on that page in your logs, that would be me and my other programmer. :-p
                        If there's a better way to do it, I'll find it.