Download & Extend
Date » Issues

Change date_migrate_example Feature to be listed within the "Migrate Examples" package

Posted by rupl on August 8, 2012 at 2:34pm
Project:Date
Version:7.x-2.x-dev
Component:User interface
Category:task
Priority:minor
Assigned:Unassigned
Status:reviewed & tested by the community

Issue Summary

Unless someone goes out of their way to categorize their Features, this date_migrate_example Feature often ends up listed with client-specific code in the Features UI. I think it would be ok to move it into "Migrate Examples" since that appears to be its purpose. Thanks!

Login or register to post comments

Comments

#1

Posted by rupl on August 8, 2012 at 2:36pm
Status:active» needs review

Here's the patch.

AttachmentSizeStatusTest resultOperations
1719290-1-migratepackage.patch611 bytesIdlePASSED: [[SimpleTest]]: [MySQL] 5,238 pass(es).View details | Re-test

#2

Posted by rupl on September 25, 2012 at 9:00pm

Can I offer a review on another issue in exchange for this cosmetic patch being committed?

#3

Posted by rupl on February 22, 2013 at 5:19pm
Component:Code» User interface

So sad that I can't even offer a review to get this committed :(

Doesn't anyone want to avoid seeing this random unrelated Feature listed with all their other client-specific code? End users are confused by it. I have confirmed that already with multiple clients.

#4

Posted by Simon Georges on March 16, 2013 at 1:33pm
Status:needs review» reviewed & tested by the community

I'm totally in favor of that too, either "Migrate examples" or "Example modules" (same as Variable or Examples modules).

Patch applies cleanly.