End of June would be great - I think it's a bit of a stretch since I'm
sure there are likely to be various issues cropping up.
I think that feature-wise we're ready for a 1.0, but in terms of
documentation, use-cases, stability, etc. I'm inclining towards an
intermediate release or two indicating that we're close so perhaps
1.0beta1 or 0.9.9?
Major feature development should be moved to a separate branch at
release time.
I'm also not inclined to promise a query system for 1.0. To do a
proper job I believe will require some additional changes to core
functionality (although hopefully not the data stores or DB) such as
keeping rough statistics over btree accesses for a query planner,
etc. I don't want to rush it.
So here's a proposal:
- Feature-freeze the current branch
- Focus entirely on testing and documentation through the end of June.
- Ensure that we've field tested the 0.9.1->1.0beta1 upgrade
- At the end of June, subject to Robert and I agreeing, we
release a 1.0beta1 and fork a branch for post 1.0 features
- We'll keep pushing on testing, etc and do monthly 1.0betaX
releases until we're happy.
Ian
On Jun 3, 2008, at 9:19 AM, V. Glenn Tarcea wrote:
Yup, I'll be helping on the docs. I'm running silent but watching the
emails. I'll have more time to help out with things in about 2 weeks
(end of
spring semester)
Is there a goal date for the next release?
Glenn
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian
Eslick
Sent: Monday, June 02, 2008 5:43 PM
To: Elephant bugs and development
Subject: Re: [elephant-devel] Re: unstable postmodern troubled..
Fantastic! Thanks for all the work on this. Now I have no excuse to
start the long list of little items necessary to get to a release...
The big areas are:
- Thread safety for all schema-related operations
- Test coverage
- Docs coverage
Some bugs I've seen and haven't been able to fix:
- Leslie's BDB bug on unstable
- BDB on AMD 64
Anything else?
I think Glenn was going to help us out with a little organization of
this list vis-a-vis documentation? The missing tests are roughly the
same as the missing doc sections, so we can come up with a list of
tests from that.
Anyone want to do a thread-safety review of the schema code? A fresh
pair of eyes is usually much better for this than the developer as
recent e-mails have shown. However, I'll take a first pass before too
long.
Thanks,
Ian
On Jun 2, 2008, at 4:47 PM, Alex Mizrahi wrote:
IE> Sounds like there is an issue with schema coherence (the class
object
IE> cache out of sync with the db in some way? I had some of these
tuning
IE> the BDB implementation).
i've found the issue -- postmodern backend creates its "system"
btrees
(like root, schema-table etc) in "fancy" way, so it cannot simply
deserialize
them if something in DB refers to it, so it depends on object cache.
but some tests call flush-instance-cache, so db-postmodern gets
broken.
i'm not sure what is the idea behind "special" btrees.. probably it
will
work fine without this special stuff, but i'd prefer not to touch
them :),
so i'll better specialize flush-instance-cache to ensure system
btrees
are cached after flush.
seems to be passing all tests now, ha!
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
