[r7423]: website / newdocs / news.html Maximize Restore History

Download this file

news.html    285 lines (218 with data), 14.7 kB

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<?python import content ?>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:py="http://purl.org/kid/ns#" py:extends="content">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type" />
<title>TurboGears: Front-to-Back Web Development</title>
</head>
<body>
<div id="page">
<h1>Nov 19, 2010: TurboGears 2.1</h1>
<p>
The TurboGears team is proud to present TurboGears 2.1. 2.1 has been in development
for about one year with the first alpha released in October of 2.1. Featuring better
performance, improved mako support, support for kajiki, an updated dispatcher, Pylons
1.0 support, and improved documentation. TurboGears is committed to maintaining the
2.x branch for the long-term.
<a href="http://trac.turbogears.org/wiki/2.0/ChangeLog">changelog</a>.</p>
<h1>Oct 17, 2010: Turbogears 2.1rc1</h1>
<p>
It’s been a long summer, and the TurboGears crew has been busy testing the new release candidate on our own production sites. We think the release is ready for introduction into the wild. One of the reasons this release has been delayed is due to the release of Pylons 1.0, which 2.1rc1 now supports. In fact, only one routing change has taken place which removes the possibility for infinite recursion, and this should not affect the majority of users. Of note is the addition of support for kajiki, which is a super-fast xml-based template language.
<a href="http://trac.turbogears.org/wiki/2.0/ChangeLog">changelog</a>.</p>
<h1>Mar 27, 2010: TurboGears 2.1b2</h1>
<p>This release is a result of the overwhelming response from TurboGears Developers
at Pycon 2010. Over 20 bugfixes were applied, with minor API changes. This
will be our last beta before releasing a final candidate for 2.1. Please see the
<a href="http://trac.turbogears.org/wiki/2.0/ChangeLog">changelog</a>.</p>
<h1>Mar 21, 2010: TurboGears 1.1.1</h1>
<p>The first bugfix release of the 1.1 branch is now available. Please see the
<a href="http://trac.turbogears.org/wiki/ChangeLog">changelog</a>.</p>
<h1>Jan 25, 2010: TurboGears 2.1b1</h1>
<p>2.1 has reached reasonable enough stability to release a
our first beta! This means that we are locking down the api, nothing will
be added or removed, only bugfixes and critical changes will be made as we
march towards a 2.1 final. Please see the
<a href="http://trac.turbogears.org/wiki/2.0/ChangeLog">changelog</a>.</p>
<h1>Nov 29, 2009: TurboGears 2.1a3</h1>
<p>2.1a3 is primarily a bugfix release. Keeping with our month-long release cycle,
there are very few changes. 2.1 is becoming more stable and therefore
this will be the last alpha release before 2.1 moves into beta. Please see the
<a href="http://trac.turbogears.org/wiki/2.0/ChangeLog">changelog</a>.</p>
<h1>Oct 27, 2009: TurboGears 2.1a2</h1>
<p>2.1a2 is primarily a bugfix release. The goals for this release were to
provide fixes for many long-standing issues. We were also able to provide a 15-20%
performance increase after reviewing some of the i18n code. Please see the
<a href="http://trac.turbogears.org/wiki/2.0/ChangeLog">changelog</a>.</p>
<h1>0ct 16, 2009: TurboGears 1.0.9 released</h1>
<p>The TurboGears 1 team is pleased to announce the release of TurboGears
1.0.9, a maintenance version for the 1.0 branch. This has almost a year's
worth of minor improvements and bug-fixes and also includes many fixes
already available in the 1.1 release.</p>
<p>While you update your old TG 1.0.x applications, why don't you take the
time to fill out our current
<a href="http://www.surveymonkey.com/s.aspx?sm=gV9RHor_2fCklQM35r2DhumA_3d_3d"
>TurboGears user survey</a>? The survey will close on Sunday Oct, 18!</p>
<h1>Oct 7, 2009: Take part in the TurboGears user survey!</h1>
<p>Now that TurboGears 1.1 final is out, and with 2.1alpha just released,
it is the perfect time to get some feedback from our users. We heartly
invite you to take part in the online survey which we have prepared! It
will only take you a few minutes and your input will be most valuable
to us. We have questions about how you use TurboGears currently and about
your expectations for TG 2.1 and further development in the TG 1
branch.</p>
<p>So why don't you head over <a href="http://www.surveymonkey.com/s.aspx?sm=gV9RHor_2fCklQM35r2DhumA_3d_3d"
>to the survey</a> right now?</p>
<h1>Oct 4, 2009: TurboGears 1.1 final released!</h1>
<p>The TurboGears 1 team is pleased to announce the release of TurboGears
1.1 final, the first stable version of the 1.1 branch. We made a few more
important changes after the 1.1rc1 release candidate.</p>
<p>Turbogears 1.1 has been rather long in the making but this means that the
current code has been running stable in production environments for
several months now. 1.1 brings many, many small improvements and fixes
and uses most of the same defaults as TG2 while being <strong>100 percent
compatible</strong> with TG1 applications. For more information on what's
new, please see the <a href="http://trac.turbogears.org/wiki/ChangeLog"
>changelog</a>.</p>
<p>With TurboGears 1.1 out the door, the TurboGears 1 team will take
some time to evaluate, where its efforts are best spent in the future.
We are commmited to supporting the TurboGears 1 branch in the future
(to prove it, we will isue a TurboGears 1.0.x maintenance release in the
next few weeks) but we are interested to know, how <strong>you</strong>
want Turbogears to evolve!. We will conduct a survey amongst TurboGears
users and followers, which we are going to announce very soon, and we
hope that many, many of you will participate! Stay tuned...</p>
<h1>Oct 02, 2009: TurboGears 2.1 alpha</h1>
<p>The TurboGears2 team has been hard at work making refinements to the
TG 2.x codebase. These refinements are ready for a public alpha
offering, with new docs, less dependencies, and better support for the
<a href = 'http://www.makotemplates.org'>Mako</a> templating engine.
Please help us test our new code against your applications. Our goal is
to release 2.1 final by February 2010.
<a href="http://trac.turbogears.org/wiki/2.0/ChangeLog">changelog</a>.</p>
<h1>Sep 20, 2009: TurboGears 1.1 release candidate</h1>
<p>The TurboGears 1 team is pleased to issue a release candidate for
the first stable version of the 1.1 branch. This has been rather long in
the making but this means that the current code has been running stable
in production environments for several months now. 1.1 brings many, many
small improvements and fixes and uses most of the same defaults as TG2
while being 100 percent compatible with TG1 applications. For more
information, see the <a href="http://trac.turbogears.org/wiki/ChangeLog"
>changelog</a>.</p>
<h1>May 27, 2009: TurboGears 2.0 available.</h1>
<p>TurboGears 2 is the next stage in TurboGears development, and provides
a solid base on which the future of TurboGears will be built. The 2.0
release does not spell the end of 1.0 support, and while it's new, there
are already people using it in production. So, if you're interested in
working with the latest turbogears, check out the
<a href="http://turbogears.org/2.0/">new TG2 release</a>, or just read up
on it in the <a href="http://www.turbogears.org/2.0/docs/">new docs</a>.
TurboGears 2 is designed to get you going with sane defaults and gets out
of your way when you know what you want. We want to make easy things
easy and still leave you in charge for since you know the needs of your
application better than we do.</p>
<h1>Dec 29, 2008: TurboGears 2.0 beta 1 released.</h1>
<p>Thanks to the hard work of Florent, Chris, Jon, Christopher, Lee,
Gustavo, Sanjiv,and many, many others we have been able to jump
directly from 1.9.7 beta 2 to 2.0 beta 1.</p>
<p>TurboGears 2 is the next stage in TurboGears development, and provides
an extraordinarybase on which the future of TurboGears will be built. We
are rapidly aproaching a 2.0 final release very early in 2007. So, if
you're the type that wants to live in the future today, check out the
<a href="http://turbogears.org/2.0/">new TG2 release</a>, or just read up
on it in the <a href="http://www.turbogears.org/2.0/docs/">new docs</a>.
But remember it's still a work in progress, so feel free to help us dust
the cobwebs out of the corners and get ready for a full public release
over the few weeks.</p>
<h1>Dec 17, 2008: TurboGears 1.0.8 stable released.</h1>
<p>Even during the TG2 sprint we think about our user base and do
maintenance releases of TurboGears 1.0. Here is a bugfix only release for
TurboGears 1.0 serie which fixes a few glitches with IE7. Some more
improvements have been made that I'll let you discover in the changelog.</p>
<h1>Dec 3, 2008: TurboGears 1.1b3 Plissken, released.</h1>
<p>A new beta release for the 1.1 serie. A small typo slipped into the last
beta version and has been fixed. Please enjoy this new beta version and
give us as much feed back as possible in the next days.</p>
<h1>Dec 2, 2008: TurboGears 1.1b2 Plissken, released.</h1>
<p>A new beta release for the 1.1 serie. This brings even more features like a bootstrap commmand,
i18n support for Genshi templates, an absolute url generation function, the possibility to choose
the inclusion order of your widgets (think JS)... and many more enhancements and fixes.
</p>
<h1>Sep 15, 2008: TurboGears 1.0.7 stable released.</h1>
<p>This version brings some more bug fixes that could not but included in the last 1.0.6 release,
and also fixes a bug which was introduced in the previous release when backporting some identity
stuff from the 1.1 branch. All 1.0 users who want to stay in 1.0 before trying out our new 1.1 beta
should upgrade to this 1.0.7 release directly without using 1.0.6.
</p>
<h1>Sep 10, 2008: TurboGears 1.1 Plissken beta1 released.</h1>
<p>To install this beta version you'll need to use easy_install and make
sure you have an ORM installed (as easy as running "easy_install
SQLAlchemy")</p>
<p>In 1.1 Plissken, the defaults have been changed and you now get Genshi
as a rendering engine, and SQLAlchemy as an ORM when quickstarting a new
project.</p>
<p>Please test, report bugs and glitches in the
<a href="http://groups.google.com/group/turbogears">mailing list</a>...</p>
<h1>Aug 26, 2008: TurboGears 1.0.6 stable released.</h1>
<p>The TurboGears team is proud to announce the 1.0.6 release of our web
framework. This version adds some more stability and offers some new
functionalities.</p>
<p>This release is a maintenance release to backport some enhancements
and fixes that were found while working on the 1.1 upcoming release.</p>
<p>TurboGears 1.1 is nearing a beta release and will be available real
soon for testing</p>
<h1>TurboGears joins Google Summer of Code 2008!</h1>
<p>TurboGears is excited to be a <a href="http://code.google.com/soc/2008"
>Google Summer of Code</a> (GSoC) 2008 mentoring organisation!</p>
<p align="center"><a
href="http://docs.turbogears.org/GSoC"><img
src="static/images/gsoclogo_shadow_228x158.png" border="0" width="228"
height="158" style="float: right; padding: 1em"/></a></p>
<p>We are <a href="http://docs.turbogears.org/GSoC/StudentsApplication2008"
>looking for students</a> who want to work on a <a
href="http://docs.turbogears.org/GSoC/Ideas2008">TurboGears GSoC 2008
project</a> during the Summer and to be part of the fascinating world
of Python web frameworks and Open Source! Please help to spread the word
and visit our central <a href="http://docs.turbogears.org/GSoC"
>TurboGears GSoC page</a> for project ideas, application rules, flyers
and many other resources.</p>
<h1>Jul 1, 2008: TurboGears 1.0.5 stable released.</h1>
<p>This release was a maintenance release to prepare our teams to work mainly on the 1.1 branch.</p>
<h1>Mar 7, 2008: TurboGears 1.0.4.4 stable released.</h1>
<p>The TurboGears team is proud to announce the 1.0.4.4 release of the
megaframework. This version adds some more stability and offers even more
functionality.</p>
<p>This release marks a turning point in the TurboGears evolution because
starting at this date the 1.1 branch becomes our main development branch
and will see the new defaults (Genshi, SQLAlchemy) proposed to the
public.</p>
<p>We still support SQLObject and Kid, and will continue to do so in the
1.0 &amp; 1.1 branches for security fixes and important bugfixes.</p>
<h1>Jan 21, 2008: TurboGears 1.0.4 stable released.</h1>
<p>
This version includes the security fix mentioned below and fixes many bugs.
It follows a long beta cycle that helped us eliminate a lot of problems and
polish this release with love to give you an even better TurboGears
framework.
</p>
<p>
Enjoy!
</p>
<h1>Important Security Notice</h1>
<p>CherryPy 2.3.0 has been released and contains an <b>important</b>
<a href="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-0252">security
fix.</a></p>
<p>We just released two versions of TurboGears to make sure all new
installs are using the safe version of CherryPy.<br/>
If you are using our stable version please upgrade to TurboGears
&gt;= 1.0.3.3. If you are using our beta version please upgrade to
TurboGears &gt;= 1.0.4b5.</p>
<p>If you do not want to change the version you are using for any reason,
but are using file based sessions with CherryPy please upgrade your
CherryPy server <strong>immediately</strong> using the following command:
<pre>easy_install -UZ "Cherrypy==2.3.0"</pre></p>
<p><strong>Update:</strong> There is a stable release for TurboGears 1.0.4
available now. We suggest that you upgrade to the latest stable version
1.0.4.3.</p>
</div>
</body>
</html>