rolfm at denison
Oct 20, 2008, 2:21 PM
Post #3 of 8
(1658 views)
Permalink
|
On Oct 20, 2008, at 3:36 PM, Simon Wilcox wrote:
> We originally selected Bricolage back in 2003 for a project to
> deliver XML content for a mobile portal. Some 45,000+ stories &
> 17,000+ images later it's still going strong.
>
> I'm pleased to say that the portal is being revamped and we're going
> to be building a new version of the CMS to deliver content to it.
>
> So we're considering jumping in with both feet and doing the work in
> Bricolage 1.11.x.
>
> Is this wise or are we being foolish, does anyone think it's really
> not production ready yet ?
The good: I am very excited about the forthcoming 2.0 release. The
AJAX goes a *long* way to solving some of the more frustrating user
interface issues. The element occurrence improvements are massive for
outputting hardcore structured xml. We won't be running this on MySQL
anytime soon, but those improvements will be of use to people who use
that DB. Apache 2 support is very welcome. It works with Perl 5.10.
I have no doubt this will be the best version of Bricolage yet by a
long shot.
The bad: I haven't tested 1.11.1 very rigorously yet, but I've found
plenty of bugs. Most of them are of the user interface variety. Some
of them are holdovers from 1.10, some of them are new feature
specific. The one thing that concerns me, as I mentioned in my last e-
mail, is the coherence among the Find Stories/Desks/Workspaces. At
Denison in version 1.10 we experienced files duplicating themselves
(check out a document, start editing, and suddenly two documents are
in the workflow or on the desk), files slipping out of workflows,
things like that. 1.11.1 has the added fun of AJAX buttons, which
didn't always work the best in earlier builds. Those issues have
greatly improved, but I've still found some coherence problems. One
story I created will not show up on any desk interface no matter what
I do. The find stories interface would let me check out stories I
already had checked out.
The bottom line: There is nothing to suggest Bricolage 2.0 is more
unstable than 1.0, but I've also not subjected it to serious load
testing nor even a methodical testing procedure. There are great
improvements in the interface, but there is also a lot that could be
patched and improved before a release goes out. It seems like 1.11.1
has provided the momentum for us and a lot of others to do more
serious bug testing and fixing in the coming weeks.
Ultimately, it is up to you. Take a look at the bugs that have been
filed against 1.11.1. Set up a test server, import your stuff and see
how it goes in a controlled environment. If you feel like the bugs
that are already out there and the ones you find are tolerable then go
for it.
We will undoubtedly be waiting for the release version, if not the
first point upgrade. Part of that has to do with our academic
schedule. We are in no rush, but damn is 1.11.1 sexy.
I know Scott was looking at 2.0 as well, but I'm not sure what
conclusions he came to.
-Matt
|
