This makes it extremely difficult to maintain via CVS. Can a DRUPAL-6--2 branch be started?

Comments

jcfiala’s picture

jcfiala commented

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.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented

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.

jcfiala’s picture

jcfiala commented

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.

jcfiala’s picture

jcfiala commented
Status: Active » Fixed

There!

I've put the code under DRUPAL-6--2 - hopefully that will do.

Status: Fixed » Closed (fixed)

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