Why is Link DRUPAL-6--2-6-BETA2 in the DRUPAL-6--1 branch?
tim.plunkett - July 2, 2009 - 16:22
| Project: | Link |
| Version: | 6.x-2.6-beta2 |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
This makes it extremely difficult to maintain via CVS. Can a DRUPAL-6--2 branch be started?
#1
Probably. I got it in this status, and I was first planning to get out a stable release, and then go over and get it into the correct branch. I'm not very certain on how to use CVS correctly.
But I'm the one maintaining it, so what's the problem? Just curious.
#2
When maintaining a site via CVS, the CVS Deploy module and the core Update module work together to notify the admin when modules are out of date. But when a 6.x-2.x version is released via CVS as DRUPAL-6--1, Update sets off major warning signs.
#3
Ah, see? I wasn't aware of that. I'll try to get this moved to an appropriate branch before I do the final release of 6.x-2.6 - so far, I haven't heard anybody having trouble with it.
#4
There!
I've put the code under DRUPAL-6--2 - hopefully that will do.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.