phpwiki-talk

[Phpwiki-talk] Better use of CVS

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

I have a modest proposal:

Tag code as usable with the cvs tag -F "tagname" option.

This means we could selectively update the demo site so it's less likely 
to be broken by bugs.  Currently the demo and test sites both do a 
checkout of the current files in CVS; for the test site, we don't mind 
if it gets broken since that's what it's there for. But to have the demo 
site down is egg on our faces.

For the cron job that updates the demo site, it would do a cvs update on 
the tag we choose.

The downside to this is it's one more hassle for the devloper. A more 
low tech solution is to disable the cron job entirely, and update the 
demo site by hand periodically when new functionality is ready.

~swain

Re: [Phpwiki-talk] Better use of CVS

[Jeff D. <da...@da...>]

On Sat, 24 Aug 2002 17:19:52 -0400
Steve Wainstead <sw...@pa...> wrote:

> I have a modest proposal:
> 
> Tag code as usable with the cvs tag -F "tagname" option.

I don't know if others agree (they may well not), but
my personal preference is that developers refrain
from checking in known-to-be-non-functional code.

Personally, I have a personal PRCS repository set up which
I use to track my edits as I'm working on larger changes.
If modifications are made (by others) to the CVS code while
I'm working, I can use my PRCS repository to merge the mods
into my working files...
Then, when I finally get everything (more or less) working,
I check it in all at once, in an effort to leave the CVS
is a broken state for as short a time as possible.


Still, having the demo/test wikis update from a tagged set
is probably a good idea.

Another option is to only use the tag when the most recent
version of the file is known broken.
  cvs update -f -r WORKING_TEST
Will update each file to the version tagged WORKING_TEST,
if that tag exists for the file; otherwise it will update
to the most recent version of the file.



It might also be nice to make the test-wiki update script
accessible/runnable by all the developers, so
that when one makes changes he can immediately
update the test wiki and check to see that it still works.

Maybe (via CVS scripts) this can even be done automatically,
so that the test wiki is always in sync with CVS.

Sorry to be so scattered.  I've not yet consumed enough
coffee this Sunday morning...

Re: [Phpwiki-talk] Better use of CVS

[Reini U. <ru...@x-...>]

Jeff Dairiki schrieb:
> On Sat, 24 Aug 2002 17:19:52 -0400
> Steve Wainstead <sw...@pa...> wrote:
>>I have a modest proposal:
>>Tag code as usable with the cvs tag -F "tagname" option.
> 
> I don't know if others agree (they may well not), but
> my personal preference is that developers refrain
> from checking in known-to-be-non-functional code.
> 
> Personally, I have a personal PRCS repository set up which
> I use to track my edits as I'm working on larger changes.
> If modifications are made (by others) to the CVS code while
> I'm working, I can use my PRCS repository to merge the mods
> into my working files...
> Then, when I finally get everything (more or less) working,
> I check it in all at once, in an effort to leave the CVS
> is a broken state for as short a time as possible.
> 
> Still, having the demo/test wikis update from a tagged set
> is probably a good idea.
> 
> Another option is to only use the tag when the most recent
> version of the file is known broken.
>   cvs update -f -r WORKING_TEST
> Will update each file to the version tagged WORKING_TEST,
> if that tag exists for the file; otherwise it will update
> to the most recent version of the file.

It is a good idea to tag the stable from the unstable versions. My idea 
was to share my updates in flux with others to get immediate feedback on 
different setup's.
To attrack users to use this version I added some "cool" new features, 
before finishing the needed features.

Obviously a seperation between the new userauth and the latest additions 
and fixes which are independent would have been useful for you. But a 
lot of work for me. So I'm in a hurry to get it finished.

I'm for non-functional code, but I'm against broken code, of course.
But I can be persuaded.

This is my fault (as with the WikiUser typo lately). Normally I do an 
immediate cvs up on sf.net and check it. Thanks steve (and others) for 
fixing this.

> It might also be nice to make the test-wiki update script
> accessible/runnable by all the developers, so
> that when one makes changes he can immediately
> update the test wiki and check to see that it still works.
> 
> Maybe (via CVS scripts) this can even be done automatically,
> so that the test wiki is always in sync with CVS.

No need. A simple $ cvs up works for me.
Permissions are okay.

> Sorry to be so scattered.  I've not yet consumed enough
> coffee this Sunday morning...

And I didn't have my coffee this morning too. Thanks for reminding me.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/