Posted by NancyDru on September 18, 2009 at 4:33pm
Jump to:
| Project: | Util |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
According to the Usage report there are only 40 some users of this branch, it is very much out of date, and I doubt anyone is really supporting it. Why don't we go ahead and drop it?
Comments
#1
See also #359671: Update status. Marking that issue as duplicate.
#2
Fine by me. To be honest i didnt even test 1.2 it and i'm still fine with dropping it.
If anyone wants to find util 1.2 they can download it here: http://drupal.org/node/253615
#3
Actually its a 2 step process.
First i want to release util 3.x considering how many new features went in (before that i want to do a thorough code review). After we have 3.x out of the door with an upgrade path then we can drop 1.2 from the project page and mark it unsupported.
#4
Okay. I also just posted a patch in #456440: Add options in Modules List to see if it does what they want. Actually whether it does or not, I like it and think it should go in before 3.x.
#5
Oleg, I just looked at the usage stats and very few people are using the 1.x branch any more.
#6
I haven't tested it, but if we have upgrade path then by all means mark it unsupported. Rule of thumb when deprecating old stuff is making sure we have ugprade path.
#7
I don't think I ever used v1. The worst that could happen is settings are changed, but then I would encourage anyone not using the most recent -dev to revisit their settings anyway. But if you aren't ready, no big deal.
#8
I'm ready :). i'm just saying we need upgrade path prior to deprecating anything old.
#9
On second thought. scratch it. usage stats is too low. lets just do it ;).
#10
Okay. I don't think there really is an upgrade path needed for Util. It's not like we keep any data.
#11
Done. I also moved everything to a DRUPAL-6--3 branch. That means a 6.x-3.x-dev will appear this evening.