Issue 4616 - Push Edge related changes to the edge bookmark of adblockpluschrome

metadata.edge

Index: metadata.edge
===================================================================
new file mode 100644
--- /dev/null
+++ b/metadata.edge
@@ -0,0 +1,17 @@
+[default]
+inherit = metadata.chrome
+
+[general]

[Sebastian Noack, 2016/12/19 11:48:34]

As long as Adblock Plus is still in beta, and still not released out of
upstream, the version should remain 0.9.*. So we have to override the "version"
key in the "general" section.

[Oleksandr, 2016/12/19 12:41:33]

Our current version is 0.9.9.9. What would you see the next version to be?
Besides, the version built from this *will* be based on the upstream, so I think
it's a good time to switch to the correct version number now.

[Sebastian Noack, 2016/12/19 14:28:05]

Our current version is 0.9.9.0 (not 0.9.9.9), and the next version would be
0.9.10. As far as version numbers matter in the first place, the 0.* notation is
_correct_ and important to indicate that we are in beta, which isn't going to
change before we merged the branch upstream and before we get the storage logic
straight which then again requires the Windows Creators Update. Moreover, we
might introduce conflicts when the upstream branch (i.e. tip) and the edge
branch are on the same version track but are released separately.

+basename = adblockplusedge
+app_id = EyeoGmbH.AdblockPlus
+publisher_id = CN=4F066043-8AFE-41C9-B762-6C15E77E3F88
+background_color = red
+
+[compat]
+edge = 37.14332.1000.0
+windows = 10.0.14332.0/12.0.0.0
+
+[appx_assets]
+logo_44.png = icons/abp-44.png
+logo_50.png = icons/abp-50.png
+logo_150.png = icons/abp-150.png