Re: [cowiki-dev] Releasing coWiki with the "working" parser

Daniel T. Gorski wrote:

>LOL, I am ACK with you, but you know that Becky and Randy are Pauls family?
>:=) ... I needed to laugh, hehe. Forgive me, Paul, I ment it pleasant :)
>
>regards dtg
>  
>
Randy would be amused that he's been adopted, but I'm sure he likes his 
family just fine.  He is highly competent, a Master Teacher, and 
responsible for technology in a hundred or so schools in the US NW.  He 
is also a trainer for Intel's /Teach to the Future/ initiative where he 
is teaching teachers how to make technology an integral part of the 
class room (not just something bolted onto the outside).  Here's a 
pointer to his web site at PAES <http://www.paes.com/>.

My point is that

    * The development team has scratched some technological issues that
      (under normal circumstances) make absolutely no difference to users.
    * There are no performance enhancements or changes to "pay" for the
      effort of upgrading.
    * If Boron wasn't adequate for a task, then neither will be
      Fullerene (at this point).
    * The most we can claim to have is a "Bug-fix" release.  As such,
      except for the database incompatibility, the most we can claim is
      0.3.5...

BTW, with the INNODB database requirement, there are quite a few places 
we will no longer run.  As has been noted, XAMPP no longer works, and 
frankly I wonder why we have paid this price...  I know the effort was 
to get database reliability because of the "Magic" problem, but it has 
been demonstrated with the new code so I am as ready to roll back the 
database as you are the parser.

I say "Fix the database AND the parser before the next release."  I also 
don't see any reason that, if InnoDB isn't available why we can't fall 
back to MyISAM and simply forgo ACID quality transactions.

Paul