This is a rather early follow up release, mainly early because of GIO issues that were rather hard to reproduce and made Midori unusable for some users. Also waf was updated because the previous version wouldn’t build on OpenBSD.

Two new features…

Continue reading " Fast and fervent follow up "

Hello,
As promised, Gnac-0.1.1 has been released!
Some improvements include better progressbar and more information about files.
We also spent a lot of time doing code refactoring, mainly in the conversion library which has been partly rewritten.
Feel free to send us your comments, feature requests or bug reports.
Thank you for using Gnac!

Continue reading " Gnac-0.1.1 released!! "

While we’re still hard at work pushing Flock 2 from beta towards release, we are taking a moment to provide you with Flock 1.2.5.

Flock puts you at the center of the action, with all your tools and services orbiting around you.  It’s a lot of work to string all these things together, and occasionally things break.  This has been the case with Twitter and Facebook in recent days, as they have both changed elements of their back-end (Facebook with a new design, Twitter with their feeds).  You may have noticed issues posting your status to Facebook from the People Sidebar or getting recent friend updates from Twitter in the sidebar.  These have been fixed in Flock 1.2.5, which is available now from http://www.flock.com. Auto-updates will go out next week.

Enjoy, and please continue to provide the great and timely feedback that allows us to keep Flock in tip top shape!

Evan Hamilton
Community Ambassador
evan at flock dot com

Tags: flock, browser, 1.2.5, twitter, facebook, newfacebook, bugs, fixes

Continue reading " Flock 1.2.5: Facebook and Twitter Fixes "

Here is a cool animated Code_Swarm graphcreated by /nickpalmer from our CVS source commits.

Continue reading " bitweaver Code Swarm! Trip out to 3 years of bitweaver code "

Behind the scenes there were a few changes and I still didn’t announce anything, since I still hadn’t done all bits of it yet. The last bit being the first release of Midori under the hood of Xfce Goodies.

What does Midori moving in with Xfce bri…

Continue reading " Moving to Xfce land "

Hello,
Thank you for  those of you who tried Gnac and sent us their comments.
We have solved the problems you have reported to us and therefore, Gnac 0.1.1 will be released very soon!!
As some of you ask us to make a .deb package, we did it and it will be released with Gnac 0.1.1.
Thank you for [...]

Continue reading " Gnac 0.1.1 is approaching!! "

Mike from “Capsize Designs” shares his experiences from choosing a content management system for their most recent project. Capsize Designs chose Textpattern from a short-list containing Drupal, ExpressionEngine, SilverStripe, Textpattern,…

Continue reading " Spoilt for CMS Choice [9] "

We are happy to announce the stable releases of eZ Publish 4.0.1, 3.10.1, and 3.9.5. These releases carry a huge number of fixes (about 310 for 4.0.1) and upgrading is highly recommended. eZ Publish 4.0.1 should be used for all new installations.

Included in these new releases is a dedicated extension to migrate custom URL aliases and URL history elements for existing 4.0.0 and 3.10.0 sites.

Please also note the
security advisories which are resolved with these maintenance releases.

Continue reading " eZ Publish 4.0.1, 3.10.1, and 3.9.5 released "

Had some nice crasher fixes in svn for a while so I thought I would do a new minor release. There is also 3 new translations and some translation updates. Should be good for everyone. Debian packages should also work on amd64 now (please test ).

Continue reading " Nemo 0.2.3 released "

As most of you know, a critical security vulnerability affecting all Joomla versions below (and including) 1.5.5 was discovered on Tuesday, August 12th 2008.  What most of you don’t know, is what went on behind the scenes that day.  A whole mass of people came together and immediately worked on all the tasks necessary to make 1.5.6 happen.   Experiencing this first hand was quite amazing…  Publishing a release is a process that normally has two weeks (and a team of people) devoted to it (for everything from selecting which remaining artifacts will be fixed, to translations, to clicking publish and everything in-between).  This all happened in a VERY short time.

Here’s an abridged breakdown of how 1.5.6 came to be…

15:50 EST

Bug Squad member Marijke Stuivenberg points the squad to a reported vulnerability in Joomla 1.5.5.

15:55 EST

Bug Squad members Jennifer Mariott, Elin Waring, and Marijke (along with development coordinator Wilco Jansen, OSM Vice President Rob Schley and myself) verify that the vulnerability exists and the report is valid.

15:56 EST

All available development Work Group members, Bug Squad members and Core Team members are notified of the issue.

Bug Squad confirms that 1.5’s SVN is stable and is ready for immediate release pending vulnerability fix.

Forum moderators are informed of and asked to remove references of this issue until release.

16:05 EST

Patch is generated and provided to Bug Squad for testing/confirmation of fix.

16:20 EST

Patch is confirmed to fix vulnerability.

Front page announcement is drafted.

16:30 EST

Patch is committed into SVN along with all preparations for release. 

Joomla 1.5 branch is frozen for release cycle.  Bug Squad begins testing sanity and operation of SVN.

16:46 EST

Security announcement (on developer.joomla.org) is drafted.

17:20 EST

Front page announcement provided to translators.

Joomlacode prepared for release.

17:30 EST

Bug Squad confirms sanity of SVN and that all release preparations are in place.

Package generation begins. 

17:50 EST

Full download packages generated.

18:05 EST

Packages provided to Bug Squad for validation and testing.

18:30 EST

Bug Squad confirms package sanity, final steps before release are completed.

18:40 EST

Front Page article and Developer security report published. 

Full download packages released.

19:30 EST

All patch downloads tested and published.  Release cycle completed.

Conclusion

Total time from report of vulnerability to initial release: 2 hours 50 minutes

Total time from report of vulnerability to completion of release cycle completion: 3 hours 40 minutes

Total number of people directly involved: between 20 and 30

Continue reading " How Joomla 1.5.6 came about "