0.9.1 release plans

A few things that will make a big impact with 0.9.1 release:

1) Primarily bugfixes and tweaks. If we can get snippets/chunks merged, even better (a preview of things to come). nope... not now Mostly though, let’s test and knock of as many bug reports as possible and get them committed ASAP. I think everyone has SVN and a local branch working now. Quite a bit has been done here, too. Please try to keep bug reports updated with progress and status.

2) Release the "Future of MODx" explanation in the announcements forum including flowcharts, etc. Release any current docs in any state or form in the developer section of the site.

3) A snippet/file repository; we’re SOOOO close with the file cabinet... just need the ability to record the actual snippet authors, and merge file upload capabilities into UserComments. This would enable osCommerce style file repositories.

4) Integration with our forums... the SMF plug-in. Not only would this be incredibly useful for us, but it would also be a great example of what so many users have been clamoring for. Releasing the Gallery 2 stuff would be great as well. Next up we should try to knock out IPB and an e-commerce module.

5) Upgrade Flyspray to latest 0.9.8... with a plug-in of course. done but no plugins (or doing one now)

Any other thoughts? This would be great stuff to shoot for by end of next week I think.

Been a busy day of bug squishing and prioritizing of stuff (bug related). I squished as many of them as I’m capable of doing and closed others that tested to not really be bugs after all. Jason solved some great ones and updated flyspray (RSS feeds are great!). If we can hit any more bugs (many originally due in 0.9.5 have been completed) or the feature requests slotted for 0.9.1 that would be great as well.

If I could, I’d like to assign a few bugs to folks that really should be addressed for 0.9.1:

Jason: 81, 85 (I think we’ve nailed 81 with a syntax change)
Adam: 101, 102, 111
Jeff: 72, 75, 87
Raymond: 100, 104 (thanks Jeff!)
Ryan: 91 (but is the reskin/safari fixes worth it... a lot of work given that the manager rewrite is effectively under way) nope... not now... 0.9.5 focused effort

More research needed: 67 waiting on susan’s feedback and moving to 0.9.5 since there’s a workaround


I personally think that what would be the biggest boon to the 0.9.1 release effort would be the SMF forum user acounts synched to a webuser login. Raymond has done a bunch of work on an SMF plugin, but it’s still not quite there yet. Likewise, if someone could get the file uploading part of FileCabinet and graft it into UserComments that’d be very cool as well.

Code-change wise, I would like to see four things done for 0.9.1:

• stats replaced by slimstats and existing slow implementation removed (and an option to turn it off entirely)
• The warnings and Errors in the existing parser squished. I think Remon (R.S.) has done most of this already.
• as many of the general cleanups as possible from the spreadsheet I put together done on the parser (I’ve already started killing off some empty/dead stuff, for example.)
• reorganize the manager menus to match the proposed revisions as much as possible.

Jeff and Adam will need to get any work done in their branch (or locally) committed in: QE and FCK were/will be updated. After that, I think it’s time for a release build for internal testing...

Remaining scheduled 0.9.1 bugs:

• 14 -- default tree sort order... do you guys agree with this? deferred to 0.9.5
• 75 -- broken floater widget
• 85 -- "&" in TVs not converting to &
• 87 -- inaccurate error message  when using meta tags feature
• 118 -- transition QE to use manager language files (Adam)

Jason is tacklng all the suppressed error warnings in the parser and cleaning that up a bit... very nice! crushed 100 of them yesterday! (but more to go... )

There are several default snippets that are causing errror warnings including ListIndexer using a $_GET call (?) and ListRelated with an undefined index. Some others have been cleaned up, but this is where they’re falling so far.

That really leaves the two things I’d like to see done asap are the SMF plugin and the File repository that supports file attachments via a modified User Comments borrowing from the File Cabinet snippet. Any takers?

And a couple more I glanced over:

• Make sure manager login page looses the Etomite reference.
• Loose all instances of original Eto spyware and other such silliness including add notice and all instances of phone home crap... browser sniffing too if possible.

Here is the zip file that contains 3 files that I found has "Etomite" in the code. There are files that have many Etomite but for reference to author or credit to Etomite. Since I am not sure it should be remove so I leave them out.

Quote from: rthrash at Nov 17, 2005, 06:47 PM

• Make sure manager login page looses the Etomite reference.

I don’t think we should loose the Etomite warning as long as MODx uses the exiting layout. We can remove the Eto info once the look and feel has changed.

• ...browser sniffing too if possible.

Personally I don’t think we should remove this because it will be needed in the future.

I think we *should* move the config file to the asssets directory... I just deleted mine while testing as it’s so easy to do when upgrading.

I do wish that "summary" and "introtext" could be dealt with! I can never remember the one if I remember the other! It’s "summary" on the doc creation form, and "introtext" in the database...drives me nuts! It would simplify life a great deal (at least for me) if the text in the form more closely followed the field names used in the database.

That is such a clear and logical request I can’t say "no".

Quote from: rthrash at Nov 18, 2005, 04:46 PM

I think we *should* move the config file to the asssets directory... I just deleted mine while testing as it’s so easy to do when upgrading.

I think we should have a "users" directory where we check for configs/images/files whatever before we check in the default assets dir. And the users dir should be untouched during upgrades.