The fourth (and probably final) 2.1 Alpha distribution is now available for download. We've gotten a decent amount of feedback from our community testers and reviewers - and have addressed almost all reported bugs as well as quite a few improvement suggestions.
If you haven't spent any time with 2.1 yet - seriously consider downloading and trying out the upgrade - as well as any and all of the new features you're looking forward too. It's a wise investment. Time spent now will help prevent frustration and hair-pulling down the road. As we get closer to stable release, we are less likely to fix non-critical bugs or implement even minor improvement suggestions - so getting your hands dirty now means you're more likely to be really happy with the release. AND, the team is much more likely to provide extra help with upgrades to folks who have participated in the release review and testing process.
Download or test out the release on the 2.1 Sandbox NOW!
NOTE: If you're already running an earlier 2.1 Alpha, you will need to install (or upgrade a 2.0.x site) from scratch - there is no upgrade path from earlier alpha versions.
Reporting Issues and Bugs
If you have questions installing, upgrading and / or using 2.1 features - or you're seeing a problem and you're not sure if it's a bug - please post your issue to the 2.1 release testing section of the community forums. Include as many specifics as possible about the issue or question. Bugs should be reported via our issue tracking system. Please select 2.1 in the ‘Affects Version’ dropdown. You will need to register as a user – this ensures that we can follow-up with you on your bug reports if necessary. Please ensure that the bug you’ve found is not reported already by checking the open issues listing.
Comments
Is there something to update at the db level ?
X+
most of us just recreate the database on a regular basis and hence ensure we get the latest schema. yes this is not a great scenario, but unfortunately its reality for now :(
lobo
Glad to see that there aren't a lot of open issues, so it sounds like you're on schedule for 9/3 Beta release. Just a question about the process, are there usually many DB changes once it reaches Beta, and if there is one is an upgrade path provided?
tc
In our past few releases, we've not made any significant db changes after beta. There were a couple of upgrade related db changes with 2.0 and we published a "fix" for some of them. I dont expect any major changes in the db now. We will provide patch files for beta db changes, but no automated upgrade path within beta releases
lobo