对票证进行版本控制? [英] Version control for tickets?

查看:169
本文介绍了对票证进行版本控制?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

与Git独立内容托管的概念相关



我想分开3件事:票务 - 版本控制(管理),编程 - 版本控制和结构 - 版本控制(更多这里)。现在每个人都应该能够看到门票,以及他们是如何从一个想法演变成一个代码/产品的。目前,我遇到了很大的问题,因为门票位于Bitbucket和Github的私有棺材中,显然是他们锁定用户的业务策略。我想在某些存储库管理票据此处这里这里。如果我做一张票,我想承诺。我想跟踪我的票,因为我希望能够稍后更改提供者。 Github有一些很好的功能,比如打卡片(更多这里),但是通过Bitbucket很难使用。我想控制我的门票并随时添加功能。那么如何才能对票证进行版本控制呢?

  | --->票据的版本控制(Ticgit版本还不存在)
|
--- | --->代码的VC(git)
|
| --->结构化VC(?maven ??运行,部署,??)
|
| ---> perm'VC(Gitolite)

也许相关



  1. 版本控制版本控制?


  2. 版本控制中的项目结构

  3. .com / questions / 4952 / database-version-control> https://stackoverflow.com/questions/4952/database-version-control


>


解决方案

我不确定您的问题到底是什么:它更像是一个意向声明一个问题。但假设你正在寻找一个可以让你这样做的系统,你可能会对 ticgit ,一个使用Git分支作为后端的错误跟踪系统,让您在分叉代码的同时分叉和分支错误跟踪数据。


Conceptually related to the independent content-hosting with Git here.

I would like to separate 3 things: ticketing -version-control (management), programming -version-control and structural -version-control (more here). Now everyone should be able to see tickets and how they have evolved from an idea into a code/product. Currently, I have large problems because tickets are in proprietary coffins in Bitbucket and Github, apparently their business strategy to lock users. I want to manage my tickets in some repository -- related tickets here, here and here. If I do a ticket, I want to commit that. I want to keep track of my tickets also because I want to be able to change the provider later easily. Github has some good features such as punch -cards (more here) but otherwise harder to use over Bitbucket. I want to control my tickets and add features whenever I want to. So how can I have a version-control over tickets?

   |---> tickets' version-control (Ticgit -version-not-yet-exist)
   |
---|---> code's VC (git)
   |
   |---> structural VC (? maven ?? runs, deployes, ??)
   | 
   |---> perms' VC (Gitolite)

Perhaps related

  1. Version control for version control?

  2. Structure of Projects in Version Control

  3. https://stackoverflow.com/questions/4952/database-version-control

解决方案

I'm not sure exactly what your question is: it reads more like a statement of intent than a question. But assuming you're looking for a system that lets you do that, you might be interested in ticgit, a bug-tracking system that uses a Git branch as a backend, letting you fork and branch the bug tracking data at the same time as forking the code.

这篇关于对票证进行版本控制?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