Drupal.org upgrade
If you want to help with the Drupal.org upgrade, here is what you can do: 1. Help categorize projects. See http://dev.bryght.com/t/wiki/ DrupalProjectCategories, and the discussion on development@drupal.org. 2. Go to http://scratch.drupal.org/ and test, test, test. Report problems using the issue tracker. (Example 1: the user profile pages are broken due to a bug in CVS HEAD. Just take a look. Clearly a show-stopper.) (Example 2: double-check whether the Drupal.org theme has been updated to comply with recent CSS changes.) 3. Look into optimizing the forum listings; ?q=forum is one of the slower pages. 4. Look into optimizing the cvslog module: ?q=cvs is one of the slower pages. 5. Follow-up and work on infrastructure issues: http://drupal.org/ project/issues/drupal_org_maintenance. You can also help with: 1. Project module development. 2. Improving the code checker script. 3. Importing CVS repositories in cvslog module. -- Dries Buytaert :: http://www.buytaert.net/
2. Go to http://scratch.drupal.org/ and test, test, test. Report problems using the issue tracker. (Example 1: the user profile pages are broken due to a bug in CVS HEAD. Just take a look. Clearly a show-stopper.) (Example 2: double-check whether the Drupal.org theme has been updated to comply with recent CSS changes.) there are problems with the url-paths at the "Contributor links" goto a page like http://scratch.drupal.org/project/ and then look at the contributor links you can see that the path for example planet drupal has changed to http://scratch.drupal.org/project/planet
access to planet drupal is denied on /project: you read under every item: "BLABLABLA are not part of any official release and may not work correctly. Only use matching versions of BLABLABLA with Drupal. BLABLABLA released for Drupal 4.5 will not work for Drupal 4.6." sounds ugly would be better if this very general sentence would be at the top of the site and under every item a description like: Modules: Enhance Drupals functionality with Modules. For example a Newsletter-Module or a Project-management module Themes: Change Drupals design with prebuilt themes Translations: Drupal in your language. Theme engines: Some Themes need another Theme engine which you can find here.
On 2/3/06, Tobias Maier <tobias.maier@gmail.com> wrote:
2. Go to http://scratch.drupal.org/ and test, test, test. Report problems using the issue tracker. (Example 1: the user profile pages are broken due to a bug in CVS HEAD. Just take a look. Clearly a show-stopper.) (Example 2: double-check whether the Drupal.org theme has been updated to comply with recent CSS changes.) there are problems with the url-paths at the "Contributor links" goto a page like http://scratch.drupal.org/project/ and then look at the contributor links you can see that the path for example planet drupal has changed to http://scratch.drupal.org/project/planet
access to planet drupal is denied
The same problem affects the bug-bingo and many others in the contribute block. It seems that links that point to other sites work fine, but those that point to paths internal to drupal.org have problems. Greg
there are problems with the url-paths at the "Contributor links" goto a page like http://scratch.drupal.org/project/ and then look at the contributor links you can see that the path for example planet drupal has changed to http://scratch.drupal.org/project/planet
access to planet drupal is denied
The same problem affects the bug-bingo and many others in the contribute block. It seems that links that point to other sites work fine, but those that point to paths internal to drupal.org have problems.
Thank you, Greg. I just fixed those. The fixes won't be visible until next time scratch.drupal.org is synced. -- Dries Buytaert :: http://www.buytaert.net/
On 2/4/06, Dries Buytaert <dries.buytaert@gmail.com> wrote:
Thank you, Greg. I just fixed those. The fixes won't be visible until next time scratch.drupal.org is synced.
They are fixed/published now. I tried submitting a comment on an issue and it did not go through. Should we continue testing out scratch? Is the comment problem a known issue? Thanks, Greg
On 20 Feb 2006, at 23:16, Greg Knaddison wrote:
Thank you, Greg. I just fixed those. The fixes won't be visible until next time scratch.drupal.org is synced.
They are fixed/published now.
I tried submitting a comment on an issue and it did not go through. Should we continue testing out scratch? Is the comment problem a known issue?
Yes, feel free to test. The last upgrade should have fixed some bugs. Note however that I disabled (or tried to disable) all the mail- functionality on scratch to prevent people sending mails while testing. If your mail doesn't get through, that's probably the reason. Makes sense? :) -- Dries Buytaert :: http://www.buytaert.net/
Dries Buytaert wrote:
4. Look into optimizing the cvslog module: ?q=cvs is one of the slower pages.
I've had a look and found that it does a join on the cvs_files table that isn't used most of the time. Avoiding that brings the query down from 2 seconds(!) to about 0.8s on my laptop. I've also changed some LIKEs to =. The change is in cvs, roll back what you don't like. :) Cheers, Gerhard
FYI: I posted a few issues regarding scratch.drupal.org glitches on user page http://drupal.org/node/48791 security issue: I'm able to outline pages http://drupal.org/node/48790 menu ordering was changed http://drupal.org/node/48789
On 12 Feb 2006, at 19:59, Tobias Maier wrote:
glitches on user page http://drupal.org/node/48791
I don't think anyone has been looking into this. It's a show- stopping issue so any help is appreciated. Likely a bug in CVS HEAD.
security issue: I'm able to outline pages http://drupal.org/node/48790
Unlike users on drupal.org, users on scratch.drupal.org have the 'maintain books' permission ... This is the result of a decision that was made recently on the documentation mailing list. The goal was to invite more people to make changes/edits to the handbook. Being able to outline book pages doesn't sound like a good idea though.
menu ordering was changed http://drupal.org/node/48789
This might be due a bug in the upgrade path. scratch.drupal.org is about three weeks old so this might have been fixed in newer versions of database/updates.inc. I'll import and upgrade a fresh copy by the end of next week to see if the problem persists. Thanks Tobias, -- Dries Buytaert :: http://www.buytaert.net/
Dries Buytaert wrote:
I don't think anyone has been looking into this. It's a show- stopping issue so any help is appreciated. Likely a bug in CVS HEAD.
security issue: I'm able to outline pages http://drupal.org/node/48790
Unlike users on drupal.org, users on scratch.drupal.org have the 'maintain books' permission ... This is the result of a decision that was made recently on the documentation mailing list. The goal was to invite more people to make changes/edits to the handbook. Being able to outline book pages doesn't sound like a good idea though.
This sounds like a good case for splitting the outlining into a separate permission?
On 13 Feb 2006, at 08:34, Robert Douglass wrote:
I don't think anyone has been looking into this. It's a show- stopping issue so any help is appreciated. Likely a bug in CVS HEAD.
security issue: I'm able to outline pages http://drupal.org/node/48790 Unlike users on drupal.org, users on scratch.drupal.org have the 'maintain books' permission ... This is the result of a decision that was made recently on the documentation mailing list. The goal was to invite more people to make changes/edits to the handbook. Being able to outline book pages doesn't sound like a good idea though.
This sounds like a good case for splitting the outlining into a separate permission?
Probably. We need to investigate the code though. Maybe 'maintain books' is no longer the best permission name. -- Dries Buytaert :: http://www.buytaert.net/
participants (5)
-
Dries Buytaert -
Gerhard Killesreiter -
Greg Knaddison -
Robert Douglass -
Tobias Maier