On 9/8/08, Andy Lester <[EMAIL PROTECTED]> wrote: > > > On Sep 8, 2008, at 4:22 PM, Brian Aker wrote: > > We can use all of them. >> > > > How are we tracking that, then? Assigning someone to the task? How do we > make sure we don't lose 'em?
Well, right now we're not. As far as I know they're not *in* the code yet, so there's nothing to track. Do we expect there to be many revisions of the patchsets, such that we actually have to track this? It's pretty cool that we have 5.0 and 5.1 patches, but back in April 2007, when the 4.1 patches came out, we were told to expect version 5 patches "soon"....(extremely better late than never, but I'm pretty surprised at how "late"....I know, it's free, what more do I want?) Anyway, point being, is Google expecting to make their patchsets incompatible with each other? Or use features someone might not want? I don't think so -- I gather that we will just apply the patch as a google-patch branch or whatever, and if we need to roll that patchset back, we can....(am I missing something else?). I gather this will be tracked the same way we track every other patchset -- by using a blueprint or creating a bug and associating the patch merge with that blueprint/bug. -Sheeri
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
