![]() Regardless, PGV has previously muddled through these trying times and new faces and brains have emerged or joined, only to have the program make new leaps forward. ![]() Each of those that left to develop new software have had excellent reasons for doing so and some successfully, while others have been less so. As this is a volunteer project, I have seen splinter groups before, as well as developers who simply ran out of spare time or lost interest in the project and left. I've been here longer than almost any of you, and have been intimately involved in suggesting and assisting with testing and development of many of the features that have been added over the last six years. webtrees version 1 will most likely be ready for public consumption by August 2010 and will provide a method for moving from PGV, so don't rush into anything drastic just yet. When there is a new release for PGV, you will be notified here. ![]() Go ahead and install PGV, get accustomed to using it and begin your ancestral journey. It is likely that this will happen again, as the code is, at best, in a beta condition. Just yesterday, the code added tables that made a complete database deletion and reinstall necessary. The code isn't really suitable for use on a live/production site. In fact, IMHO, the project is no where near ready for casual, new, or in many cases, even experienced admins to begin installing it: GREG says: The procedure would be identical to the WIKI install instructions, and you'll have a quite pleasant and usable code structure for your new site.Īlso, I don't want it to appear that Greg was soliciting you to 'switch' to webtrees. And, as the current SVN condition, #6937, is VERY stable, I would recommend simply doing a tarball download of the SVN code at that SVN level and use it to install PGV, instead of 4.2.3. While Greg refers to minor bug fixes since the release of 4.2.3, others would argue that there are significant improvements contained therein.
0 Comments
Leave a Reply. |