Is MODX3 On Its Way ?

Quite some time back the mention of Evo & Revo being made redundant as soon as MODX3 comes along was made:

In 2013 we will release MODX 3.0. Note the distinct lack of any word between “MODX” and the version number. The MODX 3 release will also mark the official deprecation of both Evo and Revo, bringing the confusion as to what’s the official recommendation to a close.

Source:Clarity, Focus & Simplicity

So my question: Is MODX3 on its way ?

Ive been reading the forums a lot lately and still see extensive talk about Evo & Revo, but almost no mentions of MODX3. Not from the community and nothing from MODX LLC.

A discussion about the 2014 conference has just opened and I read this:
Quote from: sottwell at Nov 11, 2013, 12:33 PM

Of course, by then 2.3 should be out, so something more interesting may come up.

I presume the quote refers to Revo 2.3, which indicates to me that MODX3 isn't or is possibly not on the books to be around by then.

Isn't it time to say what's going on in the future, possibly some information about if and when MODX3 is going to show its head. [ed. note: iusemodx last edited this post 12 years, 11 months ago.]

MODX 3 has been delayed. There is no argument there. 2.3 is nearing a beta release and we are always recruiting contributors to help test it out and provide feedback.
While there may be a 2.4 release, you can expect to see much more discussion and active development on 3.0 once 2.3 is released.

No MODX LLC members willing to comment on this ?

JP works full time for MODX LLC

The team has never been great at estimating deadlines so feel free to ignore the note about 2013. MODX3 is of course still on the table but that needs a lot of work to get off the ground and tobuild together with the community, so as with all good things that will take time. As 2.3 gets released, a lot more LLC attention will go to 3.0 and we should see some structure for the community to help build it by then.

The other thing is that, as both Ryan and Mark said at MODXpo 2013, the time to get to the next milestone depends a lot on community contributions. Once the going forward development cycle is more or less firm, and I have time to get acquainted with github, etc., I plan on starting to contribute as well.

Regards,
Tom

The team has never been great at estimating deadlines

Neither am I. There are just too many variables in life for me to be able to say how long it'll take for something to get done. Especially when other factors fail to materialize, or fail to meet expectations.

Besides, I'm in no great hurry for 3, I still haven't got 2 under control yet! Maybe another six months... did I say that I'm really bad at guesstimating time deadlines?

By the way, just got myself a copy of the latest A Book Apart e-book, Sass for Web Designers. At $9 for the e-books, these are really good bargains.

I was a reluctant believer in Sass. I write stylesheets by hand! I don’t need help! And I certainly don’t want to add extra complexity to my workflow. Go away!

My sentiments exactly!

Sass is to CSS as MODX Chunks are to HTML. Both are completely backwards compatible. Raw CSS is valid Sass just as raw HTML is valid Chunk.

After reading Dan Cederholm's first chapter, I am already understanding that much better. This will certainly get me over one of the blocks in my way of contributing more to MODx.

Probably the second-biggest one (after getting a firm grip on git and github) still remains, though... tests. Many years ago when I was a larval programmer, my library got in a new book, something about mathematically provable programming. At that time it went right over my head, and I've had a phobia ever since. So I have to get a grip on myself and figure out what these "unit test" thingies are all about.

I think for some reason the term 'unit tests' scares people. I'm not awfully familiar with them either but keep in mind, this is a unit test


As simple or as complex as they need to be.