The most recent stable version of this module is 7.x-3.1, which is 2 years and 4 months old at the time of writing (release date: 11 May 2015).

Is the 7.x branch of this module still maintained? There are more than 250 open tickets for this branch. Should I be looking at other back-up solutions and if so, which can you recommend?

Comments

brankoc created an issue. See original summary.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

As of today (#2826162: Add a new maintainer) there's a new maintainer for the D8 branch, but give it a little time and I'm sure the D7 work will pick up again.

(and I agree, I have several patches that could use a commit on the D7 branch)

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Fixed
couturier’s picture

couturier commented

@DamienMcKenna there are a ton of tickets open in the 7.x-2.x branch. Is there any reason why we can't deprecate the 2.x branch? I'm wondering if a lot of these issues would be resolved with an update to the newest 7.x-3.2 version released yesterday. The 2.x branch hasn't received a code update in 4 years.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Related issues: +#2912440: Verify 7.x-2.x -to- 7.x-3.x upgrade path, mark 7.x-2.x as unsupported

Lets focus on the 7.x-2.x thing in #2912440: Verify 7.x-2.x -to- 7.x-3.x upgrade path, mark 7.x-2.x as unsupported.

Status: Fixed » Closed (fixed)

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