Update packagecontrol.io For New Schemas

[wbond]

Since dependencies need a new python_version field in the JSON schemas, the https://packagecontrol.io code will need to be updated also.

Here are a few relevant places:

• https://github.com/wbond/packagecontrol.io/blob/master/setup/sql/up.sql#L101-L109
• https://github.com/wbond/packagecontrol.io/tree/master/setup/sql/migrations
• https://github.com/wbond/packagecontrol.io/blob/master/app/models/dependency.py
• https://github.com/wbond/packagecontrol.io/blob/master/app/lib/refresh_packages.py#L136-L162
• https://github.com/wbond/packagecontrol.io/blob/master/app/tasks/generate_channel_v3_json.py

There are likely a few more I haven't thought of, off of the top of my head.

[deathaxe]

Is it planned to keep creating channel_v3.json for Package Control 3.4 (for ST2 users) or should database scheme be updated to 4.0.0 as well (drop load_order column)?

ST2 users wouldn't have access to default chennel anymore, if no or a dummy channel_v3 (for PC update) is left behind.

In short: Completely drop support for ST2 and ST3 before 3143?

[wbond]

I think we’ll update the schema but not the file name. I believe that old clients will error out. Either way, no use supporting ST2.

[deathaxe]

With a look at channels.json, providing a dummy channels_v3 which contains Package Control 4.0 release only might be a more robust solution for smooth transition, IMHO.

Just changing scheme version might leave all users behind, which haven't upgraded to PC4.0 before channel_v3 scheme changes upstream.