phpwiki-talk

[Phpwiki-talk] 1.3.3; and towards 1.4

[Steve W. <sw...@pa...>]

About two or three weeks ago I asked if we were ready for a new release 
on the 1.3 branch; Jeff, you said you and Carsten were busy with a 
serious refactoring. If that's settled down for now I'd like to put out 
1.3.3 before the week is out.

While I had goals for 1.4, the coders on the project had plenty of 
itches to scratch, and by letting them scratch away we've acheived a lot 
of new features, many never listed in the Task List. I have been very 
happy with this. You folks have done a really amazing job.


We should probably nail down that which needs finishing before we do a 
1.4 release (as started on 
http://phpwiki.sourceforge.net/phpwiki/Release1.4), and I'm sorry to say 
the first thing that comes to my mind is user authentication. I feel 
like Frodo climbing towards Cirith Ungol.

I think I'd like to tackle the flat file database, since I haven't 
written any code for the project since... since I can't remember when! 
But this needs doing. For some people it's the only way.

If the new parse engine is integrated and it does not support the old 
markup, we will indeed need a conversion tool since all the PhpWiki 
sites on SF will not port.

Carsten, not to publicly flog you, but one of the reasons I've fallen 
behind on the CVS list is because of the volume of checkins you make. 
(Oh that all open source projects had such a complaint! :-) I have been 
wondering: if you make the same change to 10 different files, do you 
check in each one individually? It looked that way to me in the past. I 
haven't tried coding PhpWiki in ProjectBuilder yet, and it wouldn't 
suprise me if there were no way to do this (check in ten files at once). 
We could teach you to check in from the Terminal app and possibly save 
you a lot of work.

cheers
~swain

not splitting up commits (was Re: [Phpwiki-talk] 1.3.3; and towards 1.4)

[Carsten K. <car...@ma...>]

Hi Steve,

I noticed Project Builder does split up cvs commits by directory, even if 
I only do one commit with files highlighted across multiple directories. 
Sometimes I do commit from the command-line, but for me doing multiple 
commits is quicker in the gui especially when there are other scattered 
modified files which are not ready to commit yet (or will never be 
committed).

Honestly I had been making the effort to intentionally split up commits 
when the comments are a little different for each of the files, so that 
inspection of cvs logs (hidden away as Get Info in Project Builder's 
Project menu) for individual files describe only the changes to that 
particular file.

So to reduce the number of commit emails I'm happy to use the shell more 
often when doing commits, and to avoid splitting up commits just for the 
sake of comments, unless say, it's very significant change to code and not 
just css or html template files.

Thanks for bringing this up.

:-) Carsten


On Thursday, February 21, 2002, at 10:40  am, Steve Wainstead wrote:

>
> Carsten, not to publicly flog you, but one of the reasons I've fallen 
> behind on the CVS list is because of the volume of checkins you make. (Oh 
> that all open source projects had such a complaint! :-) I have been 
> wondering: if you make the same change to 10 different files, do you 
> check in each one individually? It looked that way to me in the past. I 
> haven't tried coding PhpWiki in ProjectBuilder yet, and it wouldn't 
> suprise me if there were no way to do this (check in ten files at once). 
> We could teach you to check in from the Terminal app and possibly save 
> you a lot of work.
>
> cheers
> ~swain

Re: not splitting up commits (was Re: [Phpwiki-talk] 1.3.3; and towards 1.4)

[Steve W. <sw...@pa...>]

No problem... if you want to continue the way you do it (i.e. you find 
it more useful) I can just create a new mail filter to jam the mail from 
  phpwiki-checkins to a different folder. Which I will do anyhow. :-)

~swain

Carsten Klapp wrote:
> 
> Hi Steve,
> 
> I noticed Project Builder does split up cvs commits by directory, even 
> if I only do one commit with files highlighted across multiple 
> directories. Sometimes I do commit from the command-line, but for me 
> doing multiple commits is quicker in the gui especially when there are 
> other scattered modified files which are not ready to commit yet (or 
> will never be committed).
> 
> Honestly I had been making the effort to intentionally split up commits 
> when the comments are a little different for each of the files, so that 
> inspection of cvs logs (hidden away as Get Info in Project Builder's 
> Project menu) for individual files describe only the changes to that 
> particular file.
> 
> So to reduce the number of commit emails I'm happy to use the shell more 
> often when doing commits, and to avoid splitting up commits just for the 
> sake of comments, unless say, it's very significant change to code and 
> not just css or html template files.
> 
> Thanks for bringing this up.
> 
> :-) Carsten
> 
> 
> On Thursday, February 21, 2002, at 10:40  am, Steve Wainstead wrote:
> 
>>
>> Carsten, not to publicly flog you, but one of the reasons I've fallen 
>> behind on the CVS list is because of the volume of checkins you make. 
>> (Oh that all open source projects had such a complaint! :-) I have 
>> been wondering: if you make the same change to 10 different files, do 
>> you check in each one individually? It looked that way to me in the 
>> past. I haven't tried coding PhpWiki in ProjectBuilder yet, and it 
>> wouldn't suprise me if there were no way to do this (check in ten 
>> files at once). We could teach you to check in from the Terminal app 
>> and possibly save you a lot of work.
>>
>> cheers
>> ~swain
> 
> 
> 
>