Re: [phpBT-dev] PHPBT state

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

I may have answered your questions in my last email, but just in case... 
  I don't want to add anything that would cause database changes at this 
point, but any other patch would be fine.

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?
> 
> 
>>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?)
> 
> 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?
>