DRUPAL-5 branch incompatible with DRUPAL-5 Workflow
gnassar - May 27, 2008 - 18:47
| Project: | Actions |
| Version: | 5.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
The Workflow DRUPAL-5 branch is in sync with the DRUPAL-5--2-x revisions, but the Actions DRUPAL-5 branch is in sync with the DRUPAL-5--1-x revisions. Workflow 2.x correlates to the "new style" Actions DRUPAL-5--2-x revisions, obviously, not 1.x; it would make sense that both DRUPAL-5 branches refer to revisions that work with each other.
#1
In retrospect, considering that workflow is moving pretty much irrevocably towards compatibility with 6 (and understandably so), this should be an item in the Actions queue and not the Workflow queue, implying that it'd be more appropriate to make the change to DRUPAL-5 in Actions than it would to Workflow. My apologies.
Also, perhaps a task as opposed to a bug report. Only reason I considered it a "bug" is because pulling DRUPAL-5 Actions and Workflows fails (as WF's counting on the other style of Actions). Not sure; I'll leave as is for now.
#2
And I forgot to change the title. Goodness gracious.
#3
Hello,
What do you advise to do until this problem is solved?
Thanks,
David
#4
As you can see from the actions releases page, actions 5.x-2.x-dev is taken from HEAD currently. So if you want to be on the bleeding edge of actions 5.x-2.x development, pull actions HEAD from CVS. Otherwise use a release tag like DRUPAL-5--2-5.
#5
Yes, I did that. My point is that the branch naming is inconsistent, confusing, and in some cases technically incorrect. Actions 5.x-2.x-dev should be pulled from a 2.x-dev tag. Actions HEAD build should be pulled from the HEAD tag. Right now, there is no 5.x-2.x-dev tag (DRUPAL-5--2). HEAD and DRUPAL-5--2 would be synonymous, yes -- but that should be clear from CVS; it should not require some entry at the bottom of the releases page to realize.
As per the handbook, DRUPAL-5 is a synonym for DRUPAL-5--1 (which won't be permitted in Drupal 6 tags anymore, thank goodness). So, my recommendation (as earlier requested):
- Actions gets a DRUPAL-5--2 tag, which is synonymous to HEAD;
- Workflow's DRUPAL-5 tag becomes DRUPAL-5--2, leaving HEAD as the Drupal 6 dev location;
- Workflow's last commit that was compatible with Actions 1.0 gets tagged DRUPAL-5.
This will make the branch structure consistent with handbook recommendations and with the other modules in contrib, as well as solving the 1.0/2.0 tagging inconsistency.
#6
I agree. Pulling from head, to me, makes me think that I'm getting something geared towards Drupal 7 (not even 6).
A DRUPAL-5-2 tag would greatly help.
Just my 2 cents.
#7
DRUPAL-5--2 branch added to actions.