[typo] Towards 4.0.0

Piers Cawley pdcawley at bofh.org.uk
Thu Mar 30 03:29:48 EST 2006

So, I've been looking at the roadmap, and as far as I can tell we have
two show stoppers:

1. #725 -- the cornered rat issue
   I am not prepared to push the real 4.0 until is substantially
   easier to install than it is right now. We *must* provide both easy
   initial installation and easy migration for people currently on

2. #746 -- It must work with 1.1
   Something of a no brainer really

However, if at all possible, we want a 2.6.0 user to be able to
something like this sequence of steps:

1. Upgrade to Typo 4.0.0
2. Check everything's working.
3. Upgrade to Rails 1.1
4. Check everything's working

Requiring to independent upgrades before the user has a working blog
is probably not a good idea. The current rails_1_1 head seems to work
with both 1.1 and 1.0 now, certainly in production mode, so that's
probably for the best. However, until 4.0.0 is out, I think we really
need to do our level best to retain dual compatibility.

I'm happy to push pretty much everything else on the 4.0.0 milestone
on to the 4.1 milestone. Also, as soon as we've got the rails_1_1
branch merged back into the trunk I want to cut a
typo-4.0.0_for_daredevils tarball which can continue to suffer from
the cornered rat problem, but which will work with 1.1

Again, I'm interested in everyone's input, but I'm particularly keen
to hear from anyone still running 2.6.0.

We're also looking into working out an appropriate incantation to
shove in 2.6.0's environment.rb which will force it to use the 1.0
gems if they're installed, so hopefully we'll be able to make a 2.6.1
that you can just untar over your 2.6.0 installation and, so long as
you still have your old gems kicking about (and most hosting services
will do) everything will continue to work. If anyone *knows* the
appropriate incantation and has tested it, a patch would be enormously

Piers Cawley <pdcawley at bofh.org.uk>

More information about the Typo-list mailing list