It might take a bit of getting used to, but git is a revision control tool that allows you to create your own personal branches. Many Chromium developers use it for their daily work. The way it interfaces with svn is a bit clunky, but if you're not committing very often, it probably won't matter much to you.
That said, I'm not sure if you're going to be able to do work like you have on other projects. We take code reviews very seriously, and it's pretty hard to do code reviews except in small increments. This is partially because it's hard for a reviewer to understand all the elements of a large change. But it's also partially because a reviewers will have suggestions for how you could do things better. Even people who have been working on Chromium from the beginning still go through reviews and often need to tweak designs based on said reviews. One way or another, you'll need to figure out how to get from point A to point B in small increments. Sometimes I like to prototype in a branch and then re-implement it in the trunk as multiple smaller patches. This seems wasteful, but since you're not worrying about the details in the first phase and you know exactly what you need to do and how to do it in the second phase, it's actually not a bad way to go. If, on the other hand, you understand the path you want to take pretty well, then maybe you should just do it in the trunk. You can do it behind a run-time flag if necessary. Out of curiosity, what are you planning on working on? J On Tue, Jun 16, 2009 at 9:35 PM, Daniel Cowx <[email protected]> wrote: > > What is the recommended procedure for working on long/big features? > > In the past, I've always created a separate branch and then done all > my work there. I then do regular integrations from trunk into my > branch to ensure that that my branch doesn't drift too far out of sync > with the trunk (i.e. so as to minimize the amount of merge work I have > to do when I'm ready to have my branch-specific changes reviewed and > merged back into the trunk). However, being that chromium is hosted on > a remote SVN server which I have no control over, what is the > recommended way of doing dev? > > I'd really like to be able to do commits of my incremental work, but > without a sep branch to fiddle around with, how can I accomplish this? > > All input and feedback welcome. > > Cheers, > Daniel > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
