On Mon, Aug 22, 2011 at 4:06 AM, Jörgen Maas <jorgen.maas(a)gmail.com> wrote:
I think there should be a list of features we absolutely want in 2.1.
When will the feature freeze be? When will the (beta) testing start, etc etc?
Basically, some form of release engineering...
I think the feature freeze would be at the least the last month of the
cycle, so 5 months of adding stuff with 1 month of feature freeze
where no more features would be added. Each week of that last month
could be a RC, or just a beta version depending on how people want to
do things.
> The major feature change I'd like to see for 2.2 would be a
new
> templating engine. Cheetah has got to go, it is poorly supported and
> extremely difficult to debug errors with. We could continue to support
> cheetah for a while, but we need to setup some transition plan.
Do you have an alternative in mind?
Not really, I've been using ruby/sinatra a lot lately, which has a ton
of templating options available for use. It just got me thinking on
how much of a pain cheetah is in comparison. Obviously, the top choice
would probably be Django's templating engine, though it is a bit
verbose and restrictive.