Re: [PHP] Chnage Management in PHP aka version control?
Well, I had similar problems at a previous job with SourceSafe as I'm having with CVS. I totally get and understand the concept of these systems, but they're still overly headachey to use. Maybe I DONT really get them. hah. I understand mostly how they work and the concept but it seems like another case of we don't need to make it easier because the people who use this are highly technical and they'll figure it out. Or as the gaming community might say lrn2configure noob! For now, CVS works fine for us. But it still feels like we're using a go-cart with no engine. If we push it to the top of the hill, we can coast down the other side and even steer and stop if we want... but it feels incomplete usage and functionality-wise. Oh well, project for another day. Thanks for the input! -TG = = = Original message = = = On Wed, July 5, 2006 10:40 am, [EMAIL PROTECTED] wrote: I don't know about you, Jay, but all we really want to do is keep a record of revisions and be able to 'diff' between them and have the files lock so if someone tries to open the file and it's already open, that the user is alerted and allowed to open read-only if they desire. I *much* prefer the CVS/subversion paradigm of concurrent changes, but if the above is what you want, perhaps you should look into SourceSafe. NOTE: SourceSafe in the 80s on Mac PPC *ate* two of my projects when goofballs added .doc files as text. I'll never ever ever use this product again, no matter how many people tell me it's been fixed. YMMV ___ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Chnage Management in PHP aka version control?
[EMAIL PROTECTED] wrote: Well, I had similar problems at a previous job with SourceSafe as I'm having with CVS. I totally get and understand the concept of these systems, but they're still overly headachey to use. Maybe I DONT really get them. hah. I understand mostly how they work and the concept but it seems like another case of we don't need to make it easier because the people who use this are highly technical and they'll figure it out. Or as the gaming community might say lrn2configure noob! For now, CVS works fine for us. But it still feels like we're using a go-cart with no engine. If we push it to the top of the hill, we can coast down the other side and even steer and stop if we want... but it feels incomplete usage and functionality-wise. $ cvs -q crowbar or $ cvs -q magicwand or $ cvs -q dowhatimean unfortunately that's only in my imagination :-P Oh well, project for another day. Thanks for the input! -TG = = = Original message = = = On Wed, July 5, 2006 10:40 am, [EMAIL PROTECTED] wrote: I don't know about you, Jay, but all we really want to do is keep a record of revisions and be able to 'diff' between them and have the files lock so if someone tries to open the file and it's already open, that the user is alerted and allowed to open read-only if they desire. I *much* prefer the CVS/subversion paradigm of concurrent changes, but if the above is what you want, perhaps you should look into SourceSafe. NOTE: SourceSafe in the 80s on Mac PPC *ate* two of my projects when goofballs added .doc files as text. I'll never ever ever use this product again, no matter how many people tell me it's been fixed. YMMV ___ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Chnage Management in PHP aka version control?
On Wed, July 5, 2006 10:40 am, [EMAIL PROTECTED] wrote: I don't know about you, Jay, but all we really want to do is keep a record of revisions and be able to 'diff' between them and have the files lock so if someone tries to open the file and it's already open, that the user is alerted and allowed to open read-only if they desire. I *much* prefer the CVS/subversion paradigm of concurrent changes, but if the above is what you want, perhaps you should look into SourceSafe. NOTE: SourceSafe in the 80s on Mac PPC *ate* two of my projects when goofballs added .doc files as text. I'll never ever ever use this product again, no matter how many people tell me it's been fixed. YMMV -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Chnage Management in PHP aka version control?
By 'change management' do you mean something like version control software? CVS, Subversion, etc? We use CVS at work and tried setting up Subversion at one point. I don't know, maybe we're all a bunch of retarded monkies here or maybe both systems are just overly complicated, but I don't like either of them. We have a working CVS setup right now, but it's not integrated with Zend Studio (which would be nice) and we couldn't get Subversion to integrate nicely either so we're just sticking with CVS for now. Sad to say, but the easiest, most user-transparent and still functional file locking system I've ever used was what's built into Microsoft Office applications where it'll tell you This file is already open, would you like to open read-only and be alerted when you can write to it?. But that doesn't contain any version control (unless you turn on change tracking in some MS Office apps). I don't know about you, Jay, but all we really want to do is keep a record of revisions and be able to 'diff' between them and have the files lock so if someone tries to open the file and it's already open, that the user is alerted and allowed to open read-only if they desire. What kind of features are you looking for in a 'change management' software package? Maybe someone can recommend an app or two that will fit yours (and maybe our) needs. -TG = = = Original message = = = I have been searching and digging for a PHP based change management application but have had little luck. Can anyone make a recommendation? Thanks! ___ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Chnage Management in PHP aka version control?
[snip] By 'change management' do you mean something like version control software? CVS, Subversion, etc? [/snip] Sort of, but broader. More like a log. Maybe I should build it myself. For instance we have a server. That server requires that PHP be recompiled with additional features. I would like to record the change, and maybe even plan for the change. I would need a baseline for PHP and then be able to setup maintenance to be done or maintenance that was performed. That way, if something goes kablooey (ka-bloo-E) we can roll back to where things were prior to the change. Or we could record that the power supply failed on x and was replaced on y with xyz power supply. Etc. Make more sense? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Chnage Management in PHP aka version control?
[EMAIL PROTECTED] wrote: By 'change management' do you mean something like version control software? CVS, Subversion, etc? We use CVS at work and tried setting up Subversion at one point. I don't know, maybe we're all a bunch of retarded monkies here or maybe both systems are just overly complicated, but I don't like either of them. We have a working CVS setup right now, but it's not integrated with Zend Studio (which would be nice) and we couldn't get Subversion to integrate nicely either so we're just sticking with CVS for now. Sad to say, but the easiest, most user-transparent and still functional file locking system I've ever used was what's built into Microsoft Office applications where it'll tell you This file is already open, would you like to open read-only and be alerted when you can write to it?. But that doesn't contain any version control (unless you turn on change tracking in some MS Office apps). I don't know about you, Jay, but all we really want to do is keep a record of revisions and be able to 'diff' between them and have the files lock so if someone tries to open the file and it's already open, that the user is alerted and allowed to open read-only if they desire. What kind of features are you looking for in a 'change management' software package? Maybe someone can recommend an app or two that will fit yours (and maybe our) needs. -TG = = = Original message = = = I have been searching and digging for a PHP based change management application but have had little luck. Can anyone make a recommendation? Thanks! ___ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com. His message seemed to indicate that he wanted a version control application WRITTEN in PHP, not that supported PHP. Regards, Adam. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Chnage Management in PHP aka version control?
On Wed, 2006-07-05 at 10:50 -0500, Jay Blanchard wrote: For instance we have a server. That server requires that PHP be recompiled with additional features. I would like to record the change, and maybe even plan for the change. I would need a baseline for PHP and then be able to setup maintenance to be done or maintenance that was performed. That way, if something goes kablooey (ka-bloo-E) we can roll back to where things were prior to the change. Way back when, I wrote something like that. It sucked, but was really easy to write very quickly. The hardest part was the DB design... I would suggest looking through some of the projects on Sourceforge andd freshmeat though, there is bound to be a useful app there. On the other hand you could just roll out a BugZilla Helpdesk from Mozilla, but that is designed for a huge company with many servers, desktops etc. You could use our framework to roll out a solution in a few hours, but you would have to learn it first... sigh I agree with the first reply - roll your own, its less stress than you think! --Paul All Email originating from UWC is covered by disclaimer http://www.uwc.ac.za/portal/uwc2006/content/mail_disclaimer/index.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
