I learned git 3 days ago and I actually love it. It is very easy to create branches and for your big feature you are trying to implement, it is better to organize it into different milestones. Because in git/chromium world, every branch can have at most one CL (Change List, Review). So if you define your milestones for your big feature before hand, by describing what your trying to do, you can then define how you can apply them to different branches and incrementally review each branch. Its easier for you to manage as well for the reviewers. Make sure you present a proposal on what your trying to accomplish and attach it to a tracking bug. For example, write up a detailed design document on what your big feature will do and then request comments on the discuss mailing lists. Its good to address the issues on why your big feature should be done in chrome. Don't put a lot of work implementing this before people think your design and idea is ok for the chromium project.
-- Mohamed Mansour On Wed, Jun 17, 2009 at 12:35 AM, 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 -~----------~----~----~----~------~----~------~--~---
