On Tue, Aug 23, 2011 at 5:06 AM, Jörgen Maas <jorgen.maas(a)gmail.com> wrote:
On Mon, Aug 22, 2011 at 1:16 PM, James Cammarata
<jimi(a)sngx.net> wrote:
<snip>
>
> 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.
>
Sounds like a decent plan.
So, can we/you/me/someone start putting information like this on the
wiki and start the ball rolling? ;)
I'd like to get feedback from more people, not sure if everyone's on
summer vacation or not but this would ultimately be up to Scott.
> 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.
The only "drawback" i see is that cobbler-web becomes mandatory.
Personally i have no problem with this, others might though.. dunno.
Installing the django package would be, yes, but you wouldn't have to
use the webui. I'm not a huge fan of using the django template engine
though, it is very heavy-handed and restrictive, since it was designed
for a purpose that probably didn't envision general purpose
templating. It's just the path of least resistance, since it is
already used in some part of cobbler.
You can see here just how many options there are for python though:
http://wiki.python.org/moin/Templating