On Wed, Aug 29, 2012 at 10:41 PM, Massimo Di Pierro
<massimo....@gmail.com> wrote:

Should be 100% backward compatible. If you run into any issue let us know ASAP.

On Thursday, August 30, 2012 6:41:34 AM UTC+3, Massimo Di Pierro wrote:

After 5 months. It is done. This is the most waited and the most feature-packed release.

I am sure we'll find some corners that need to be ironed but it is considerably better than 1.99.7. It adds lot of new features and improves many existing ones:

On Wednesday, August 29, 2012 11:41:34 PM UTC-4, Massimo Di Pierro wrote:

After 5 months. It is done. This is the most waited and the most feature-packed release.

I am sure we'll find some corners that need to be ironed but it is considerably better than 1.99.7. It adds lot of new features and improves many existing ones:

- 57,000 new lines of code and closed 279 issues since 1.99.7.

- Retrieving data from DB should be faster, in particular select(cacheable=True)

- Has a new scheduler, a built-in wiki, new language and pluralization system, better markmin with oembed support and better scaffolding app, increased security.

- Lots of experimental features including GIS support, mongodb support, built-in auth.wiki(), and more.

Should be 100% backward compatible. If you run into any issue let us know ASAP.

I personally want to thank the major contributors to this release (in alphabetic order)

Alan, Andrew, Anthony, Bruno, Christian, Dave, Dominic, Iceberg, Jonathan, Marc, Mariano, Marin, Martin, Mark, Michael, Michele, Niphlod, Patrick, Vladyslav, 

They spend many nights testing, coding, debugging at a very fast pace.

Many many people have contributed.

If your contribution has not been properly acknowledged please let us know ASAP. It is probably an oversight.

Massimo

Please can you post a concrete example?

On Friday, August 31, 2012 7:44:31 AM UTC-4, viniciusban wrote:

First of all, I'd like to thank you all. You're making a great job, guys.
I see web2py becoming more reliable to bigger projects and I'm very
pleased with it.
You all rock! :-)

In spite of this huge effort, isn't it premature to call 2.0.2 or even
2.0.3 stable? I know there were several months of hard work, but if we
have bugs detected so fast, we cannot call it stable yet, right?

Maybe some release candidate call or a pre-release period for tests,
before spreading it as stable would help us.

> Web2py has so much features and it is impossible to test everything.

On 08/31/2012 09:01 AM, Marin Pranjić wrote:
> It is called stable since no one using trunk/nightly build detected
> those errors.
>
> I agree with you, but you cannot blame anyone.
>
>

> On Fri, Aug 31, 2012 at 1:44 PM, vinic...@gmail.com

>              - db(...).select(cacheable=True) make select 30% faster

>              - MongoDB support in DAL (experimental), thanks Mark Breedveld
>              - geodal and spatialite, thanks Denes and Fran (experimental)
>              - db.mytable._before_insert, _after_insert, _before_update,
>              _after_update, _before_delete. _after_delete (list of
>         callbacks)
>              - db(...).update_naive(...) same as update but ignores
>              table._before_update and table._after_update
>              - DAL BIGINT support and DAL(...,bigint_id=True)
>              - IS_IN_DB(..., distinct=True)
>              - new syntax:

>         <http://db.b.id>))
>              - db.mytable.myfield.filter_in, filter_out

>         versioning to this table
>              - teradata adapter, thanks Andrew Willimott
>              - experimental Sybase Adapter
>              - added db.table.field.avg()
>              - Support for Google App Engine projections, thanks Christian
>              - Field(... 'upload', default=path) now accepts a path to a
>         local
>              file as default value, if user does not upload a file.
>         Relative path
>              looks inside current application folder, thanks Marin

>         results in
>              Rows, thanks Anthony
>
>              ### Auth improvements
>

>              - auth supports salt and compatible with third party data,
>         thanks
>              Dave Stoll
>              - CRYPT now defaults to pbkdf2(1000,20,sha1)
>              - Built-in wiki with menu, tags, search, media,
>         permissions. def
>              index: return auth.wiki()

>              - new layout based on Twitter Bootstrap
>              - New generic views: generic.ics (Mac Mail Calendar) and
>         generic.map
>              (Google Maps)
>              - request.args(0,default=0, cast=int, otherwise=URL(...)),
>         thanks
>              Anthony
>              - redirect(...,type='auto') will be handled properly in
>         ajax responses
>              - routes in can redirect outside with

>              - better memcache support
>              - improved spreadsheet, thanks Alan
>              - new internationalization engine, thanks Vladyslav
>              - pluralization engine, thanks Vladyslav
>              - new markmin with support for nested lists, <i>, <em>,
>         autolinks,
>              thanks Vladyslav
>              - new syntax: {{=BR()*5}}
>              - gluon.cache.lazy_cache decorator allows caching functions
>         in modules
>              - .coffee and .less support in response.files, thanks Sam
>         Sheftel
>              - ldap certificate support
>              - pg8000 postgresql driver support (experimental)

