A VCS is important whether you're working alone or not.
Really, it should be there for those moments when you realize you've made a mistake and want to rollback to what you had yesterday or this morning, or maybe you've just made a different decision in the implementation and want to branch so you can test things out without effecting the core of what you've written so far.
All in all, it is a nice thing to have. And you're better off being safe than sorry.
As far as the bug tracker, that is more your personal preference. I like Redmine, which integrates with SVN, git, etc. Others prefer Trac. But either way they will be able to run on your laptop while taking a minimal amount of resources. Especially when you consider that you're the only one using them.
I would check out http://bitnami.org/ they offer packaged Bug Trackers that you just execute and it will start its own little server on the port of your choice, and you can stop it when you're not using it.
You might want to consider an online repository and/or tracker/planner in addition to your local one. It's another stage of risk management and if, in the future, someone else joins your team, you can scale up just by granting them access.
Some options:
Source Control (Online):
Assembla - Public source is free, private repositories are paid
I think you should go with FogBugz. It's online, free for 2 developers, it integrates with your source control. I think bugtracking is second to source control in terms of project management especially for a single developer. You need to be able to tell when you've fixed all the reported bugs so you can predict a ship date on a feature etc etc..
An automated build process will take a huge burden off of you to be able to create your software on demand (in case of deletions etc). A CI process may be a little overkill but automated builds rule.
If you're worried about putting it on your laptop but still want to roll your own you can go to slicehost and get an ubuntu box for a subversion/trac solution online for 20 bucks a month. I do this for some of my personal projects...
对于您的情况，我会坚持使用简单的方法，如果您不想花费太多的开发时间来设置专用系统，即使只是 Outlook 中的专用待办任务列表也可能就足够了。 重要的是有一种方法可以确定您已经解决了报告的所有错误。
Subversion and Trac don't take up very much of your system resources especially when they're just sitting there waiting for you to use them.
I'm working on a small project, just 2 full-time developers, but I find I use our bug tracking software (Jira in our case, similar to Bugzilla), even just to keep track of my own bugs and issues. Easier than trying to remember the details of a bug when you get time to work on it later, and there's a very satisfying feeling to checking off issues after you've resolved them.
I'd stick with something simple in your case, even just a dedicated to-do task list in Outlook would probably suffice if you don't want to spend too much development time setting up a dedicated system. The important thing is to have a way to know for sure you've solved all of the bugs that were reported.
The real value of a bug tracker is that you don't lose track of anything that needs to be fixed. This is probably more important if there is only one of you as if there are more because there is no one else to remind you of what you have forgotten. I can remeber a project in the past where we had a simple typo type bug and only one application developer (I was the db developer) and he didn't have time to do it the day the CEO brought it up and a couple of months later when the CEO noticed it was still there he went ballistic. When you are juggling a whole bunch of tasks and possible bugs, it is very easy to lose sight of something (especially something you think of as trivial). That incident resulted in us getting a bug tracker and putting all tasks not just bugs into it and it was one of the best things we ever did. Just being able to say to the client when he wants something new, "Well here is my current list of tasks. How important is it compared to these things?" makes it worth its weight in gold especially when you are the only person. It will help you develop time estimates to and give you a place to document discussions and decisions concerning the task so no one can come back later and say they didn't know you were going to do that.
虽然不是一个明确的错误跟踪器，但您可以使用 tiddlywiki 这是一个独立 HTML 文件中的很棒的 wiki，这使得它很容易受到版本控制。
我之所以提到这一点，是因为迟早，除了错误列表之外，您还需要做笔记。
希望这可以帮助
Although not an explicit bug tracker, you can use tiddlywiki which is a great wiki in a self-contained HTML file, which makes it easy to have it under version control.
The reason I'm mentioning this, is because sooner or later, you will want to take notes in addition to the bug listings.
I would agree with JPunyon that you should use Fogbugz for bug tracking. I use if for my personal stuff and it is brilliant. While a bug tracker is not essential (though useful) if you are on your own, Source Code Control is essential. My product of choice is now Perforce which provides a fully functional 2 user copy you can download and use. It takes up very little resource and is easily tranferable when you upgrade machines. Theres a bit of a learning curve, but its worth it.
如果您在笔记本电脑上进行开发，您可能经常离线工作（我就是这样）。 考虑使用不需要互联网连接即可运行的错误跟踪器。 您可以查看 Artifacts - 简单、离线工作并且具有 Visual Studio 集成。
If you develop on your laptop, you probably work offline often (I do). Consider using bug tracker which doesn't require internet connection to operate. You may check Artifacts - simple, works offline and has Visual Studio integration.
It is mentioned that he has an msdn subscription. Although it's not my favorite version control system to use, Sourcesafe is very easy to set up and use, and not a bad solution if he is the only one using it (which it sounds like).
And yes, you want to use something to track bugs, even if it's just a simple list in Excel (or ) so you can keep track of what's still broke and what is fixed. I've done that before on small projects I have worked on.
您应该看看Fossil。 它是一个现代分布式（开源）版本控制系统，可在 Windows、Linux 和 Mac 上运行。 它还具有集成的错误跟踪器和 Wiki。 它是由 D. Richard Hipp 博士创建的，他也是 SQLite 的创建者。 事实上，它利用 SQLite 作为版本控制系统、错误跟踪器和 Wiki 的底层存储系统。
You should take a look at Fossil. It's a modern distributed (Open Source) version control system that runs on Windows, Linux, and Mac. It also has a integrated Bug Tracker and Wiki. It was created by Dr. D. Richard Hipp, the same guy who created SQLite. And, in fact, it utilizes SQLite as the underlying storage system for the version control system, bug tracker, and Wiki.
Fossil was specifically designed to meet the needs of the small development team or individual developer, and it does an excellent job. However, depending on the specifics, it can also work pretty well for a larger development team (for example, it is being used for SQLite's developement).
(I know this is an old question, but I came across Fossil about six months ago, and have become a big fan of it (coming from CVS -> SVN -> Hg -> Bzr -> Git over the past 15 years) for my own work, and for the team at work.)
发布评论
评论（10）
无论您是否单独工作，VCS 都很重要。
实际上，当您意识到自己犯了一个错误并想要回滚到昨天或今天早上的内容时，或者您可能只是在实施中做出了不同的决定并想要分支时，它应该在那里可以在不影响您迄今为止所写内容的核心的情况下进行测试。
总而言之，这是一件很好的事情。 安全总比后悔好。
至于错误跟踪器，这更多是您个人的喜好。 我喜欢 Redmine，它与 SVN、git 等集成。其他人更喜欢 Trac。 但无论哪种方式，它们都能够在您的笔记本电脑上运行，同时占用最少的资源。 尤其是当您认为您是唯一使用它们的人时。
我会查看 http://bitnami.org/ 他们提供打包的错误跟踪器，您只需执行它，它就会启动在您选择的端口上拥有自己的小服务器，当您不使用它时可以将其停止。
A VCS is important whether you're working alone or not.
Really, it should be there for those moments when you realize you've made a mistake and want to rollback to what you had yesterday or this morning, or maybe you've just made a different decision in the implementation and want to branch so you can test things out without effecting the core of what you've written so far.
All in all, it is a nice thing to have. And you're better off being safe than sorry.
As far as the bug tracker, that is more your personal preference. I like Redmine, which integrates with SVN, git, etc. Others prefer Trac. But either way they will be able to run on your laptop while taking a minimal amount of resources. Especially when you consider that you're the only one using them.
I would check out http://bitnami.org/ they offer packaged Bug Trackers that you just execute and it will start its own little server on the port of your choice, and you can stop it when you're not using it.
除了本地存储库和/或跟踪器/规划器之外，您可能还想考虑使用在线存储库和/或跟踪器/规划器。 这是风险管理的另一个阶段，如果将来其他人加入您的团队，您只需授予他们访问权限即可扩大规模。
一些选项：
源代码控制（在线）：
免费的私人存储库需付费
私人存储库是付费的
个跟踪/项目管理
You might want to consider an online repository and/or tracker/planner in addition to your local one. It's another stage of risk management and if, in the future, someone else joins your team, you can scale up just by granting them access.
Some options:
Source Control (Online):
free, private repositories are paid
private repositories are paid
Bug Tracking/Project Management
我认为你应该使用FogBugz。 它是在线的，免费供 2 名开发人员使用，它与您的源代码管理集成。 我认为在项目管理方面，错误跟踪仅次于源代码控制，尤其是对于单个开发人员而言。 您需要能够知道何时修复了所有报告的错误，以便您可以预测某个功能的发布日期等。
自动化构建过程将为您减轻巨大的负担，以便能够在需求（在删除等情况下）。 CI 过程可能有点矫枉过正，但自动化构建规则。
如果您担心将其放在笔记本电脑上，但仍想自己动手，可以访问 slicehost 并每月花费 20 美元在线获取一个用于 subversion/trac 解决方案的 ubuntu 盒子。 我这样做是为了我的一些个人项目......
I think you should go with FogBugz. It's online, free for 2 developers, it integrates with your source control. I think bugtracking is second to source control in terms of project management especially for a single developer. You need to be able to tell when you've fixed all the reported bugs so you can predict a ship date on a feature etc etc..
An automated build process will take a huge burden off of you to be able to create your software on demand (in case of deletions etc). A CI process may be a little overkill but automated builds rule.
If you're worried about putting it on your laptop but still want to roll your own you can go to slicehost and get an ubuntu box for a subversion/trac solution online for 20 bucks a month. I do this for some of my personal projects...
Subversion 和 Trac 不会占用太多系统资源，尤其是当它们只是坐在那里等待您使用它们时。
我正在开发一个小项目，只有 2 名全职开发人员，但我发现我使用我们的错误跟踪软件（在我们的例子中是 Jira，类似于 Bugzilla），甚至只是为了跟踪我自己的错误和问题。 当您稍后有时间处理错误时，这比尝试记住错误的详细信息更容易，并且在解决问题后检查问题会带来非常令人满意的感觉。
对于您的情况，我会坚持使用简单的方法，如果您不想花费太多的开发时间来设置专用系统，即使只是 Outlook 中的专用待办任务列表也可能就足够了。 重要的是有一种方法可以确定您已经解决了报告的所有错误。
Subversion and Trac don't take up very much of your system resources especially when they're just sitting there waiting for you to use them.
I'm working on a small project, just 2 full-time developers, but I find I use our bug tracking software (Jira in our case, similar to Bugzilla), even just to keep track of my own bugs and issues. Easier than trying to remember the details of a bug when you get time to work on it later, and there's a very satisfying feeling to checking off issues after you've resolved them.
I'd stick with something simple in your case, even just a dedicated to-do task list in Outlook would probably suffice if you don't want to spend too much development time setting up a dedicated system. The important thing is to have a way to know for sure you've solved all of the bugs that were reported.
错误跟踪器的真正价值在于您不会丢失任何需要修复的内容。 如果只有你们一个人，就像有更多人一样，这一点可能更重要，因为没有其他人提醒您忘记了什么。 我记得过去的一个项目，我们有一个简单的拼写错误，只有一名应用程序开发人员（我是数据库开发人员），而在首席执行官提出这个问题的那天，他没有时间去做这件事，花了几个月的时间后来，当首席执行官发现它还在那里时，他勃然大怒。 当您处理一大堆任务和可能的错误时，很容易忽视某些事情（尤其是您认为微不足道的事情）。 那次事件导致我们得到了一个错误跟踪器，并将所有任务都放入其中，而不仅仅是错误，这是我们做过的最好的事情之一。 当客户想要新东西时，只需能够对他说：“这是我当前的任务清单。与这些事情相比，它有多重要？” 使它物有所值，尤其是当您是唯一的人时。 它将帮助您估算时间，并为您提供一个记录有关该任务的讨论和决策的地方，这样就没有人可以稍后回来说他们不知道您要这样做。
The real value of a bug tracker is that you don't lose track of anything that needs to be fixed. This is probably more important if there is only one of you as if there are more because there is no one else to remind you of what you have forgotten. I can remeber a project in the past where we had a simple typo type bug and only one application developer (I was the db developer) and he didn't have time to do it the day the CEO brought it up and a couple of months later when the CEO noticed it was still there he went ballistic. When you are juggling a whole bunch of tasks and possible bugs, it is very easy to lose sight of something (especially something you think of as trivial). That incident resulted in us getting a bug tracker and putting all tasks not just bugs into it and it was one of the best things we ever did. Just being able to say to the client when he wants something new, "Well here is my current list of tasks. How important is it compared to these things?" makes it worth its weight in gold especially when you are the only person. It will help you develop time estimates to and give you a place to document discussions and decisions concerning the task so no one can come back later and say they didn't know you were going to do that.
虽然不是一个明确的错误跟踪器，但您可以使用 tiddlywiki 这是一个独立 HTML 文件中的很棒的 wiki，这使得它很容易受到版本控制。
我之所以提到这一点，是因为迟早，除了错误列表之外，您还需要做笔记。
希望这可以帮助
Although not an explicit bug tracker, you can use tiddlywiki which is a great wiki in a self-contained HTML file, which makes it easy to have it under version control.
The reason I'm mentioning this, is because sooner or later, you will want to take notes in addition to the bug listings.
Hope this helps
我同意 JPunyon 的观点，您应该使用 Fogbugz 进行错误跟踪。 我将 if 用于我的个人物品，它非常棒。 如果您独自一人，错误跟踪器并不是必需的（尽管很有用），但源代码控制是必不可少的。 我现在选择的产品是 Perforce，它提供了功能齐全的 2 用户副本，您可以下载和使用。 它占用的资源很少，并且在升级机器时可以轻松转移。 有一点学习曲线，但这是值得的。
I would agree with JPunyon that you should use Fogbugz for bug tracking. I use if for my personal stuff and it is brilliant. While a bug tracker is not essential (though useful) if you are on your own, Source Code Control is essential. My product of choice is now Perforce which provides a fully functional 2 user copy you can download and use. It takes up very little resource and is easily tranferable when you upgrade machines. Theres a bit of a learning curve, but its worth it.
如果您在笔记本电脑上进行开发，您可能经常离线工作（我就是这样）。 考虑使用不需要互联网连接即可运行的错误跟踪器。 您可以查看 Artifacts - 简单、离线工作并且具有 Visual Studio 集成。
If you develop on your laptop, you probably work offline often (I do). Consider using bug tracker which doesn't require internet connection to operate. You may check Artifacts - simple, works offline and has Visual Studio integration.
据说他订阅了 msdn。 虽然这不是我最喜欢使用的版本控制系统，但 Sourcesafe 非常容易设置和使用，如果他是唯一使用它的人（听起来像），那么这也是一个不错的解决方案。
是的，您希望使用某些东西来跟踪错误，即使它只是 Excel（或 ）中的一个简单列表，这样您就可以跟踪仍然存在问题的内容和已修复的内容。 我之前在我从事过的小项目中就这样做过。
It is mentioned that he has an msdn subscription. Although it's not my favorite version control system to use, Sourcesafe is very easy to set up and use, and not a bad solution if he is the only one using it (which it sounds like).
And yes, you want to use something to track bugs, even if it's just a simple list in Excel (or ) so you can keep track of what's still broke and what is fixed. I've done that before on small projects I have worked on.
您应该看看Fossil。 它是一个现代分布式（开源）版本控制系统，可在 Windows、Linux 和 Mac 上运行。 它还具有集成的错误跟踪器和 Wiki。 它是由 D. Richard Hipp 博士创建的，他也是 SQLite 的创建者。 事实上，它利用 SQLite 作为版本控制系统、错误跟踪器和 Wiki 的底层存储系统。
Fossil 是专门为满足小型开发团队或个人开发人员的需求而设计的，而且它做得非常出色。 然而，根据具体情况，它对于更大的开发团队也可以很好地工作（例如，它被用于 SQLite 的开发）。
（我知道这是一个老问题，但我大约六个月前遇到了 Fossil，并且成为了它的忠实粉丝（来自 CVS -> SVN -> Hg -> Bzr -> Git 过去15 年）为了我自己的工作，也为了工作中的团队。）
You should take a look at Fossil. It's a modern distributed (Open Source) version control system that runs on Windows, Linux, and Mac. It also has a integrated Bug Tracker and Wiki. It was created by Dr. D. Richard Hipp, the same guy who created SQLite. And, in fact, it utilizes SQLite as the underlying storage system for the version control system, bug tracker, and Wiki.
Fossil was specifically designed to meet the needs of the small development team or individual developer, and it does an excellent job. However, depending on the specifics, it can also work pretty well for a larger development team (for example, it is being used for SQLite's developement).
(I know this is an old question, but I came across Fossil about six months ago, and have become a big fan of it (coming from CVS -> SVN -> Hg -> Bzr -> Git over the past 15 years) for my own work, and for the team at work.)