Github项目和里程碑之间的区别/关系是什么(What is the difference / relationship between Github Projects and Milestones

Github项目和里程碑之间的区别/关系是什么(What is the difference / relationship between Github Projects and Milestones)

Github最近的更新在Github工作流程中添加了一些名为Projects的内容，由于我没有任何具体的项目跟踪工具 （如Jira或Trello）的经验（至少我注意到相似性） ，任何人，请详细说明关于 Github的里程碑与新项目之间的（关键）差异 ？

如果我理解正确， 里程碑是将问题组织到较小的“子项目”中的一种方式 - 小于整个“项目”（在我的世界观中，由存储库代表）。 当所有问题都完成/关闭时，里程碑可以被认为是完整的 。

正如我所看到的，新推出的项目也是将问题组织到小型存储库 “子项目”（尽管称为项目 ）的一种方式。 我理解工作流程应该略微不同，比“简单”的里程碑更细粒度。

那么， 项目是什么补充里程碑 （或更重要的是里程碑补充项目现在？）或者我应该宁愿查看项目作为里程碑的替代品 ？

项目实际落在repository[-milestone]-issue层次结构中的哪里？

遗憾的是，Github关于项目介绍的博客文章没有提到任何关系（ https://github.com/blog/2256-a-whole-new-github-universe-announcing-new-tools-forums-and特征 ）。

我不知何故觉得有一个，但我不能把手指放在它上面。

The recent update to Github added something called Projects into the Github workflow, and because I don't have any particular experience with project tracking tools such as Jira or Trello (hey, at least I noticed the similarity), could anyone, please, elaborate on the (key) differences between Github's Milestones and the new Projects?

If I understand correctly, Milestones are a way of organizing issues into smaller "sub-projects" - smaller than the whole "project" (which, in my world view, is represented by the repository). When all issues are done/closed, the milestone can be regarded as complete.

The newly introduced Projects are also, as I see it, a way of organizing issues into smaller-than-the-repository "sub-projects" (albeit called Projects). I understand the workflow is supposed to be slightly different and more fine-grained than with "mere" Milestones.

So, are Projects something that supplements Milestones (or rather Milestones supplement Projects now?) or should I rather view Projects as a replacement of Milestones?

Where exactly do the Projects actually fall into the repository[-milestone]-issue hierarchy?

Sadly, the Github's blog entry about the introduction of the Projects doesn't mention any relationship (https://github.com/blog/2256-a-whole-new-github-universe-announcing-new-tools-forums-and-features).

I somehow feel there is one, but I can't put a finger on it.

最满意答案

我想知道完全一样的事情。 这是我想出来的

首先，我们回顾一下主要的相似点和不同点：

一个问题可以属于多个项目，但只有一个里程碑 项目永远不会完成 。 没有进度条或截止日期。 另一方面，里程碑有一切，但缺乏任何形式的组织。 一个问题是在一个里程碑，还是不是。 问题可以由里程碑过滤，但不能由项目过滤。 如@cmonkey所指出的，现在可以通过Project和Milestone过滤问题。 项目可以包含Notes （可以转换为问题），因此它不会以模糊的想法污染问题跟踪器 项目可以跨越多个里程碑，里程碑可以包含不同项目的部分。 组织也可以有项目。 这些项目可以包括来自组织中任何存储库的票据，这使得它非常有用。

所以我看到的方式是， 项目是一个完全独立的方式来在更高层次上可视化和组织你的工作（认为“项目管理”，多个团队，多个存储库等），而里程碑是组织您的截止日期和更新版本（认为“发布管理”，“版本”等）。 考虑到这一点，一个问题只属于一个里程碑（它只发布或推送到生产一次），但可以作为不同的项目的一部分是有道理的。

我确定他们是其他方式来看它，而且我有兴趣听到其他意见。

I'm wondering the exact same thing. Here is what I came up with.

First, let's review the main similarities and differences:

An issue can belong to multiple Projects, but only one Milestone. Projects are never complete. There is no progress bar, or deadline. Projects have no progress bar or deadline, but can now be closed (as pointed out by @Sheen) Milestones on the other hand have all that, but lack any form of organization. An issue is either in a milestone, or isn't. (They can be ordered as pointed out by @Nick McCurdy) Issues can be filtered by Milestone, but not by Project. As pointed out by @cmonkey, issues can now be filtered by Project as well as Milestone. Projects can contain Notes (which can be converted as issues) so it doesn't pollute the issue tracker with vague ideas A Project can span over multiple Milestones, and a Milestone can contains parts of different Projects. An Organization can have Projects as well. These projects can include tickets from any repository in the organization, which makes it quite useful.

So the way I see it, is that Projects are a completely separate way to visualize and organize your work on an higher level (think "project management", multiple teams, multiple repository, etc.), while Milestones are a way to organize your deadlines and releases on a more basic level (think "release management", "versions", etc.). With this in mind, it makes sense that an issue only belongs to one Milestone (it's only released or pushed to production once) but can be part of different Projects.

I'm sure they are other ways to look at it though, and I'm interested to hear other opinions.

Edit December 2017

Some time ago, after working with Milestones and Projects for over a year, I realized there is another important aspect I had completely overlooked.

Milestones is a tool for Scrum methodology. Milestones are good for timeboxed iterations and working in sprints with batches of issues. Projects is a tool for Kanban methodology. Projects are good for continuous delivery and steady flow of work.