I am still noticing that there are some folks struggling with the new process and also uploading free extensions, so I wanted to check in to provide you with some useful tips and information. It is important for you to be aware of the new process in order to make extension approval go smoother.
Extension moving back to pending from Submitted
If you have recently noticed that your extension has gone back to pending status from submitted status, this is because there is a problem with your extension. In the past, we’ve used the incomplete status, but with new connect we no longer have that and we use pending. Your extension will stay in the pending status until you have completed the details, and uploaded the package (if applicable.) When you are ready for your extension to be approved, you must SUBMIT your extension for approval by clicking the “Submit for Approval” button on the extension details page.. If you do not do this step, your extension stays in pending status and we will not know on our end if you’re ready to have it looked at.
Here are the statuses we use and what they mean.
Pending = This status indicates your extension is still in development
Submitted = This status indicates to us that you are ready to have us review your extension
Live = self explanatory
Not Approved = This should indicate to you that your extension did not pass review. If there is a problem with your extension, we will not mark it as not approved, but put it back to the pending status.
Tips for Uploading Extensions
We now give you the option to create your own extension key for your free up loadable extension. In the past we generated these keys for you but what you probably didn’t know was that these keys were based directly on the name of your extension. It’s very important to note that if you are uploading a package to Magento Connect—the package name must be IDENTICAL to the new extension key created by you. For instance:
If you create an extension called “My New Extension”—you should create similar extension keys but using an underscore instead of a space.
My New Extension should have the extension keys of My_New_Extension. Also when uploading the package, it should be identical (extension key+version.tgz) So if you repackaged a 2.0 version of this extension it would look like this: My_New_Extension-2.0.0.tgz.
Please be aware: If you do not make the package identical to the key you created, your extension will fail on upload.
Deleting Specific Versions of Your Extension
This functionality has been removed.
Common Packaging Problems
Reminder! When packaging extensions be sure to pay attention to the version of Magento you are working on—as well as which versions of Magento you intend for your extension to support.
Reminders for packaging in 1.4 or earlier versions of Magento
If you are packaging on a system with Magento version 1.4.x or earlier—you must package with magento-community as the channel. The package generated by the system will reside in the var/pear directory. This is the file you must upload in order to generate the 1.0 version of the extension. If you would like to also support the 2.0 (or 1.5 and later) version of the extension, be sure to check those boxes and magento connect system will create the 2.0 for you. This only works when you’re uploading from var/pear.
Reminders for packaging in 1.5 or later versions of Magento
Packaging has changed in version 1.5 and later. You now have the options to package for 1.4 and earlier versions of Magento or 1.5 and later versions of Magento. Weather you select pre 1.5 or 1.5 and later (or both) you still must package with channel community. Some folks have the impression that packaging using the pre 1.5 option should use the same channel as 1.4 but this is not the case. Use single word ‘community’ only.
If you package only using the 1.5 or later option, the system will only create the 2.0 version of the extension. This file is generated in the var/connect directory during the packaging process. Use this file only if you intend to ONLY support 1.5 and later versions of Magento (or 2.0 extensions)
Your USER NAME
Please DO NOT change your username username is directly linked to packaging and if you change it you will lose the ability to update that extension in the future.
Questions? Send them to Magento Connect team at connect at magento dot com