Forum OpenACS Development: Outphasing old versions
This would not be harmful if the time period between the last minor release of the previous major version and the release of the BETA is small. Sadly, experience has shown that it usually is fairly large. This does not encourage the interested people in switching their not so important sites with real data to the next major release and use it in production.
My idea therefore was to release the BETA of the next major version with the last release of the previous major version. If we therefore cut 5.1.5 we would (after the merge thanks to our merge king Jeff Davis) immediately cut 5.2b1.
This means (as we do have our release criteria) that we will not release the last minor version before we can actually cut the first BETA.
What do you think about this suggestion (linking the last minor release with the first BETA of the next version) ?
Maybe it's just me, but I think I've completely missed the main thrust of whatever point you're trying to get across...
After all, there is no incentive to move a (not important, production) site to 5.2 if there is no guarantee that you are able to upgrade from that version to which you upgraded to.
Maybe this makes my aim a little bit clearer.
What do you wish to upgrade to? I am seriously confused.
If your insallation is running the latest release version, why do you need to upgrade?
The reason we don't support upgrades to development version is a pratical lack of resources.
The way to reduce the length of time before release of OpenACS 5.2 is to dig in, test, fix bugs, and basically make the release happen. Anyone in the community is encouraged to help out in any way they can, by testing, reporting bugs, submitting patches, cleaning up the bugtracker. Anything. If anyone would like to help, but does not know how, please post to the forums or visit us on IRC at #openacs http://openacs.org/irc/
"Supported" in this case means tested and debugged. The OpenACS community is always supportive of anyone who makes an effort to use OpenACS. That means if you upgrade from a development version to a release and have a problem, the community will always be there to answer questions and help out. You might not get a volunteer to log into your server and fix it for you, but there are people in the community that enjoy and challenge and will help those who are willing to dig in, ask smart questions, and learn something new.