phpbt-dev

[phpBT-dev] PHPBT state

[Matthieu P. <mat...@dp...>]

    Hello,

What is the sate of PHPBT. It has been in rc5 for months and nothing 
seems to change. Is a 1.0final planned ?

   Thanks,

-- 
Matthieu PUPAT
Digital Product Simulation
Téléphone : +33 (0)5 62 12 03 87 (interne 7013)
Fax : +33 (0)5 62 12 03 89

Re: [phpBT-dev] PHPBT state

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

The current goal is to get 1.0 released in July.

Matthieu Pupat wrote:
>    Hello,
> 
> What is the sate of PHPBT. It has been in rc5 for months and nothing
> seems to change. Is a 1.0final planned ?
> 
>   Thanks,
> 

Re: [phpBT-dev] PHPBT state

[Ulf E. <ulf...@fa...>]

Benjamin,

Could you please update the RoadMap to show what features actually went 
into 0.9, what curently sit in 1.0rc and what you plan to include for 
1.0final? I'd try to help with a thing or two if I knew where you're 
going.. til now I have not heard much about if/when (or why not) my 
earlier set of patches will get included. The good thing with this slow 
pace is that they probably still apply ;-)

/Ulf

* Benjamin Curtis [2005-05-12 15:26]:
> The current goal is to get 1.0 released in July.
> 
> Matthieu Pupat wrote:
> 
>>   Hello,
>>
>>What is the sate of PHPBT. It has been in rc5 for months and nothing
>>seems to change. Is a 1.0final planned ?
>>
>>  Thanks,

Re: [phpBT-dev] PHPBT state

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

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.

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.

Ulf Erikson wrote:
> Benjamin,
> 
> Could you please update the RoadMap to show what features actually went
> into 0.9, what curently sit in 1.0rc and what you plan to include for
> 1.0final? I'd try to help with a thing or two if I knew where you're
> going.. til now I have not heard much about if/when (or why not) my
> earlier set of patches will get included. The good thing with this slow
> pace is that they probably still apply ;-)
> 
> /Ulf
> 
> * Benjamin Curtis [2005-05-12 15:26]:
> 
>> The current goal is to get 1.0 released in July.
>>
>> Matthieu Pupat wrote:
>>
>>>   Hello,
>>>
>>> What is the sate of PHPBT. It has been in rc5 for months and nothing
>>> seems to change. Is a 1.0final planned ?
>>>
>>>  Thanks,
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> phpbt-dev mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbt-dev

Re: [phpBT-dev] PHPBT state

[Ulf E. <ulf...@fa...>]

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

-- 
Ulf

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.

Re: [phpBT-dev] PHPBT state

[Ulf E. <ulf...@fa...>]

* Ben Curtis [2005-05-19 17:34]:
> 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.

Great. I'll take a look at my old feature patches as well. By the end of
the week, I hope.

> > 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.

Hmm.. There have actually been a number of tumbs down for installer and
upgrade scripts lately.. I suspect that this partly could be due to
newer versions of php and/or mysql. I'll try to come up with something
there (including the error and warning log we talked about earlier).

How about a wiki page to collect information about systems where install
and upgrade work or fail (and error messages, in case of failure)? If
you write a short description on how to test this anyone can fill in his
system specifics and results. And, if you write the first entry everyone
will include as much information. I wouldn't know what parameters are of
importance ;-)

/Ulf

Re: [phpBT-dev] PHPBT state

[Ulf E. <ulf...@fa...>]

* Ulf Erikson [2005-05-23 16:42]:
> * Ben Curtis [2005-05-19 17:34]:
>>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.
> 
> Hmm.. There have actually been a number of tumbs down for installer and
> upgrade scripts lately.. I suspect that this partly could be due to
> newer versions of php and/or mysql. I'll try to come up with something
> there (including the error and warning log we talked about earlier).

I have updated PEAR and DB in CVS now, as well as changed all error 
checking to use DB::isError. For me this was enough to get phpBT running 
with PHP5 earlier (can't test that right now, but it still works with 
PHP4 here).

Logs for install and upgrade will come later. Probably something along 
these lines:
http://sourceforge.net/mailarchive/message.php?msg_id=11121869

Let me know if I managed to fix or break something ;-)

/Ulf

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

[phpBT-dev] phpBT future

[Ulf E. <ulf...@fa...>]

* Ben Curtis [2005-06-05 00:02]:
> 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.

That's fine.

What are your plans after the 1.0 release? Will you make a branch for 
security updates, new translations, and additional database schemas? and 
then accept more experimental patches to head again? or do you do the 
experiments on a branch?


After the release, any chance that you can help sketch on what tables 
and fields would be needed to implement things such as:
   * User permission levels:
http://sourceforge.net/mailarchive/message.php?msg_id=10866429
   * Work Flow
http://sourceforge.net/mailarchive/message.php?msg_id=11038314
   * Customizable Fields:
http://sourceforge.net/forum/message.php?msg_id=2118034

I'd be interested in trying to realize those features, but I am not able 
to make a neat design alone..

/Ulf

Re: [phpBT-dev] phpBT future

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

After 1.0 is released, and after there's a bit of stabilization (I'm
going to assume there will be bugs to fix that are discovered right
after the release), I'll create a 1.0 branch so that new stuff can be
added to the HEAD.

Actually, I'm planning on moving to Subversion, so I may not make the
branch, but instead just start new development in the new repository.
In fact, I'm planning on going whole hog with the second-system syndrome
and starting from scratch with a 2.0 track.  The code is starting to
make me cringe, and I've learned a lot with Tesly and other projects
that I'd like to use for this project.

What remains to be seen is just how motivated I'll be to work on that,
though.  Recently I've been much more interested in working on Tesly,
and there are a gazillion other bug tracking packages, so I question
whether the effort of continuing to work on phpBT is worth it.  For the
moment, though, the momentum of getting 1.0 released is carrying me
along, and maybe the chance to start from scratch will keep it interesting.

Certainly after the 1.0 release I'll be happy to provide input on how to
implement the features you mentioned and the others posted at the
sourceforge site.

Ulf Erikson wrote:
> * Ben Curtis [2005-06-05 00:02]:
> 
>> 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.
> 
> 
> That's fine.
> 
> What are your plans after the 1.0 release? Will you make a branch for
> security updates, new translations, and additional database schemas? and
> then accept more experimental patches to head again? or do you do the
> experiments on a branch?
> 
> 
> After the release, any chance that you can help sketch on what tables
> and fields would be needed to implement things such as:
>   * User permission levels:
> http://sourceforge.net/mailarchive/message.php?msg_id=10866429
>   * Work Flow
> http://sourceforge.net/mailarchive/message.php?msg_id=11038314
>   * Customizable Fields:
> http://sourceforge.net/forum/message.php?msg_id=2118034
> 
> I'd be interested in trying to realize those features, but I am not able
> to make a neat design alone..
> 
> /Ulf
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
> shotput
> a projector? How fast can you ride your desk chair down the office luge
> track?
> If you want to score the big prize, get to know the little guy.  Play to
> win an NEC 61" plasma display: http://www.necitguy.com/?r=20
> _______________________________________________
> phpbt-dev mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbt-dev