>              - added tox.ini, thanks Marc
>              - web2py.py --run_system_tests, thanks Marc Abramowitz
>              - html.py (and web2py helpers) can be used without web2py
>         dependencies
>              - new fpdf, thanks Mariano
>
>         --
>
>
>
>
>     --
>
>
>
>

> Web2py has so much features and it is impossible to test everything.

Sorry, but I cannot agree with this statement. Is it the official position?

"Stable" means: "you can download and just use it". Anything different
is "almost stable" or "buggy yet" or, using beautiful words, "release
candidate" or "pre-release version".

but I think it could be very good to have a beta testing a week before stable.

On 08/31/2012 11:07 AM, Richard Vézina wrote:
> Hello,
>
> I love web2py and normally I just wait a bit when there is new version
> to make sure I don't spend to much time on version issue.
>
> I also test de trunk once in a wild, but I found difficult to proceed
> that way. 1) I don't have much time, 2) there is often little issue that
> will be gone in a release that are actually artifact of development I
> think. I mean, the developer know that there is most probably something
> wrong with the new code he produce, but just can't test it in all situation.
>
> For sure, tag a beta testing version before releasing could make more
> work and struggle with version control to make sure patch spread over
> all branch (trunk, beta), but I think it could be very good to have a
> beta testing a week before stable.
>
> Anyway, I don't have to much problem with the actual practices, but I
> think beta test could had avoid 1.99.5 for example, since this version
> has be the beta test version and 1.99.7 the final.
>
> Richard
>
> On Fri, Aug 31, 2012 at 9:49 AM, Anthony <abas...@gmail.com

> <mailto:abas...@gmail.com>> wrote:
>
>         > Web2py has so much features and it is impossible to test everything.
>
>         Sorry, but I cannot agree with this statement. Is it the
>         official position?
>
>
>     Well, we can probably improve the unit test coverage. And there's
>     been recent talk of developing a test application to check against
>     for some functional testing. But as with any software (particularly
>     as complex as a web framework), it's not possible to test every
>     conceivable permutation of functionality a user might implement. We
>     have to rely on reports of bugs found in the wild to some extent.
>
>         "Stable" means: "you can download and just use it". Anything
>         different
>         is "almost stable" or "buggy yet" or, using beautiful words,
>         "release
>         candidate" or "pre-release version".
>
>
>     We had two (officially labeled) release candidates
>     (http://code.google.com/p/web2py/source/detail?r=ed41a29eb7c2e283587c141d0464b6c9be68eb0d).
>     Maybe we should change the "Nightly Build" label on the downloads
>     page to "Release Candidate", and perhaps advertise a bit more. Not
>     sure it will help, though, as there were already many requests for
>     testers. What do you suggest?
>
>     Anthony
>
>     --
>
>
>
>

On 09/01/2012 05:18 PM, Richard Vézina wrote:
> Confirm backward compatibility.
>
> I just migrate from 1.99.4 to 2.0.5
>
> Notice, that I change :
>
> controllers/appadmin.py
> static/css/*
> static/js/*
> static/images/*
> views/*generic.*
> views/web2py_ajax.html
>
> With the files form welcome app, provided within web2py.
>
> Thanks Massimo and all developers for this promising new web2py version!!
>
> Richard
>
> On Sat, Sep 1, 2012 at 1:11 PM, Massimo Di Pierro

> <massimo....@gmail.com <mailto:massimo....@gmail.com>> wrote:
>
>     I agree. we kind of have a referral program (experts4solutions.com

>     businesses. We need to create more structure. There are definitively
>     business opportunities.
>
>
>     On Saturday, 1 September 2012 08:32:55 UTC-5, apps in tables wrote:
>
>         So, How to do business with web2py?
>
>         How to find a customer ( needs web app )?
>
>         How to find a technical support ?
>
>         I think the business side of web2py needs to be wraped up in a
>         video by massimo...
>
>
>         On Saturday, September 1, 2012 4:26:56 PM UTC+3, apps in tables
>         wrote:
>
>             Most of the users will donate, specially the ones who do
>             business with web2py.
>
>             On Saturday, September 1, 2012 3:30:12 PM UTC+3, Massimo Di
>             Pierro wrote:
>
>                 No you do not win anything. It means make a gift to
>                 web2py. It is the usual donation box.
>
>                 On Saturday, 1 September 2012 00:38:29 UTC-5, apps in
>                 tables wrote:
>
>                     make a gift to win 10,000 ???
>

{{if response.flash:}}
<header>
    {{if 'errors' in response.flash:}}
    <div class="alert alert-block alert-error fade in">
        <button type="button" class="close" data-dismiss="alert">
            &times;
        </button>
        <p>
            {{=response.flash}}
        </p>
    </div>
    {{else:}}
    <div class="alert alert-block fade in">
        <button type="button" class="close" data-dismiss="alert">
            &times;
        </button>
        <p>
            {{=response.flash}}
        </p>
    </div>
    {{pass}}
</header>
{{pass}}

Also will need to add in proper success ones as well. I'll get to it within a week then send a pull request