在非 DEV 环境中进行的修改称为什么?
在应用程序生命周期管理中,通常有一些环境。例如:
DEV->分期->生产
通常,您会在 DEV 环境中进行开发,并将您的开发阶段到暂存和生产。
但可以直接修改 PRD 环境(例如快速修复错误)。 你如何调用这个过程(在非DEV环境中修改你的代码)?
我以为它被称为“修补程序”,但我在 Google 中没有看到相关搜索结果。
In application life-cycle management, it's common to have some environments. For example:
DEV -> Staging -> Production
Normally, you would develop in the DEV environment and stage your developments to Staging and Production.
But it's possible to directly modify the PRD environment (to quickly fix a bug, for instance).
How do you call this procedure (the modification of your code in an environment that is not the DEV environment)?
I thought it was called "hotfix" but I see no related search results in Google.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
与您的参考实体
环境
相反,在我看来,该实体是您的 SCM 内的分支
。考虑到这一点,你是绝对正确的:根据我的经验,它始终是一个修补程序分支。
对于我目前居住的星球 TFS,各种分支指南对此进行了描述,包括这个 - 这是被认为是最好的(如果不是最好的)。
我在 UNIX/ClearCase 星球上也有类似的经历,同样是 Hotfix 分支 - 它们被命名为“MaintenanceRelease”分支。其中包含一个或多个修补程序,有时也可以将备受期待的功能合并到其中。
我不会期望在任何公司中看到“修补程序”环境。 “修补程序”解决了客户遇到的任何可能的危机,但根据定义,这是相当模糊的。所以拥有这样的环境,可能就是一个乌托邦。
有一次,他们有一个“BLS”实验室(“后台支持”),支持人员使用该实验室来重现客户场景。开发提供的修补程序在发布前已部署在本实验室中。这在某种程度上是一个“修补”环境 - 不过,请注意此安装花费了数百万美元。
As opposed to your reference entity
Environment
the entity is, in my opinion,Branch
within your SCM.With this in mind, you are absolutely right: In my experience it was always a Hotfix branch.
For planet TFS where I currently reside, this is described in various branching guidelines including this one - which is considered to be among the best (if not THE best).
I had similar experiences in a UNIX/ClearCase planet, again with Hotfix branches - they were named as "MaintenanceRelease"-branches. Those contained one or more Hotfixes, occasionally a highly anticipated Feature could be merged into that as well.
I wouldn't ever expect to see in any company a "Hotfix"- Environment. 'Hotfixes' address any possible crisis that a customer has experienced and that is per definition pretty vague. So having such an environment, is possibly a Utopia.
In one occasion, they had a "BLS" - lab ("Back Level Support") which was used by Support-People to reproduce customer scenarios. Hotfixes provided by Development were deployed in this Lab before release. This is in some extend a "Hotfix" environment - still, beware that this installation costed millions.