Soho Posted December 14, 2011 Report Share Posted December 14, 2011 Different developers check in their changes with different frequency. Some check in at the end of the day, some, like me, check in every few unit tests or changes, which could be many times an hour. I like a long smooth history of changes. Some like changes to be more profound. I will argue that very frequent check-ins are better than those "a couple a day" when using a branch-per-task workflow, but is there a performance consideration for a certain check in frequency when using Plastic? Link to comment Share on other sites More sharing options...
psantosl Posted December 14, 2011 Report Share Posted December 14, 2011 I checkin after a few changes that make sense. I try to "tell a story about my changes" on each series of checkins... SO... as frequent as possible!!!! Link to comment Share on other sites More sharing options...
Soho Posted December 14, 2011 Author Report Share Posted December 14, 2011 The question is whether Plastic is optimized for frequent checkin or if performance is better with fewer checkins. Link to comment Share on other sites More sharing options...
manu Posted December 15, 2011 Report Share Posted December 15, 2011 Hi Soho! I also prefer to commit my changes continuously. It's my branch and inside it I do what I want. There is no problem to create as many changesets as you want.... Manu. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.