维护不同Worklight Studio补丁版本的最佳做法 [英] Best practices to maintain different Worklight Studio patch versions

问题描述

每当eclipse市场上有worklight工作室的新更新时，我都会安装它以获得最新的修复程序。当我在安装更新后重新启动eclipse时，Worklight会触发某种过程将我的项目更新到新版本。在此过程中，worklight会执行一些黑色伏都教并更新一些文件。

Whenever there is a new update of the worklight studio available in the eclipse market place I install it to get the latest fixes. When I restart eclipse after installing an update, Worklight triggers some kind of process to update my project to the new version. During this process worklight does some black voodoo and updates some files.

我想，一旦我提交这些文件，整个团队应该从eclipse市场下载并安装新的更新？因为在已经更新以使用较新版本的项目上使用旧版Worklight Studio不是一个好主意。

I suppose that once I commit these files, the entire team should download and install the new update from the eclipse market place? Because it can't be a good idea to work with an old version of Worklight Studio on a project that was already updated to work with a newer version.

这个主题是否有最佳实践？

Are there any best practices on this topic?

在常规基础上更新您的worklight工作室是个好主意吗？我不是在谈论小版本或主要版本，只是在Eclipse市场上可用的新补丁。例如，从platformVersion =6.2.0.00.20140701-1500更新到platformVersion =6.2.0.00.20140724-2139

Is it a good idea to update your worklight studio on a regular base? I'm not talking about minor or major versions, just a new patch which is available in the eclipse marketplace. Take for example an update from platformVersion="6.2.0.00.20140701-1500" to platformVersion="6.2.0.00.20140724-2139"

如果您选择坚持一个特定版本，您如何将此分发给开发团队中的新成员？你应该在某处保留一份副本吗？如果你需要修复，会发生什么？

If you choose to stick with one specific version, how do you distribute this to new members in your development team? Should you keep a copy somewhere? And what happends then if you need a fix?

推荐答案

我想一旦我提交这些文件，整个团队应该
下载并从日食市场安装新的更新？
因为在已经更新为使用
更新版本的项目上使用旧版本的
Worklight Studio不是一个好主意。

I suppose that once I commit these files, the entire team should download and install the new update from the eclipse market place? Because it can't be a good idea to work with an old version of Worklight Studio on a project that was already updated to work with a newer version.

如果您不单独工作，并升级您的Worklight Studio版本（然后执行黑巫毒并更新项目的文件），然后您交付更改您的SCM，然后是 - 您的团队成员也必须升级他们的Worklight Studio插件。

If you do not work alone, and you upgrade your Worklight Studio version (which then does "black voodoo" and updates the project's files) and you then deliver your changes to your SCM, then yes - your team members must upgrade their Worklight Studio plug-in as well.

是否有任何最佳做法这个主题？

Are there any best practices on this topic?

作为Worklight开发团队成员，我的建议是：如果我们向Eclipse Marketplace / IBM Fix Central发布修复程序 - 是的，安装它。

As a Worklight development team member, my advise is: if we publish a fix to Eclipse Marketplace / IBM Fix Central - yes, install it.

也就是说，您还可以查看IBM Fix Central中的修复错误（APAR）列表，并决定是否要升级安装。

That said, you can also review the list of fixed bugs ("APARs") in IBM Fix Central and decide whether you'd like to upgrade your installation.

在这样做之前，您可以选择首先在新的Eclipse和工作区中安装此修复程序，并确保您的项目不会被破坏。如果您觉得一切正常，请升级主开发环境并指示您的团队成员执行相同操作，然后使用新的Worklight Studio版本迁移项目并将更改交付给SCM。

Before doing so, you can opt to first install this fix in a new Eclipse and workspace and make sure your project is not getting broken. If you feel all is OK, upgrade your main development environment and instruct your team members to do the same, then, migrate the project using the new Worklight Studio version and deliver your changes to the SCM.

如果您选择坚持使用一个特定版本，那么您如何将
分发给开发团队中的新成员？你应该在某处保留一份副本吗？如果你需要修复，会发生什么？

If you choose to stick with one specific version, how do you distribute this to new members in your development team? Should you keep a copy somewhere? And what happends then if you need a fix?

根据版本在SCM中分支你的代码？但为什么会引起头痛......

Branch your code in the SCM based on the version? But why create headache...

这篇关于维护不同Worklight Studio补丁版本的最佳做法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！