Thanks for coordinating schedules Brain. Im quite glad to be on EST :) We should also establish a medium: Google hangouts were not well received by everyone last year, (not everyone had a G+ account), but I cannot think of anything that is nearly as convenient. Suggestions?
-Michal On Tue, Jan 15, 2013 at 7:52 AM, Becky Gibson <gibson.be...@gmail.com>wrote: > Am I correct in assuming US pacific time zone? > > Sent from my iPad > > On Jan 15, 2013, at 4:36 AM, Brian LeRoux <b...@brian.io> wrote: > > > Works for me, however, to accommodate EU community we must to consider > > times unholy. This is Apache Way from what I understand. > > > > I created a form to help us pick a time to talk. > > > > http://goo.gl/h9d1a > > > > > > > > On Mon, Jan 14, 2013 at 7:06 PM, Michal Mocny <mmo...@chromium.org> > wrote: > >> Okay gentlemen, I think there have been countless good points made from > all > >> parties, but also some bike-shedding. > >> > >> Perhaps it is time to schedule some face-time to better articulate some > of > >> the finer points, and to help come to some consensus? > >> > >> -Michal > >> > >> > >> On Mon, Jan 14, 2013 at 9:40 PM, Marcel Kinard <cmarc...@gmail.com> > wrote: > >> > >>> Sorry if this got asked before, but does a feature branch get deleted > >>> after it is merged? Just wondering about branch clutter over a long > period, > >>> or if this is just the same as a topic branch using today's committer > >>> workflow. > >>> > >>> > >>> On 1/14/2013 5:34 PM, Brian LeRoux wrote: > >>> > >>>> You work on a Feature branch. It gets rolled into Dev as needed so > >>>> others can merge / collaborate on said feature. When it feels right > >>>> instead of merging a large set of potentially breaking commits to > >>>> Unstable the dev working on said feature just merges that feature. > >>>> This would require more responsibility for the committer to keep track > >>>> of their feature branches which I could see as being more overhead. > >>> >
