Fix the UI when creating release nodes pointing to HEAD
mgifford - March 22, 2009 - 15:39
| Project: | CVS integration |
| Version: | 6.x-1.x-dev |
| Component: | Project releases |
| Category: | task |
| Priority: | normal |
| Assigned: | dww |
| Status: | active |
| Issue tags: | drupal.org upgrade |
Description
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.
#1
HEAD 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
#2
"generate" implies auto-generated nodes, we're just talking about end users creating them... better title. ;)
#3
Ultimately, 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.
#4
At this stage: http://drupal.org/files/issues/screenshot-63.png enter:
Core: 6.x
Major: 1
Patch-level: x
Extra identifier: dev
#5
Oh, 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
#6
Ok.. 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.