Re: [mbravo@tag-ltd.spb.ru: Re: [phpBT-dev] Postgres SQL problems]

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

On Sat, Aug 25, 2001 at 03:34:15AM +0400, Michael Bravo wrote:
> On Fri, 24 Aug 2001 15:12:59 -0700
> Ben Curtis <php...@be...> wrote:
> 
> [lots skipped]
> > for just dev staff might be useful.  Of course, in this case, they
> > probably _do_ have some way to track bugs on their v2, but it might be
> > nice to have that flexibility in phpbt.  Thoughts?
> [the followup about despot settings considered]
> 
> Well then, it seems that the consensus (heh, between the two of us so far :) ) is that we go ahead and implement the whole stuff:

Heh, then we have a simple majority. :)

> 
> - on/off self-registration
> - user groups
> - project permissions (though simple, only yes/no visibility) per user AND per group, with intersection
> 
> out of this thread note: I received a CVS commit notice from sourceforge's tracker about a closing bug with the loss of component id, but it didn't show up in my working copy no matter how many updates I did (-A tried). Any ideas?

Ah, yes, that change was made on a branch (phpbt-0_2_1p) which was branched from the tag from the last release, phpbt-0_2_1.  That's why it's not showing up in your checkout, which is from the HEAD.  You can checkout a copy of the branch with cvs co -r phpbt-0_2_1p -d <dest_dir> phpbt.  I made the 0.2.2 release off that branch and tagged it phpbt-0_2_2.  Further patches for 0.2.x would also be made on that branch since there are significant changes in the current HEAD.