Merry christmas to the whole list.
I think this has been suggested earlier but thought I´d bring it up again.
I have two instances of web2py via wsgi and Apache running on my server.
One reason is the possibility to upgrade my development side everytime I
log in to admin, that way getting all new features and testing at the
same time.
Would it be possible to get two upgrade buttons in admin, one for
"stable" and one for the latest release. Lot of the time there their the
same. Maybe a third button for trunk, if that is possible.
Is there instructions how to use the hg stuff to use the trunk. Could
not find the hg command in the book?
Kenneth
+1
On Fri, Dec 24, 2010 at 8:20 AM, Luis Díaz<diazluis2...@gmail.com> wrote:
+1
2010/12/24 ron_m<ron.mco...@gmail.com>
I for one am happy with the current release cycle. It is a good balance
between new features and the ultimate stability of release 1.XX.N where N
is the last version before XX+1 for example. The nightly build is a bit of a
misnomer, many projects (C or C++ mostly) have some automated process that
takes trunk and compiles it to produce a .tar.gz labelled nightly which
"might" work. For web2py we should just hg pull; hg update to achieve that
result. The nightly for web2py is more like a beta because Massimo hand
picks code from trunk that will or will not be in the nightly which could
really be a weekly.
I am currently developing the application I am working on and testing is
easy enough that I test trunk at least daily. The web2py server is quite
easy to use but the code in some places is complicated and has many possible
use cases. It is only through exposure out to the user base that a large
number of use cases of the code get tested. I have even seen problems
reported where something was fixed but used by maybe one person in a way
that should not have worked resulting in the dreaded bug that worked and
became a useful feature for someone.
Once I go to production I will probably move the releases a lot slower
through the installed base. In fact I have 2 beta production systems up now
and only push a new web2py when I push a new version of the application to
the stakeholders to look at.
Massimo provides a fantastic service with the web2py project and I would
not like to see him stifled by a load of process. Anyone that has time to
test will definitely help the quality, if you don't have time, that is okay
too. I personally don't mind doing some release management between where
Massimo is burning the midnight oil and what I let out into the production
systems I have/will manage. The product is alive with new features and bug
fixes sometimes occur in minutes once reported. That is worth a lot.
Ron
--
Díaz Luis
TSU Analisis de Sistemas
Universidad de Carabobo
http://web2pyfacil.blogspot.com/
Facultad de Odontología
