-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 05/01/2016 08:01 PM, Emilien Macchi wrote:
<snip/> >> If a feature can't land without disruption, then why not using a >> special branch to be merged once the feature is complete ? > > The problem is that during our work, some people will update the > manifests, and it will affect us, since we're copy/pasting the > code somewhere else (in puppet-tripleo), that's why we might need > some outstanding help from the team, to converge to the new model. > I know asking that is tough, but if we want to converge quickly, > we need to make the adoption accepted by everyone. One thing we can > do, is asking our reviewer team to track the patches that will need > some work, and the composable team can help in the review process. > > The composable roles is a feature that we all wait, having the > help from our contributors will really save us time. s/wait/want/ I expect. Well said. I understand the reservations on the -1 for non-composable role patches. It *does* feel a bit strong, but in the end I think it's just being honest. The likelihood that a patch on tht is going to land "as is" prior to the merge of the related composable role changes seems really unlikely. I for one, am willing to do what I can to help anyone who has had their patch pre-empted during this period get their patch refactored/ported once the comp-roles thing has settled down. Cheers, Brent -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXJ5KpAAoJEIXWptqvFlBWmA8P/1dBlsCNYIqOHBBWxzEnLM41 gP/K+UsGFHaXj86yOdus5gp58/JFX9KJ+mqr0Yi/8ail+h+t0yjgcCXLlp6HUTKo 7OtNfAzPMDeDkquB5R7WREJfLdtP7tVpBsd0Ezs00y5ZDUuDk/J0waleQFtAKUjr Xiip2y/e8tZMdWa0gvp/q+kWJ3v+YhAnl9PNQMCeIGf/IwDQrTNYvDTIChLx6dud g7tWfH+ej6nL/ty8UM4R3ac94ZyZLrxprShbdpAh798kYhrR1WPju+hmBgln8rlx fcTzXq8b428QzCmNKFeKuNmP32yXjOCZlEi2/NijfiR7nFY6sLvh7ROIODiwmzx8 fPSb1W8bLqIijeAUy2YpZFfvbe+NZdn2iIHjseS6Yu4D85NakUunkrBJEpbnCy8L 26N9ShseHbVRckpMSyxEyi+jJfJcCp4FzR26SUFUamPcusMQVlBDQlhOh/8lr/Lq frhxcYCn45JZ/R2pc3PS2HnRapmvM/TLxdFhbteUFMcEXBT4dvdQPcQdqH1Kx/Yw S5C+1CESRMGH2KpqghHaMNnySYHFHYQNmCKEVfJjERGbI/U5dEEogIUuzHXHQlYV kL83XvMh6gGHfRwbmeTOLsrR86c8+u3vaE5PzHPxQ3IBseezmRYiN2fmNclYsg8B LvyHYCRNvOcj1y8gr0Yr =obJ6 -----END PGP SIGNATURE----- __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
