创建一个“稳定”的环境从 SVN 存储库发布
我有几个开发人员正在开发一个项目并提交到 /trunk
在理想的世界中，他们的代码将没有错误，并且他们会在提交之前完成问题的所有部分，但正如我们所知，情况并非总是如此。
通常我会浏览并只更新我知道好的文件，然后测试并发布公共版本，但这变得越来越难 - 使用 SVN，当你更新文件时，要么全部要么全无，除非你想开始添加手动编辑文件 - 烦人。
所以我需要一种方法，获取代码，并获得更细粒度的方法来拉入他们的更改 - （几乎像 git add --patch 的 UI），然后我可以浏览每个更改集（直到行）并添加有效的内容然后发布构建。 （标记这个是理想的）。
有人有什么建议吗？
I got several developers who are working on a project and committing into /trunk
In an ideal world, their code would be bug free and they would of completed all parts of a problem before committing, but as we know that is not always the case.
Often I will go through and only update the files which I know are good, then test and release a public build but it's getting harder and harder - with SVN when you update a file it's ALL or nothing, unless you want to start adding in the edits by hand to files - annoying.
So I need a way, of taking the code, and getting a more fine grained approach to pulling in their changes - (almost like the UI of git add --patch), I can then go through each change set (down to the line) and add things which work then release build. (tagging this would be ideal).
Anyone have any suggestions?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这就是分支的用途。
如果主干应该是稳定分支，那么您可以让每个开发人员在自己的分支中工作。然后，您将这些分支的特定更改合并到主干中。当您准备好发布时，您可以从主干创建一个标记分支。
或者，您可以使用 trunk 作为每个人都提交的不稳定开发分支，并将特定更新合并到稳定发布分支中。
This is what branches are for.
If trunk is what should be the stable branch, then you could have each developer work in their own branch. You then merge specific changes from those branches into trunk. When you're ready to do a release you can create a tagged branch from trunk.
Alternatively you could use trunk as the unstable dev branch that everyone commits into, and merge specific updates from that into a stable release branch.
简而言之，您无法通过源代码控制来修复您的流程。如果你想尝试，svn 并不是你所描述的过程的朋友。
In short, you can't fix your process with source control. If you want to try, svn is not your friend for the process you are approximately describing.