TurboGears 1.0 is out???

[Steve Bergman]

I just installed TG on a new machine and was surprised to get something
called TurboGears 1.0. Not b1, not b2, not b3. But 1.0. The site now
says TurboGears 1.0 with a date of Jan 3.

[isaac]

yes, it is!

[Karl Guertin]

Yes, 1.0 was released at around 12:15 EST. In addition, Kevin has
stepped down as BDFL and Alberto has taken over. The irc log [1] might
be of interest.

[1] http://irclog.turbogears.org/archive/freenode/turbogears/2007/01/03

The meeting starts at 1700 on the log.

[Jorge Godoy]

"Steve Bergman" <st...@rueb.com> writes:

It is out. ;-)

--
Jorge Godoy <jgo...@gmail.com>

[Kevin Dangoor]

Note that I'm planning to send out proper announcements later today,
but that is the quick summary :)

Kevin

[Dieter]

Amazing... finally a python web framework has reached 1.0 status. :)
Keep up the good work.

[Steve Bergman]

Dieter wrote:
> Amazing... finally a python web framework has reached 1.0 status. :)

And now that 'with' has been added, Python keywords now outnumber them.
;-)

I just finished reading over the irc log. This is all truly exciting.
Congrats, Alberto.

[Matthew Bevan]

> I just finished reading over the irc log. This is all truly exciting.
> Congrats, Alberto.

Indeed, I only recently finished with the IRC log. Impressive and
congratulations to all!

There is, however, one show-stopper that prevents me from upgrading
past my own custom version of 1.0b1. That is, Trac Ticket #468 [1],
supposedly resolved in r2259 [2]. I do not currently have the time
to test the SVN version, but I hope I do later tonight when my time
is my own again.

I have been, previously, required to solve this bug by hand on two
development and one production machine, thus breaking the sacred unit
tests and requiring me to remember to make the change every time I
update an installation or install new. I was quite surprised that
this problem - which effects everything KID can be configured to do;
i18n, site templates, default output format, and default encoding,
just to mention the settings I actively use - was not fixed in 1.0.
It had, in past, been scheduled for release in 0.9 and 1.0b2.

I eagerly await a 1.0.1 release which includes this fix, and will not
be upgrading until then for fear of breaking my projects,

Matthew Bevan, Systems Administrator
Top Floor Computer Systems Ltd.

[1] http://trac.turbogears.org/ticket/468
[2] http://trac.turbogears.org/changeset/2259

[Jorge Vargas]

On 1/3/07, Matthew Bevan <matt....@topfloor.ca> wrote:
>
> There is, however, one show-stopper that prevents me from upgrading
> past my own custom version of 1.0b1. That is, Trac Ticket #468 [1],
> supposedly resolved in r2259 [2]. I do not currently have the time
> to test the SVN version, but I hope I do later tonight when my time
> is my own again.
>

1.0 is tagged at r2333 and r2259 was applied to the 1.0 branch that
means it is there, unless what your trying to say is that the fix that
was applied doesn't works?

>
> I eagerly await a 1.0.1 release which includes this fix, and will not
> be upgrading until then for fear of breaking my projects,
>

if the above is right then this is not needed

[Matthew Bevan]

> 1.0 is tagged at r2333 and r2259 was applied to the 1.0 branch that
> means it is there, unless what your trying to say is that the fix that
> was applied doesn't works?

Indeed, now that I have had a chance to install 1.0 on a clean test
machine, creating a brand new quickstarted project, copying over my
massive site template and configuring the project, the site template
is actually used, and does generate content to my specifications
(xhtml-strict). Bravo!

Thanks to all the contributors for 1.0!