Changes to CVS
Way back at the last developer meeting, we decided that once 1.0 was released, we'd split the CVS tree into two branches, STABLE and CURRENT.
STABLE will be basically what you've been checking out from CVS if you've been tracking it before now; namely, changes are tested and work to the best of our knowledge, although there is always an element of risk.
CURRENT will be a place for us to work on major new features that may break backwards-compatibility and may not work properly at any given moment. Changes will still be tested, but not necessarily as thoroughly as they will in STABLE. We don't recommend using CURRENT to run a live site.
To check out the 1.0 release:
cvs co -r scoop-1_0-RELEASE scoop
Captain_Tenille will post more information about the changes to CVS and how to use the different branches, since it was his idea.
Major features and bugfixes since 0.9
If you've been tracking CVS, you've seen these features appear over time. If you're still running 0.9 or a version even older than that, now's a good time to upgrade...
For descriptions and a more complete list, see the CHANGES file. (If it asks for login information, give it user = anonymous, pass = anonymous)
- File uploads
- "Safe mode"
- More flexible comment rating system
- Admin tools search
- New admin documentation
- Ads and subscriptions work out of the box now
Quite a few new features have been proposed and started for future versions of Scoop, including mod_perl2/apache2 support, postgreSQL support (for real this time, we actually have some code submitted, not just a promise), more flexible user prefererences, wiki-style collaboration and versioning on Scoop stories, and much more.
The Scoop Bug Muncher has proven helpful for tracking bugs, patches, and the "1.0 to-do list" in the months it's been running, so I think we'll keep it. Thanks to MostlyHarmless for setting it up.
Hopefully we will have releases a little more frequently than every year or so from now on, for those who don't like running the CVS version.