Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Maybe I'm missing soemthing, but I can't seem to set up a new project release. I go here:
http://drupal.org/node/add/project-release
Select the project I want 'Earth Hour'
Check that it's from the HEAD.
Then I get these errors.
* The Patch-level must be "x" for snapshot releases from a branch (or HEAD).
* The Extra identifier must be "dev" for snapshot releases from a branch (or HEAD).
There's got to be better docs on this page or in the errors to explain what this is about. It's not a dev release, so not sure why that warning is coming up.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Choosing Project | 69.05 KB | mgifford |
| #3 | screenshot-62.png | 518.16 KB | mgifford |
| #3 | Final Selection Choices | 104.45 KB | mgifford |
| #3 | Error Messages | 58.49 KB | mgifford |
Comments
Comment #1
dwwHEAD releases are inherently "dev" releases. HEAD is a branch. A release pointing at a branch is automatically regenerated every 12 hours, and therefore must be a -dev release. So, those validation errors aren't a bug, and your basic request is a support request which would now be fixed.
That said, the UI for this form UTTERLY SUCKS. It was the best I could do when I had to get this stuff working at all in 4.7.x FAPI. In the D5 port, multi-step FAPI didn't really improve enough to make it worth trying to fix. Now that we have $form_state in D6, I could actually fix this, I just haven't had a chance, yet. Related reading:
#89699: make release node form smarter when editing HEAD releases
#370603: Previewing HEAD release nodes is broken in 6.x
Anyway, I've been meaning to change this form so that in D6, when you create a new release pointing to HEAD, you only have to answer what core compatibility term and what major version you want. And the help text should be more clear. I actually have a patch started on my laptop, but it's not working yet. ;) I'm just going to reclassify this issue to do that, instead of marking it duplicate with one of the above, since #89699 is technically about editing existing HEAD releases, not creating new ones, and #370603 is a different bug entirely (which can't be solved without a patch to FAPI itself -- #382634: Previewing multiselect taxonomy fields lose value on multistep node forms).
Cheers,
-Derek
Comment #2
dww"generate" implies auto-generated nodes, we're just talking about end users creating them... better title. ;)
Comment #3
mgiffordUltimately, if I could just take a tarball and upload it I'd be happy.
I've got stuff in the cvs, but really don't need that for this purpose.
I just want to be able to issue a stable release. Or heck, a dev release. But I can't get nothing but errors.
Thanks for your help though.
Comment #4
dwwAt this stage: http://drupal.org/files/issues/screenshot-63.png enter:
Core: 6.x
Major: 1
Patch-level: x
Extra identifier: dev
Comment #5
dwwOh, and if you want a stable release, then add a cvs tag.
http://drupal.org/handbook/cvs/introduction
http://drupal.org/handbook/cvs/releases
http://drupal.org/project/earth_hour/cvs-instructions
Comment #6
mgiffordOk.. Finally got it out the door. Thanks for all of your help.
Ultimately I didn't realize that I needed to show the cvs-instructions.
I've used CVS now for 8 years and so didn't really think I needed instructions.. That being said, Drupal's done a lot to force a process to allow the update status to work properly.
It's more complicated now, but more robust. Reading the docs was more difficult because I wasn't able to see what I didn't already know. Kept going through reams of stuff that didn't tell me anything useful or new.
Anyways, I'll likely come back here, but thanks again.
Comment #7
schildi commentedHave the same hassle each time I want to release a new version. I also know CVS since years and find the UI incredibly bad. Error messages but no real hint what is going wrong and how to solve the situation. And this situation is unchanged since years.
After checking in the sources (HEAD) I also expected that the sources will be tagged the right way when a new (stable) release is set up.
My expectancy:
* when an error message is shown please also show links to the docs
* provide step by step instructions when erroneous situations come up
Sorry, for me it looks that the explanations don't tell more in D6 than before. When a developer doesn't provide values for a snapshot or dev-release he possibly wants to set up a stable release. But there is no hint how to circumvent the erroneous situation and feels lost.
Why not provide to tag the sources (together with additional hints and links to docs like shown in #5) ?
Comment #8
dwwI'm happy to report that we've fixed this UI by completely removing it:
#850142: Integrate VCAPI with project_release node add form
#953916: Proposal: Ditch the ability to have release nodes pointing to HEAD/master
When the Git migration is completed hopefully before DrupalCon Chicago, everything will work much smoother...
Cheers,
-Derek
Comment #9
schildi commentedthanks for your friendly reply. And sorry for my emotions yesterday, I REALLY didn't want to offend you!