Steps to reproduce:

  1. Click on the Edit tab for any project release with multiple branches that you maintain.
  2. You'll notice that the Git branch is disabled.

Example: https://drupal.org/node/747432

edit release

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

colan’s picture

Strange. It seems to work now. I'll leave this open to see if anyone runs into the same problem.

andypost’s picture

Title: Cannot change a project's default branch » Cannot change a release's default branch
Issue summary: View changes
Status: Active » Needs review
FileSize
7.81 KB

Default branch change works fine, but there's no way to change release branch from master to 7.x-1.x
I get this on Imagecache profiles module dev release https://drupal.org/node/747432 following https://drupal.org/empty-git-master instructions to remove master branch

andypost’s picture

Issue summary: View changes
tvn’s picture

Issue summary: View changes
Status: Needs review » Active
Issue tags: +Drupal.org 7.1
dww’s picture

Title: Cannot change a release's default branch » Cannot move a dev snapshot release from 'master' to the corresponding branch

When I first saw the title of this issue in the queue I thought "Right, that's by design". But carefully reading the issue, you're actually talking about the edge-case where you've got releases pointing to 'master' that have a real version string (e.g. 7.x-1.x-dev) and wanting to move those to point to the corresponding named branch (7.x-1.x) once that branch exists.

Yes, there used to be special-case code in versioncontrol_release to make this possible. It was supposedly ported to D7, but probably never tested. This is a rare edge-case, so I'm not surprised it wasn't properly ported. Note that these releases only exist from before the Git migration. ;) It's no longer possible to create new releases pointing to 'master'.

Anyway, giving this a more accurate title so that it's more obvious what's actually going wrong. Technically, we should move this to the versioncontrol_project queue, since that's where versioncontrol_release lives which is where the code is that needs to be tested/fixed. However, there's some question as to what the issue workflow should be (#2129357: Suggestion to D7QA bug vetting process) so for now, I'll leave it in this queue.

Cheers,
-Derek

tvn’s picture

Project: [Archive] Drupal.org D7 upgrade QA » Version Control / Project* integration
Version: » 7.x-1.x-dev
marvil07’s picture

Component: User interface » Code
Assigned: Unassigned » marvil07
Status: Active » Needs review
FileSize
1.76 KB

Attached patch I'll be adding to 7.x-1.x.

  • Commit 59ba2c1 on 7.x-1.x by marvil07:
    Issue #2127029: Use the right variable to find version on a release node...
marvil07’s picture

Status: Needs review » Fixed

Added.

drumm’s picture

Now deployed on Drupal.org.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.