Re: [phpBT-dev] PHPBT state

[Ben C. <php...@be...>]

Ulf Erikson wrote:
> * Benjamin Curtis [2005-05-14 12:54]:
> 
>>I think the only reason the patches haven't been applied is that the
>>time just slipped by me.  To correct that, I've added you as a developer
>>to the project so you can add your patches yourself. :)  Changes should
>>be applied to the HEAD.
> 
> 
> What a dirty trick! ;-) It is soo much easier to complain than to fix it
> myself.. but I will try to look at it, next week or so. 
> 
> Could you at least give a hint on what patches are okay to add now and
> what can better wait until after 1.0?
> 

Heh, good working tossing it back. :)

> 
>>I don't have a desire to add any more features before 1.0, I just want
>>work out any remaining bugs left over from the RCs.
> 
> 
> Sounds wise. I guess this means that it is too late for changes to
> things such as the database structure, the main queries and the
> translatable strings, etc.? That would disqualify most of my patches for
> now.. Another thing, some of my changes are for MySQL only. Who can help
> with similar changes for the other database types? (do you normally
> commit changes for one type only and add the others later? or do you
> wait until changes for all types can be done at once?)

Any of the patches you already made that add pieces of functionality are
fine to add.  I'd rather not put in patches that are for mysql only,
though.  I can help with making them work with postgres, but I'm sorely
lacking in time lately.

> 
> Do you have a list of blocking bugs for 1.0? Why was RC5 named RC5 and
> not 1.0? Are those issues addressed now? What is needed for RC6 and/or
> 1.0? How can I best help reach there?
> 

Actually, I don't have a list of blocking issues.  I think the code is
basically ready to go for a 1.0 release.  Of course, I could be
forgetting something. :)  I'd rather do 1.0 than RC6.  I think the only
thing holding me back is really someone (besides me) giving me the
thumbs up that the upgrade script works just fine for a 0.9.x database.