On Aug 18, 2009, at 3:59 AM, mdipierro wrote:

>
> I think would be an unnecessary constraint.
> Bugs are always in new features and the more people use is the more
> likely they are found.

web2py is especially easy to update, so managing fixes is relatively  
painless. Not quite as easy as the one-click updates in, say,  
WordPress, but WP has the advantage of being able to assume that  
there's always an admin interface available.

Of course, not all fixes are urgent, but when normal operation leads  
to a crash, or when there's a new security vulnerability, it's nice to  
see prompt action.

The IS_STRONG bug (not IS_LENGTH, actually) was my fault, and  
illustrates the danger of cosmetic patches. (I was fixing up the  
validator messages, and in doing meant to change "some message" +  
variable to a Python %-formatted string, and my fingers automatically  
typed the C syntax instead. Oops.)

The new fix is obvious and safe; mine not so much, but the cosmetic  
diffs obscured the new bug, I'm afraid, so it slipped through the  
review process without getting caught. I should have tested that path,  
too, but I was thinking of it as simple typo fixes, not substantial.  
Well, there's a lesson in there.

>
> Massimo
>
> On Aug 18, 5:24 am, Anand Vaidya <anandvaidya...@gmail.com> wrote:
>> Hi Massimo,
>>
>> I have a suggestion:
>>
>> Why not web2py be released on a schedule (say one stable release  
>> every
>> six months), and all the minor releases such as 1.66.0 , 1.66.1 etc
>> folded into either beta or release candidates?
>>
>> This will help in stable releases with adequate test releases.
>>
>> Regards
>> Anand
>>
>> On Aug 18, 1:32 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>>
>>> 1.66.1 posted
>>
>>> fixes a bug in IS_LENGTH
>>> allows actions to return unicode strings (automatically converted to
>>> utf8)
>>
>>> please check it.




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to