On Dec 28, 2007 4:14 PM, Jim Gettys <[EMAIL PROTECTED]> wrote: > I guess there may have been misunderstanding: since the beginning of > December (or maybe before), only things intended for Update.1 and issues > approved for fixing in Update.1 needing testing were supposed to be > loaded into joyride. As such, there should be no cherry picking of > fixes needed, when you are at a completed state.
I don't mean cherry picking of single fixes/git commits, but cherry picking of packages from joyride to Update.1. My understanding of the process is: 1 rwh fix bug A in sugar 2 tomeu fix bug B in sugar 3 tomeu builds a sugar package with bug A and bug B fixes in it. 4 the package goes in joyride and tomeu test it out 5 tomeu request ApprovalForUpdate 6 marco or jg approves the package 7 dgilmore tag (in other words cherry pick) the package for Update.1 With this process, if ticket A and ticket B are closed *before* 5, it will be hard to track which packages needs to be tagged for Update.1 (and likely that we will miss some of them). Marco _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
