Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I don't see any 5.x requests left; they've all been closed. It would be nice to leave one out here for tracking.
Can we even get a beta release or a -dev? I do not want to use a CVS version, and will not use patch code.
In order for us to use the Update status module, there needs to be an "official release" of this module (no "-dev", but can be "-beta").
Comments
Comment #1
akaney commentedI don't want to step on any toes, but I think that there are still enough issues in the HEAD version to keep it in CVS. I believe vhmauery is doing very good at trying to iron the issues out, but you don't want to rush into putting out a RC. I have been using the CVS versions for a few weeks, and they are stable, but still have small glitches.
I don't think it is good reasoning to put a module in RC mode just to allow it to be indexed by the update module.
Comment #2
nancydruAt the moment it is not really an issue of getting Update status working - it's a matter of getting my site updated to 5.1. This module is holding me up. As I said, I don't want to use a release that doesn't actually exist (at least as -dev).
Comment #3
vhmauery commentedNancyw, try page 2. Plus, there are open 5.x requests in 'Needs more info' state.
Please don't bug me about creating a release. I will create one when I am ready. Please be aware that by not using the module available for testing only increases the time it will take to find a sufficient number of bugs before I feel it is stable enough to release.
Test the module and tell me what is wrong. Much of it just works for me. What is broken for you?
Comment #4
nancydruI have no idea if anything is broken. I don't know how to use CVS, and prefer to keep it that way.
Comment #5
vhmauery commentedI am not asking you to use CVS. Use the snapshot release from http://ftp.osuosl.org/pub/drupal/files/projects/acidfree-HEAD.tar.gz It is generated several hours after the latest CVS commit. So it is not too far behind CVS.
Things are broken if they 1) generate a warning or error, 2) don't work as expected or 3) don't work at all.
These are the things I need to hear about. This is what opensource is all about -- users give feedback. Some give patches. Everyone benefits from a better product.
Comment #6
blackfox commentedI'm very sorry for bugging you with this question, but it is essential for me for planning (and might be for others as well):
Can you roughly estimate when there will be a final 5.x-release? Or at least a -dev?
When Drupal 5.0 was released, I've read the status on the modules page and thought: ok, I can wait some time till I need this module for my new Drupal5-site. Looking back at http://drupal.org/project/acidfree every week there elapsed more and more time and in the near future I have to bring up a solution for the image-gallerys of my site.
I could use gallery-module, of course - but I would prefer the more Drupal-native way acidfree dose it! My problem is not, that I can't wait another two weeks e.g. if acidfree needs this to get ready for a release - my problem is that I don't know if I might wait two months. So please make a little update to http://drupal.org/project/acidfree so interested people find some information...
Comment #7
vhmauery commentedwhat you are asking for is a duplicate of http://drupal.org/node/104786
I closed this issue for a reason. Please don't keep opening it.
As I have already said to what seems like a thousand users, I will create a 5.0 branch when I feel it is ready. Acidfree 5.0 is not ready for production sites. But please test it on mock installs of production sites so we can find all the problems, document them and resolve them.
The more time I waste telling people that Acidfree is not ready means even less time for me to do real development. Have some patience. Or better yet, contribute.