BOA-2.0.4 release - update

This weekend. We have fixed all release blockers.

Looking forward to it.

And Happy to see your tweet ( http://bit.ly/WEOKYg ) about BOA already blocking access to install.php and thereby already being safe with ref to exposure that 7.16 is fixing.

Did you know that none of your #Drupal 7 sites are affected by recent security issue? #BOA system denies access to /install.php by default.

Release has been delayed a bit (1-2 days). Some folks decided to release updated distros or modules we include just before the weekend or even on Sunday, and during full re-testing we have found some issues which should be fixed. We have also decided to temporarily drop support for a few abandonware distros to help shorten BOA release cycle.

shorter release cycles sounds great!

Thank you for the update.

Thank you for the info and the extra work to keep things current and viable by making sure the distros offered are active.

I'm not sure if this would make it under the wire for 2.0.4 but just in case I wanted to make sure that you knew that Commerce Kickstart just came out with 2.0-RC2

http://drupal.org/project/commerce_kickstart

From the release notes, it appears the majority of updates was switching to the current Drupal and bringing in patches that had been for the prior release of the Commerce module and upgrading from DEV releases of some modules to the stable release versions.

http://drupal.org/node/1821260

Major changes in this release:
- Drupal core version 7.16, latest versions of contrib modules.
- Includes Commerce 1.4 (which includes more than 8 patches initially made for Kickstart).

- Greatly improved RTL, IE (6, 7, 8) support in omega_kickstart.
- The admin theme is now also a separate project called Shiny, with many fixes since Kickstart RC1.

- Removed 17 patches (previously applied to Commerce, Crumbs, Commerce Shipping, Cloud Zoom, Entityreference, Special Menu Items) from the make file, since they made it into new releases.
- Switched 6 modules (Commerce, Crumbs, Cloud Zoom, Jirafe, Search API Ranges, Search API Sorts) from -dev releases to newly created stable releases.
The goal is to ship Kickstart without any patches or dev releases, which takes time and depends on the goodwill of module maintainers.
This release brings us halfway there.

Yes, expected update for Commerce Kickstart 2.x was one of the reasons of the delay.

Some other reasons:

1. New PHP version was released on 18-Oct-2012 and fixed critical issues for those using apt-get based install (which is default).
2. Upload progress for Nginx has been fixed and newer version of the module released on Sunday, 21-Oct-2012.
3. MariaDB 5.5.28 and 5.3.9 was released on Monday, 22-Oct-2012
4. New, and not backward compatible, New Relic PHP Agent version 3.0 was released on 23-Oct-2012 and announced yesterday.

It was enough to re-start all tests on all OS versions we support, so it took extra time and now is almost complete.

Yes, we will rather remove support for not well enough maintained distros than add another. Still, one of the main goals of BOA, especially Octopus is to offer as much as possible, well maintained distros to choose from (you don't need to install all of them), so it is a matter of keeping a good balance between supported features/distros and shorter release cycle. Our goal is to release new BOA version every 1-2 months max.

Thanks for the additional info. I knew there had been some updates prior to your post, but hadn't realized that there were even more coming.

While I of course hope that all the distros I want to use are included :-) you're right that not including ones that aren't kept up to date is a good idea.

Curious as to the status on this. I'm going to do a fresh BOA install this weekend and I'm hoping 2.0.4 will be released in time?

PS - thanks for BOA it is fantastic!

After we have fixed really critical issue caused by recent Redis 2.6.2 released two days ago: #1825298: The website encountered an unexpected error. Please try again later. , we have yet another major issue to fix: #1825992: Redis cache is never cleared on cron nor with drush on command line

BOA-2.0.4 release is scheduled on Thursday, November 8, after Drupal 7 core release on Wednesday, November 7 (and some testing): http://groups.drupal.org/node/266188

Enjoy! https://twitter.com/omega8cc/status/266722029720440832

Excellent, thank you!!!

Thank you. So for those running BOA HEAD it is time to run barracuda up-stable (instead of up-head) and octopus up-stable to switch from HEAD to stable. Is that correct?

Just saying - Thank You !