I've installed Tortoise and hooked up a directory to the trunk in SVN. From what I can read on the WIKI, this is the code for the latest stable build (i.e. 4.2). Thinking that bug fixes would be included in the trunk that might not be included in the distribution package, I've been watching and updating my download directory.
I have seen literally hundreds of files modified/added/deleted in the past three weeks. My question is, are there really that many bug fixes in the stable release? Or am I hooked up to the wrong place in SVN? Here is what I used (from the WIKI):
Can anyone verify that I am actually reading the location of the stable source code for 4.2?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-02-22
Darrel, you're in the right place, but with slight inaccurate expectations.
Once a 'stable' version is released, bug fixes are provided in one or two ways (occasionally both):
As Patches (in the Tracker -> Patches section here), if they can be provided as simple file replaces.
As updates to the trunk in SVN.
However, the trunk is also the development code for the next release (4.2.1) so it does include a lot of changes other than just bug fixes. these will included new features, code improvements, tidying up, etc etc etc.
Because of this you need to think carefully about using svn for your production site. A number of us do, in order to test all the new developments in a live environment. But it does come with risks. From time to time something will be changed that breaks the system (i.e. reasonably serious bugs). I've certainly had my site down as a result on more than one occasion. However, by providing such a test environment, the developers respond VERY quickly to our problem reports, thus minimising the risk. Personally, I'm very happy to "live on the edge" and take the risk. I get a lot of pleasure from being involved in the development process, even though I am unable to do any coding.
You can also minimise your own risks by:
1 - keep a rigorous schedule of backups (your whole index folder AND your DB tables)
2 - update svn VERY often. I try to aim for a minimum of 3-4 times per week, but daily if I can. This also means you have to manage fewer file changes in any one session.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would have thought that the development would have taken place in a branch and not on top of the code for the stable release. But I've been in the software development business long enough to know that there is no standard for this.
So, if I want a copy of the stable 4.2 release code with all the fixes (since I have run into a few of the bugs that have been discussed), where do I go? Are all the bug fixes in the patches section? Do those patches always go on top of the distribution package?
Regarding running this in production, I do not. This is more of an academic exercise for me. I download to my own server and test things out and see what mods I can make to deal with some of the issues that are brought up. Takes me back to my developer days and keeps me somewhat fresh. My last addition was long ago when I added the simplyred, simplyblue themes and custom menu items way back when. They have since been incorporated into the mainstream.
Darrel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
<<I would have thought that the development would have taken place in a branch and not on top of the code for the stable release.>>
We create branches for major development work, and merge these back in to the trunk. Since many of the developers run their live sites using the trunk, there is a certain incentive to keep it stable and bug-free ;-)
<<if I want a copy of the stable 4.2 release code with all the fixes>>
There is no such thing. The "4.2 tag" in SVN is fixed, and will not change. It is a permanent record of what went in to 4.2.
If you want 4.2+all fixes, then you'll have to accept the trunk, which is 4.2+all fixes+all new bugs.
<<Are all the bug fixes in the patches section?>>
No. Patches are only created for major bugs that can't wait for a version release, or for security patches to older versions.
I would prefer to see a frequent release cycle than a proliferation of patches.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Personally I prefer using the tarball instead of an SVN client. I just download, extract the folder and upload after deleting the themes and mods I don't want and the index and media folders. After uploading I rename the extracted folder so I'm ready for the next time and I always have a previous install ready if there is some major bug. It's a bit more time consuming but I absolutely HATE Tortoise and all those extra files that need to be filtered in my ftp client.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It all boils down to one thing really. All SVN clients are written with developers in mind. They just aren't meant for end-users and they aren't tester-friendly either. Even a developer has to jump through a couple of hoops to upload new code to a live server for testing. I don't know why nobody has developed a client with ftp capability. It would make things so much simpler.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I only update to the latest SVN when I have to. Like Stew, I find Tortoise a pain and download the tarball. I use Beyond Compare from http://www.scootersoftware.com/ It's a file/folder compare/merge/sync system with ftp. It's not my main ftp client but it is ideal for updating a few files amongst many. You have to work out your own process and set up your own filters but I have used it for several years on several websites and found it pretty me-proof.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you run a remote server, but a local copy of the SVN code,
SmartSVN from SYNTEVO.com is an easy to use SVN client. Fast to setup and fast to syncSVN.
SYNTEVO.com also has SmartSynchronize for using your local directory to ftp and sync with the remote server.
Both have fully functioning demo-mode that lacks only some developer tools - FREE and both programs are crossplatform, runnig on Window OS, Linux and Mac OS.
Easy-Peasy (and I don't work for the company).
-stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried SmartSVN and it actually does seem to be better than Tortoise. I haven't quite figured out how to configure it to ignore the stuff I don't want but it's pretty easy to select files and use Tools/Backup to export them to a folder for upload.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've installed Tortoise and hooked up a directory to the trunk in SVN. From what I can read on the WIKI, this is the code for the latest stable build (i.e. 4.2). Thinking that bug fixes would be included in the trunk that might not be included in the distribution package, I've been watching and updating my download directory.
I have seen literally hundreds of files modified/added/deleted in the past three weeks. My question is, are there really that many bug fixes in the stable release? Or am I hooked up to the wrong place in SVN? Here is what I used (from the WIKI):
https://phpgedview.svn.sourceforge.net/svnroot/phpgedview/trunk/phpGedView
Can anyone verify that I am actually reading the location of the stable source code for 4.2?
Darrel, you're in the right place, but with slight inaccurate expectations.
Once a 'stable' version is released, bug fixes are provided in one or two ways (occasionally both):
As Patches (in the Tracker -> Patches section here), if they can be provided as simple file replaces.
As updates to the trunk in SVN.
However, the trunk is also the development code for the next release (4.2.1) so it does include a lot of changes other than just bug fixes. these will included new features, code improvements, tidying up, etc etc etc.
Because of this you need to think carefully about using svn for your production site. A number of us do, in order to test all the new developments in a live environment. But it does come with risks. From time to time something will be changed that breaks the system (i.e. reasonably serious bugs). I've certainly had my site down as a result on more than one occasion. However, by providing such a test environment, the developers respond VERY quickly to our problem reports, thus minimising the risk. Personally, I'm very happy to "live on the edge" and take the risk. I get a lot of pleasure from being involved in the development process, even though I am unable to do any coding.
You can also minimise your own risks by:
1 - keep a rigorous schedule of backups (your whole index folder AND your DB tables)
2 - update svn VERY often. I try to aim for a minimum of 3-4 times per week, but daily if I can. This also means you have to manage fewer file changes in any one session.
Darrel
Also, you can avoid installation of SVN to capture the current state simply by downloading the tarball:
http://phpgedview.svn.sourceforge.net/viewvc/phpgedview/trunk.tar.gz?view=tar
Stephen
Thanks.
I would have thought that the development would have taken place in a branch and not on top of the code for the stable release. But I've been in the software development business long enough to know that there is no standard for this.
So, if I want a copy of the stable 4.2 release code with all the fixes (since I have run into a few of the bugs that have been discussed), where do I go? Are all the bug fixes in the patches section? Do those patches always go on top of the distribution package?
Regarding running this in production, I do not. This is more of an academic exercise for me. I download to my own server and test things out and see what mods I can make to deal with some of the issues that are brought up. Takes me back to my developer days and keeps me somewhat fresh. My last addition was long ago when I added the simplyred, simplyblue themes and custom menu items way back when. They have since been incorporated into the mainstream.
Darrel
<<I would have thought that the development would have taken place in a branch and not on top of the code for the stable release.>>
We create branches for major development work, and merge these back in to the trunk. Since many of the developers run their live sites using the trunk, there is a certain incentive to keep it stable and bug-free ;-)
<<if I want a copy of the stable 4.2 release code with all the fixes>>
There is no such thing. The "4.2 tag" in SVN is fixed, and will not change. It is a permanent record of what went in to 4.2.
If you want 4.2+all fixes, then you'll have to accept the trunk, which is 4.2+all fixes+all new bugs.
<<Are all the bug fixes in the patches section?>>
No. Patches are only created for major bugs that can't wait for a version release, or for security patches to older versions.
I would prefer to see a frequent release cycle than a proliferation of patches.
Darrel
Asked and answered with the previously provided link. As advised - no need for SVN client and setup - just install the tarball.
=Stephen
Personally I prefer using the tarball instead of an SVN client. I just download, extract the folder and upload after deleting the themes and mods I don't want and the index and media folders. After uploading I rename the extracted folder so I'm ready for the next time and I always have a previous install ready if there is some major bug. It's a bit more time consuming but I absolutely HATE Tortoise and all those extra files that need to be filtered in my ftp client.
And I'm the opposite. I like deleting or modifying a file or directory _once_, not repeating it every time I upgrade.
And I don't mind at all having had to type
exclude .svn
_once_ in the config file for my synchronizing tool.
:-)
It all boils down to one thing really. All SVN clients are written with developers in mind. They just aren't meant for end-users and they aren't tester-friendly either. Even a developer has to jump through a couple of hoops to upload new code to a live server for testing. I don't know why nobody has developed a client with ftp capability. It would make things so much simpler.
I only update to the latest SVN when I have to. Like Stew, I find Tortoise a pain and download the tarball. I use Beyond Compare from http://www.scootersoftware.com/ It's a file/folder compare/merge/sync system with ftp. It's not my main ftp client but it is ideal for updating a few files amongst many. You have to work out your own process and set up your own filters but I have used it for several years on several websites and found it pretty me-proof.
If you run a remote server, but a local copy of the SVN code,
SmartSVN from SYNTEVO.com is an easy to use SVN client. Fast to setup and fast to syncSVN.
SYNTEVO.com also has SmartSynchronize for using your local directory to ftp and sync with the remote server.
Both have fully functioning demo-mode that lacks only some developer tools - FREE and both programs are crossplatform, runnig on Window OS, Linux and Mac OS.
Easy-Peasy (and I don't work for the company).
-stephen
I tried SmartSVN and it actually does seem to be better than Tortoise. I haven't quite figured out how to configure it to ignore the stuff I don't want but it's pretty easy to select files and use Tools/Backup to export them to a folder for upload.