On Sat, Jul 15, 2017 at 02:12:42PM -0400, Doug Ledford wrote: > On 7/14/2017 10:28 AM, Christopher Lameter wrote: > > On Thu, 13 Jul 2017, Sagi Grimberg wrote: > > > >> Join on the awesomeness. > > > > It would even be more awesome if we had multiple people that can work the > > release process so that we do not have a single person bottleneck. > > > > Doug: Would you please do some more detailed planning and delegate things > > as possible? A couple of developers should be able to review the current > > state of things and help to move things forward if there is a bottleneck > > currently or coming up. > > > > I am, without a doubt, reworking my process. I will not be syncing up > against Dave Miller's tree any more. When I take patches, they should > apply cleanly to my tree and work without dependencies. If there are > dependencies, then people need to send the dependencies through Dave's > tree (assuming that's where they go) in release X, and then send the > dependent code to my tree in release X + 1. There are two parts in this proposal, while second part (dependency) is fair enough and possible to meet, it is unclear to me the first part (apply cleanly). 1. On which branch should we send our topics? 2. Are you acknowledge that this branch is going to be updated +/- on daily basis? 3. How do you see us submitting multiple topics? Sequential submission - like DaveM, and it should be applied close to submissions (if no objections and so on ..). Or parallel submissions - like it is now and the conflicts are unavoidable. 4. If 2 and 3 are not going to change, should we wait till late rc and submit all (100+) patches at one or two shots to avoid merge conflicts? I would be glad to get the whole picture of submission process, before we are moving forward. Thanks > > -- > Doug Ledford <dledford@xxxxxxxxxx> > GPG Key ID: B826A3330E572FDD > Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD >
Attachment:
signature.asc
Description: PGP signature
