git - Should checkins be small steps or complete features? -

Two usage of version control directs different test styles.

• Distribution Centers : A complete feature will usually be displayed in the changes. Generally these checkins will grow.

• Rollback Centered : Changes will be small steps in the individual so that history can act as an incredibly powerful undo. These checkin in general will be small. This style is more developer friendly.

I would like to use my version control in a really powerful way, while some persistence codes / in this way I am scared of making drastic changes to try just one possible solution. However, it gives me a history of a split file with checkins "did not work well" checkins.

Instead, I try to fully reflect my changes, I use software for my version control experiment, however, it is easy for users / maintenance to find out how code is developed. There are many advantages for code reviews, management of many branches etc.

So what is a developer to do? Checkin small steps or full features?

itemprop = "text">

The beauty of the DVCS system is that you can be both , because unlike a CVCs in DVCS, publishing Orphogonal for deposit , in CVCs, each commute is automatically published, but it is in a DVC, only published when they pushed Goes .

Then, less small steps, but only published work facilities

If you are worried about the pollution of your history, you can rewrite it. You must have heard that the rewrite history is bad, but this is not true: only published Writing history is bad, but again, since publication and being committed, you can re-write your unpublished history before publishing it.

For example, how Linux development works. Linus Torvalds are very worried about keeping history clean. Very early in the e-mail about Git, he said that the published history should not be liked by you actually developed it, but how would you be developed it, If you were omniscient, could see in the future and never made any mistake.

Now, Linux is a bit special: at each hour for 1 hour, each commits 24 hours each hour, 7 days a week, 365 days a year, nights, weekends, holidays and natural disasters. And this rate is still increasing. Just imagine that if anybody becomes committed to doing typo and brain work, then it becomes more.

But developers themselves want to do themselves in their own personal repository often.