Ed Leafe wrote:
> On Jan 15, 2007, at 4:10 PM, Paul McNett wrote:
> 
>> Did you want dabo 0.7.2 to include the bindfunc rework? I ask because
>> you have a note that it is deprecated in 0.7.2 and will be removed in
>> 0.8. But the actual truth (as of now) is that it is deprecated in  
>> trunk
>> and 0.7.2 will not have the OnEvt parameters in place, unless we
>> backport the change to stable.
> 
>       OK, my misunderstanding. I thought that when we do a release, it  
> would take the trunk and call it 0.7.2, but you're saying that 0.7.x  
> is permanently forked from the trunk, right?

Your above paragraph is true when we do major releases (0.6.x to 0.7, 
for example), but when we do minor releases (0.7.1 to 0.7.2) we 
maintain the bugfix-only policy and only backport the needed things, in 
order to keep it 'stable', which means that features and API don't change.


>       What would be the advantage of not releasing our current stuff as  
> 0.7.2? Besides not having to test very much, that is. I thought we  
> were hoping for more of a "release often" approach.

I guess we should specify what we want, including defining terms like 
"often". We released 0.7 on November 16, about 2 months ago. We did 
0.7.1 a few days later, to fix some bugs, and now we are doing 0.7.2 
which fixes a lot, including adding wxPython 2.8 support.

In my mind, we should make stable releases as often as warranted by the 
bugs found and fixed. We waited too long between 0.7.1 and 0.7.2, but 
then again I only wacked out the last wxPython 2.8 bug a couple days ago.

We should make major releases probably in the 2-3 month timeframe, 
meaning we are due for 0.8 this next month. This feels right to me as 
trunk and stable have diverged quite a bit what with the mementos 
makeover, the spaces in field names change, and the ms-sql stuff.

Do you agree with this or no?


>       The bindfunc stuff is working great. The only issues possibly  
> remaining is that there may be a few places where the call to append/ 
> prependMenu uses the positional parameter for the bindfunc, but I've  
> gotten all of those that I can find.

We'll just have to find and fix those as they come up. I've left the 
bindfunc changes out of 0.7.2, and will change the docstrings in trunk 
to match that the feature is added in 0.8 and bindfunc will be removed 
in 0.9.

-- 
pkm ~ http://paulmcnett.com


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev

Reply via email to