On Jan 15, 2007, at 4:46 PM, Paul McNett wrote:
>> 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.
So the only way to get any new code into general release is to wait
for a 0.x release?
I guess that I thought that the purpose of stable was to have a
known release for which only bugfixes would be done. IOW, we release
0.7. We then start working on new stuff, and along the way discover
some things that were wrong. We fix them in the new code, and
backport those fixes to the 0.7 stable code. Then, after a while, we
release 0.7.1, which becomes the new stable branch.
We then continue working, and then discover more such problems. We
fix those in the current dev code, and also in the 0.7.1 stable code.
Later, we release 0.7.2, and that becomes the new stable branch.
I thought that the only changes we did not build into releases were
things that would clearly break old code, such as the dependence on
SQLite that we added in 0.7. But we're not talking about that here;
in fact, the only things we've done is fix a lot of the older code to
make it better, not incompatible.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
