Given the pace of quick adoption for new versions of web2py, I think it would be good enough to mark a new release (except if it's just a bug fix release) like "latest" or "edge release", and just keep the previous one as "recommended".
After some days (for example one week), without new releases, the "edge" would become "recommended". If bugs are found in the "edge", like it happened in 1.90 after the DAL rewrite, then just release 1.90.2 as "edge", 1.90.3, 1.90.4, ... without promiting them as "recommended". After one week of no new releases, the current 1.90.x would become "recommended" (there would be no "edge" download until a new release is done). This wouldn't add extra work to the them. Just changing the label of the release in the download page, and sometimes keep 2 download links instead of one. Greets. On 22 dic, 20:31, Branko Vukelić <stu...@brankovukelic.com> wrote: > On Wed, Dec 22, 2010 at 8:29 PM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > The idea was to have stable and nightly-build. The problem is that > > very few people check the nightly build. > > Well, yeah, it's because it's sounds like a nightly TRUNK dump. :) > It's better to make a 'incubation release' or something like that, so > it's obvious that it's a release. And when it's hatched, you can label > it safe-for-production. I don't know if people would use them, though. > They might still go yuck and decide it's just like nightly, with a > fancy name. :D > > -- > Branko Vukelic > > stu...@brankovukelic.comhttp://www.brankovukelic.com/
