The next release (0.9.5?)

Anybody play with the language hack that I posted?
I was thinking that maybe this might be a mid-way step until 1.0 comes out.

Quote from: Mark at Jul 25, 2006, 08:00 PM

Paul, actually Wayfinder as well as Ditto are in SVN, its just not available to the public yet.

Sorry, do you mean that there’s a Ditto folder in SVN that I can’t see, or that there’s a Ditto subfolder within ’trunk’ that I can’t see?

I was just going off what is in the trunk, as that’s what I consider has been ’added’ to what-will-be-0.9.5.

What is in tattoo/trunk is what indeed will be included, and yes, there is a separate Ditto folder under tattoo/tattoo-assets/ditto/ in SVN, but this is just for development purposes, not distribution. The latest needs to be brought into trunk and updated in all appropriate places in the installer so it will be included in 0.9.5 installations and upgrades (and Newslisting removed). I’m trying to straighten out the ACL that is applied to our SVN repository, but there may be a week or two delay before I can make ditto, or any other snippets being managed separately under tattoo-assets available to the public, if that’s really what we want to do.

Right. Personally I don’t see a great deal of benefit in seeing work-in-progress on Ditto, as the release cycle is quite short on that anyway.

I can see now why the 0.9.2.1 security release didn’t have all the latest versions of snippets - it looks like considerable faff to check whether each snippet needs updating and if so add things into all appropriate places. I’m willing to assist in that effort if it will help.

I can see that it might not be the best time to do this yet as the snippets may change in the meantime - I’m not sure what

Update all core snippets to use in-snippet cache control

means exactly, but I understand the "Update all core snippets" part. If the new parser makes the cut, then the sample site and examples within snippets will need changing too.

... but even though there are good reasons to hold out until nearer the release, I’m sure that a lot of us would rather that it was a bit more up-to-date now. I am intending to create my own custom install soon anyway because installing 0.9.2.1 and then updating ’core’ snippets is Not Fun. If I can share the part of it which is common to everyone, by forwarding changes to someone with commit access, that would be great.

Making custom installs is actually pretty easy... just a few files in the installer folder, mostly the .sql files.

The only blocking item for an internal test build at the moment is getting the default skin working out of the box ONLY on the access control (manager login) page. Once that’s fixed, we’ll dump in the latest Wayfinder and Ditto and it’ll be ready to roll.

I’m going through the bugtracker searching for all open bugs. There’s a few I’ll fix and commit today, but I’m also assigning some to folks. Please feel free to proactively fix any outstanding bugs.

For the next test build, here’s what I think we need to do based on recent conversations around here. I’d like to see this out internally this week.

• Nuke the SlimStats manager pages, and add a basic page view counter. Can someone turn the existing SlimStats work into a modue?
• Add in Wayfinder, and update the default content to use it.
• Fix the bug in the default content template switcher where it gets stuck when you switch to the MODx Hosting template.
• Add the latest eForm, Breadcrumb and FirstChild snippets to the mix.

For the next internal beta build, I’d like to address only three things:

• Desperately need to fix the 404/redirect apache logging problems. This impacts stats which we’re removing.
• Add the recursive parser.
• As many bugfixes from the tracker as possible. Can everyone try to find three and provide fixes? Don’t close them out but mark them 100% complete and requires testing as their status if you do.

Then I say we hit a public beta. A good plan?

I’ll try and swap out NL for Ditto in the default content.

The Recursive parser should hit Beta 3 by the beginning of next week. Hopefully I should be able to get some bugs ironed out over the weekend.

I didn’t have much time to test beta2, sorry, seems like I’ll jump directly to beta3 !

I hope I have more time by then
Thanks for keeping us posted, that’s amazing development pace Raymond