Thread

The development team hit the ground running in 2011 and just released a MojoMotor update.  What’s on tap for us now?  We have two core goals for this ExpressionEngine sprint: eliminate the lingering bugs and update file management.  Expect to see the In Progress Bugs resolved with particular attention given to improving file management.  You can expect a cleaner interface and improved usability when dealing with large numbers of files.

Continue Reading

Good news, and very nice to see an update to the Forecast page too.

As a suggestion, it would be great to not have to see the “Released” items in the Forecast, or at least so long after the releases were made. If they are out the door, then “Forecast” is not applicable, and most people frequenting that page will be well aware of any releases.

Agreed- we’re hashing out how to organize the Forecast page with an eye to handling the various statuses and such.  It’ll end up awkward without some tweaks.  And yep- I’m thinking everyone will be pleased to see us knock those two tasks off!

Look forward to the next release Robin. Expression Engine has given me the tools to take on such bigger projects.

Every new project I take on requires Content Management and finally getting my hands dirty with EE has opened a whole world of possibilities not just for me but my clients.

I agree with Daniel on separating at least the “In Progress” and “Released”

Keep up the good work, I most certainly appreciate everyones tremendous efforts!

Rich

If we had some progress bar or something to help us *anticipate release* of solutions that would be nice and actually useful…or break it down into 4-5 stages/milestones.
Never the less, thanks for all the late hours spent combing the code.

Yep- we’re still shaking out the new management approaches, so definitely let us know what’s working for you and what’s not.  ‘In Progress’ in the Forecast means it’s actively being worked on now.  But some of those are bigger in scope than others, so the completion expectations aren’t really linear.  If that makes any sense.

Robin, on the forecast page I agree…some(most) of those project are really hard to define but I was suggesting for the bugs.
This way when a new release is pushed we can anticipate that the fix for our bug x will be included. I would imagine that some of those bugs are more important to those who report it - as opposed to the rest of us who just appreciate the fixes even though it doesn’t affect our project at the time. Make it more of a ‘support ticket’ style rather than a ‘bug in Progress’ I guess 😊
Just a suggestion is all.

Expect to see the In Progress Bugs resolved with particular attention given to improving file management.

How’s it going and when is EE coming out of beta (again)?

Ah, lebisol- yes, the bugs are a bit different.  One thing you can do is check the status of the bug- generally ‘Fixed for the next release’ means the bug will be fixed for the next release.  But beyond that, it is hard to tell which ones we’re actively working on and/or prioritizing.  The prioritizing in particular is an issue we’re debating on now internally.  Perhaps we can do more there with the status- both to help focus our priority list and give you folks a ‘heads up’ on what’s in the process of being coded.

And leeaston- it’s coming along.  We’re trying to really pound on things testing wise this version.  Which means- more internal bugs have been found.  On the plus side- that should mean fewer bugs making it into the release.  It’s likely we’ll have one more beta to give the new file->database changes some exposure and get some feedback.  But it is shaping up.