提交多个捆绑黑莓应用程序世界 [英] Submit multiple bundle to Blackberry app world

问题描述

一个星期前，我已经提交了支持黑莓Z10的应用程序。昨天，我完成它支持黑莓Q10和黑莓Q5另一个版本。此刻，我在市场上的应用程序是3.0版本，它仅支持Z10。

A week ago I have submitted an application which supports Blackberry Z10. Yesterday, I finished another version which supports Blackberry Q10 and Blackberry Q5. At the moment, my app on the market is version 3.0 and it only supports Z10.

如果我上传一个新的软件包，软件的版本自动增加至4.0。该软件包还只支持Q10和Q5作为已支持Z10的previous版本。在这种情况下，会发生什么Z10用户？他们将获得更新的版本（4.0），因为它是一个较新的版本，虽然我已经设置了特定设备Q10和Q5？

If I upload a new bundle, the version of the app automatically increase to 4.0. This bundle also only supports Q10 and Q5 as the previous version already supported Z10. In this case, what will happen to Z10 users? Will they receive the update version (4.0), as it is a newer version, although I already set the specific devices to Q10 and Q5?

在未来，如果我做了一些更新，我该怎么管理呢？

In the future, if I make some update, how can I manage it?

干杯，

推荐答案

的免责声明：我不开发黑莓10，但我对传统的BlackBerry OS版本做的，我相信这个工程黑莓在同一个供应商门户（见注释彼得奇怪以下confiming）的

如果我上传一个新的软件包，软件的版本自动增加至4.0。

If I upload a new bundle, the version of the app automatically increase to 4.0.

首先，这是Web界面的默认操作是什么。它自动增量的大的版本号（数字到小数点的左边）。然而，版本号的字段是可编辑的，所以如果你不喜欢默认的选择，你可以改变它。例如，如果您想在新版本为3.1，或3.0.1，而不是4.0，那么你可以手动更改。就个人而言，我不认为你应该增加的主要的版本号只是为了添加新设备，在同一行的操作系统的范围内。

First of all, this is what the web interface does by default. It auto-increments the major version number (the number to the left of the decimal point). However, the field for version number is editable, so if you don't like the default choice, you can change it. For example, if you would like the new version to be 3.1, or 3.0.1, instead of 4.0, then you can change it manually. Personally, I don't think you should increase major version numbers simply to add a new device, within the same line of OS's.

这包还只支持Q10和Q5作为已支持Z10的previous版本。在这种情况下，会发生什么Z10用户？

This bundle also only supports Q10 and Q5 as the previous version already supported Z10. In this case, what will happen to Z10 users?

Z10用户应该看到没有变化。如果previously有一个可用的版本Z10，它仍然应该继续使用。当你上传一个新的软件包，您应该使用Web界面来指定哪些设备能释放软件包支持

Z10 users should see no change. If you previously have a version available for Z10, it should still continue to be available. Whenever you upload a new bundle, you should use the web interface to specify which devices that release bundle supports

（或者，你可以挣大钱的 ZIP容器，和使用的排放的.xml / devices.txt中指定设备支持）。

(alternatively, you can make a zip container of bundles, and use release.xml/devices.txt to specify device support).

因此​​，如果新版本仅指定Q10 / 5的支持，该软件包将不会投放给用户的Z10。 Z10的用户仍然可以访问到3.0版本。

So, if the new release only specifies Q10/5 support, that bundle won't be served to Z10 users. Z10 users will still have access to version 3.0.

在未来，如果我做了一些更新，我该怎么管理呢？

In the future, if I make some update, how can I manage it?

我会建议你只改变的主要的版本号，当你的应用程序的功能的显著的变化。 3.0版到4.0应该是一个重大的改变，对用户可见。我个人，然后使用的轻微的对小的变化，同时也是对用户可见的版本号。例如，3.0版到3.1。最后，一​​个版本号的最后一位数字我保留了小的变化，如bug修复，不增加新的功能，但prevents一个问题。例如，版本3.0到3.0.1。

I would recommend that you only change major version numbers when the functionality of your app significantly changes. Version 3.0 to 4.0 should be a major change, visible to the users. I personally, then use minor version numbers for small changes, that are also visible to users. For example, version 3.0 to 3.1. Finally, the last digit of a version number I reserve for small changes, such as a bug fix that doesn't add new features, but prevents a problem. For example, version 3.0 to 3.0.1.

有关新版本的仅的添加了对新设备的支持，我可能只是改变了最后一个数字（例如3.0至3.0.1）。但是，这是你的决定。

For a new release that only adds support for a new device, I would probably just change the last digit (e.g. 3.0 to 3.0.1). But, that's your decision.

如果你有一个新版本的仅的增加​​了对新设备的支持，那么你应该能够只上传一个新包，指定这些新设备的支持，而不是上载新的$ C $下的所有设备。这样一来，用户Z10没有费心去安装更新时，最新版本实际上包含什么新东西为他们的设备。

If you have a new release that only adds support for new devices, then you should be able to only upload a new bundle that specifies support for those new devices, rather than uploading new code for all devices. This way, a Z10 user isn't bothered to install an update when the newest release actually contains nothing new for their device.

这篇关于提交多个捆绑黑莓应用程序世界的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！