On Dec 20, 2006, at 11:11 AM, Nate Lowrie wrote:
> Since we are adding so much stuff, I'd be willing to bet it got
> glossed over and overlooked. Especially if another problem/request
> comes up that grabs your attention. Then you forget about it. I have
> done that a number of times.
Not with the stable branch. I do that all the time with dev; that's
normal for the crazy world where things are always being changed. But
the only things that should ever be copied to stable are bug fixes
and the like; no new stuff should be introduced.
The AppWizard stuff was too tough for me to sort out, so I'm adding
in some of the changes, such as including PKs in the UI and sorting
fields, but I've spent the better part of the morning testing this
under both regular Python and the runtime engine, so I'm confident
that it will not cause problems.
> Maybe after a certain point we need to move the trunk into a testing
> branch as a release candidate until it is tested.
What we've been doing is after we have accumulated enough changes
and before we start any more major ones, we decide to create a
release. At that point, no new stuff is added, and we run everything
we can to find any remaining issues. Once we're satisfied that it's
ready, we create the release. Paul does all the Subversion tagging,
and then we move that version into the stable branch.
Once it's in the stable branch, only bug fixes should be applied to
it. New features only go into the dev trunk.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
