Post by Patrick K. O'BrienPost by Matthew ScottPat,
I am going to go ahead and merge the store35 and bugfixes branches to trunk.
I'll be merging trunk back to bugfixes, so if you run into any problems
with your apps due to the upgrade to Durus 3.5 in schevo.store, we can
work on fixing them in the bugfixes branch.
Awesome. It would be nice to get a release out this week as well.
Alright. I'm crunched through Thursday, then Friday will probably be a
half day for me since it's my son's birthday.
But the stuff I'm "crunching" on is the async branch primarily. When we
do a release, I'll merge in the work done in that branch, so we can at
least release that stuff as being in an alpha state. I'd also like to
merge in gtk-support as an alpha release too, if you're comfortable with
that.
There are a few packages I've removed in the async branch since they are
receiving no "love" and have fallen out of sync with trunk. Unless
otherwise argued, they will be removed from trunk when async is merged
in: SchevoGears, SchevoNufox, SchevoPylons.
Finally, if you could review, and perhaps tweak, the "evolve" branch
this week, that would be a good thing to merge in as well.
It would make the release well-rounded, with lots of new goodies:
* Numerous improvements and bugfixes to core engine
* In-process GTK navigator and widget set
* In-process and client/server PyQt4 navigator and widget set
* Inter-version schema evolution
* Support for synchronized multi-threaded use of Schevo databases
A more concise changeset should be feasible given that we have been a
lot better about working in branches, and making merges to trunk more
atomic.
--
Matthew Scott
***@springfieldtech.com