Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.It should not be.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | gct_sandbox_releases.png | 34.41 KB | eliza411 |
| #6 | gtc_sandbox_maintainers.png | 16.84 KB | eliza411 |
Comments
Comment #1
dwwThis would be a bug in project_release. Should I move it there, or do we want to leave it in this queue for visibility to the testers?
The way we did this during the redesign was just use an issue tag for "drupal.org redesign qa". Then there was a global issue search for that tag to see all issues related to testing the redesign, regardless of what project they were in. That's what all the docs pointed to and what all the redesigners were watching. I'm not sure this Git Migration Community Testing project is going to work, since either we're going to have lots of duplicates (e.g. #1028356: Still see "CVS tree" in the "Project resources" fieldset vs #913998: Remove the 'CVS tree' field) or we're going to have lots of issues in this queue that aren't in the "right" project where the maintainers need to fix things, where the test bot can test patches, etc...
Comment #2
dwwSubmitted #1028572: "Administer releases" checkbox visible on maintainers tab for sandboxes upstream to fix this. Marking this postponed pending a fix that's committed and deployed. That seems better than leaving this "active", so we can tell someone already dealt with this issue...
Comment #3
dww#1028572: "Administer releases" checkbox visible on maintainers tab for sandboxes is now fixed and should be deployed as git-dev is rebuilt. This needs re-testing.
Comment #4
eliza411 commentedAssigning to me to test after the next rebuild.
Comment #6
eliza411 commentedAfter the Jan 19 build "Administer releases" still appears, unchecked and disabled. I can assign it to a co-maintainer, and when I do, it gets checked for me.
In addition (and seems like it's related), the Releases tab is still visible. I can check the box, and the setting is saved. This does nothing before I add a co-maintainer and still appears to do nothing afterward, although I haven't tested past this stage so I'm not totally sure what I would see.
Comment #7
eliza411 commentedremoving incorrect tags.
Comment #8
dwwI bet this is caused by #1032634: Creating new projects totally broken. Please retest once that's deployed to git-dev. Sorry about that!
Comment #9
eliza411 commentedThis was okay as of the Jan 20 build