Update: Apologies for the delay in bringing drupal.org back up. In spite of many painless conversions on scratch.drupal.org, as feared, something went terribly wrong during the update on drupal.org. It took us a few hours to work around the problems this caused with some creative coding and sneaky SQL tricks. Immediately after the site was up, it experienced about an hour of very sluggish response time. This was due to a major SQL load put on the database server during the conversion itself (a huge backlog of queries the mysqld was struggling to process), the flood of traffic from bringing the site back on-line, and some lingering PHP configuration issues that we had setup to try to debug the faulty steps of the upgrade. The good news is that the site is back now, it seems to be as responsive as ever, no actual harm was done, and the new release system is working...
After months of work, the initial version of the new system for releasing Drupal contributions is finally ready for deployment on drupal.org. To perform all the necessary backups and convert existing releases over to the new system, we will have to take drupal.org down for system maintenance for approximately 30 minutes. We are planning to do this conversion sometime on Saturday the 11th of November (2006-11-11) between 7:30am and 8:30am UTC. We apologize in advance for any inconvinence this might cause, and have done all we can to minimize the downtime required, but please plan your use of drupal.org accordingly.
We have performed this conversion many times on scratch.drupal.org, since beta versions of the release system have been installed on scratch.drupal.org for nearly 3 weeks. We expect a smooth transition to the new system, however the first rule of system administration is to expect the unexpected...
Documentation on version numbers for contributions in the new system is currently available in the information about Drupal versions handbook page on scratch.drupal.org. This page will move to the live copy on drupal.org during the conversion. Additional documentation on the new system, both for end users and contribution maintainers is in the works, and will be made available in another announcement once the system is live.
Thanks for your patience, understanding, and continued support!
-Derek
Comments
should we delay tagging on contributions?
Firstly, thanks for all your hard work. I think this is a significant development for the Drupal community.
I was just about to tag a CVS contribution (theme) with DRUPAL-4-7, my question is should I wait until the dust settles on the upgrade.
Cheers,
Ross
--
Ross Kendall
UK based Web and IT consultant specialising in Free and Open Source Software technologies.
http://rosskendall.com
Does that mean...
Does that mean Drupal 5.0 will be released right after? Hmm... That would be an early Thanksgiving present.
-Jeff
http://blog.zemote.com
Definitely not...
Please read Dries's original beta announcement e-mail to discover how you can help 5.0 become a Thanksgiving present. ;)
I am testing already :)
I have 2 Drupal 5 Beta installs currently and testing as thoroughly as I can.
-Jeff
http://blog.zemote.com
This is going to kick ***,
This is going to kick ***, any info on how far you are monetarily? I haven't seen it updated for a while, but I am interested on how it is progressing.
side-fx
congrats on the new system. a small side effect is the /modules/date page that is currently on alpha. i guess that once people start committing again, this will be solved and be by date again?
--
groets
bertb
--
groets
bert boerland
new tarballs had to be generated
right, unfortunately since the version numbers have all changed, we needed to re-create all the tarballs. no one ever pointed this problem out during the 3 weeks the system was installed on scratch.drupal.org, and i never happened to notice, so it didn't occur to me that we'd loose this date-based sorting as a result of this re-generation. instead, i suppose we could have written some scripts to try to carefully rename the files in a way that didn't change their modification times, etc, etc, but i never spent the time on such a thing, since it never crossed my mind. sorry, yeah, that's a minor bummer... my apologies. and indeed, it'll start being spread out through time again as people commit.
___________________
3281d Consulting
and i will update
the posting with some grapgs as promissed
btw: next time, i am up for stupid bugtesting stuff on scratch.
--
groets
bertb
--
groets
bert boerland
thanks! very excited to see
thanks! very excited to see version numbers with modules. Most appreciated!
morphir.com
Modules by date
Not sure where the best place to post this is, but, there seams to be an issue with searching for modules by date. It seams as though all modules are getting re-dated to the current date every day. So today, all modules are shown as having an 11/13/2006 date. I understand that this was to be expected with the initial switch to the new system, but it looks like it is continuously re-dating all modules daily.
Thanks.
see here
up pending your font and monitor size, about 8 centimeters :-)
--
groets
bertb
--
groets
bert boerland
bug fixed -- thanks for the report!
yeah, that's not just the problem bert is talking about that i commented on above. this was a genuine bug in the packaging script. :( luckily, the fix was trivial, and is now installed. this shouldn't be happening with the next packaging run. see http://drupal.org/node/97405 for details on the bug and the fix. if you see anything else go wrong about this, please reply there, not here.
for future reference, http://drupal.org/node/94000#feedback (the announcement about the system going live) explains the best ways to provide feedback about the new system.
___________________
3281d Consulting
standing up
i stand corrected, indeed two different things, so thanks for reporting and hence fixing
--
groets
bertb
--
groets
bert boerland