Should we aim for the new PackageManager when releasing a Plugin

Hi,

currently we are developing a Plugin for our APP which we want to share with the Unity Community.
The plugin has DLLs, Scripts and some Textures and Shaders in it.

We would like to upload it to the Asset Store, but this will only allow uploading the old/legacy package format:

Code (CSharp):

1. AssetDatabase.ExportPackage()

Question:
Should we wait until the new Package System is available for the AssetStore (how long?) or should we commit the package with the old/legacy method?

Can we later easily convert the plugins from the old/legancy system to the new Package system?

 

if you follow all the upm guidelines for packages (all code into asmdef, folder structure, etc...), have no external dependencies, and stick to a single root folder, I think that converting will be easier (move the root to Packages/ and add the manifest)

idk how asset store will be integrated though, and if we will be able to upgrade a legacy asset into a package, or what will be the restrictions for publishing a package...

(if your asset is free, you can already put it on github/bitbucket as a package, or have a private scoped npm registry...)

 

Thank you for the Feedback.

We will not have any dependecies.

The reason for using the AssetStore is, to reach a much larger audience then just showing it on github and/or own download pages etc.

 

Thank you, that helped us a lot. So we will create everything prepared for the new Package and put these data into the legancy stuff.