Hi Davey, 

Sorry, I have never seen any proposal or code from you regarding an ORM.
We can't even keep up with the proposals that come in using our proposal
process -- something submitted off-list is just not going to be
considered.

Have you seen the proposals we are implementing here:
http://framework.zend.com/wiki/display/ZFPROP/Zend_Db_Table+-+Fabien+Mar
ty%2C+Eugene+Panaitov%2C+Simon+Mundy
http://framework.zend.com/wiki/display/ZFPROP/Zend_Db_Table+relationship
s+-+Bill+Karwin

We aren't doing an ORM right now.  A true ORM is far too ambitious for
the time and resources we have available.  But we will have some nice
new features that will make database programming more object-oriented.
Simon and I are working on that now in a branch named "DbTable-09".
Feel free to check it out (followups to [EMAIL PROTECTED] please).

Regarding the future, of course there will be releases after 1.0.  That
has always been the intention.  If features are delayed they won't be
delayed for long.  We at Zend have many ideas for components for the
Zend Framework, and so does the community.  So there will be life
following 1.0!

We must release a stable 1.0 product in a timely way.  That is simply a
requirement of this project.  We can't continue to add more components
and features prior to 1.0, otherwise we will never finish 1.0.  But of
course there will be opportunity to add more components and features in
the next release after 1.0.  There are innumerable great ideas, and we
will do them in subsequent releases.

Regards,
Bill Karwin

> -----Original Message-----
> From: Davey Shafik [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 02, 2007 1:31 AM
> To: Bill Karwin
> Cc: [email protected]
> Subject: Re: [fw-general] Zend Framework 0.9 code freeze schedule
> 
> Bill,
> 
> It's great we're heading towards 0.9 and as such 'beta' status,
> however, there is still one major feature we are sorely lacking IMO -
> ORM
> 
> I have repeatedly submitted (off-list) feature complete, easy to use
> ORM solutions based
> ON TOP of Zend_Db_Table/Zend_Db_Select, which have gotten lost in the
> shuffle.
> 
> Unfortunately, this code has since become defunct as the
> Zend_Db_Table/Zend_Db_Select
> have changed, making the code no longer work, but I am confident I
> could resurrect it pretty
> swiftly.
> 
> Because of the use of Zend_Db_Table/Zend_Db_Select within the ORM,
> there is actually very
> little QA needed, its essentially just a smart API wrapper at that
> point :)
> 
> The only feature I had yet to implement, is lazy-loading (using
> JOINs) of known relationships, reducing
> the number of queries, and flattening the result object - this is
> pretty easy, I just never got to it :)
> 
> Finally, I know that we currently have a release *schedule* and so
> 0.9 is followed by 1.0, but will we in the future
> go to 1.10, 1.11  etc when we hit 1.9 or whatever.
> 
> - Davey
> 
> 
> On Mar 2, 2007, at 2:48 AM, Bill Karwin wrote:
> 
> > Hi everyone,
> >
> > Our schedule calls for a code-freeze on March 15, which is in two
> > weeks
> > from today.  Let's talk a bit about the process for the Beta
release.
> >
> > The objective for the Beta release is that we are *feature
complete*.
> > That means that any feature ideas for ZF components will have to
wait
> > until after 1.0 to be included in the product.
> >
> > We plan to have some number of Beta Refresh Releases, e.g. 0.9.1,
> > 0.9.2,
> > etc., about once every two weeks.  These should include bug fixes
and
> > improvements to documentation and tests, but no new features.
> >
> > Any files that are still in incubator in ZF 0.9.0 will probably
> > stay in
> > incubator until after 1.0.  We may make some exceptions in a Beta
> > Refresh, but they will be few and they will be evaluated carefully.
> >
> > The incubator will be included in ZF 0.9.0, but not in subsequent
> > releases.  After that release, files in the incubator will be
> > accessible
> > only via subversion and nightly snapshots of svn.
> >
> > When we feel the Beta Release and Beta Refresh Releases have served
> > their purpose and the product seems stable and complete, we will
> > make a
> > 1.0 Release Candidate.  We may make additional 1.0 Release
Candidates,
> > about once every two weeks, until we feel it is ready to be called
> > a 1.0
> > General Release.
> >
> > So if we assume two Beta Releases and two 1.0 Release Candidates,
> > lasting two weeks each, that means we estimate the first 1.0 RC at
> > approximately April 12, and the final General Release at
approximately
> > May 10.  If we can, we will make this date earlier.
> >
> > We have seen a steady supply of good ideas coming in, and we regret
> > that
> > we cannot include all of them in Zend Framework 1.0.  But there
> > will be
> > opportunities after 1.0 to add more technology solutions.
> >
> > Regards,
> > Bill Karwin
> >

Reply via email to