Re: [PDO] next steps
| From: | Samuel ROZE | Date: | Wed, 28 Oct 2009 14:54:18 +0000 |
| Subject: | Re: [PDO] next steps | ||
| References: | 1 | Groups: | php.pdo |
| Request: | Send a blank email to pdo+get-241@lists.php.net to get a copy of this message | ||
Hi Lukas,
I agree your game - work - plan. It must be good to fix the bugs instead
of developing others functionalities. I can fix (or minus verifiy) some
bugs however I haven't got a SVN account, so I can not change the status
to Verified for example. I just can't modify bugs...
Thanks for you job !
Samuel.
Le mardi 27 octobre 2009 à 12:03 +0100, Lukas Kahwe Smith a écrit :
> Aloha,
>
> So I think the next steps could look like this:
> 1) We try to go through the open bugs, close as many as possible. We
> also try to add tests for these bugs potentially start adding
> additional ones. We also review what sort of documentation is missing.
> Finally we run the current test suite against the different RDBMS that
> are supported. While we are doing this we use the wiki to note down
> issues we see in the current PDO API, architecture or feature set.
>
> 2) Based on the findings from 1) we ponder how we can evolve PDO. Do
> we need to do a major new version or can we get by with a minor update?
>
> ---
>
> I assume that step one would take at least until the end of the year,
> depending on how things go. There is room for everyone to do things in
> step 1), regardless of if you can code C or not. Regardless of if you
> have RDBMS xyz installed or not.
>
> What do you guys think about this game plan?
>
> If we can agree on this plan (or some variation) ideally people would
> commit to what part of step 1) they want to work on, just so that we
> know what all aspects are addressed and that all drivers have someone
> looking into things.
>
> regards,
> Lukas Kahwe Smith
> mls@pooteeweet.org
>
>
>
>