I don't mind testing and doing prep work to give feedback to the Pulp team of any breakages for a beta, but I have enjoyed seeing us avoid tagging in beta's and to some extent RCs to our tags. I prefer we not lock ourselves into a release that then ends up with hiccups and headaches and delays our release. If a feature is being tackled that requires Pulp changes, I would put the onus on the developers working on the feature to ensure that the upcoming release of Pulp has everything they need and to some extent doesn't break Katello. This would help ensure that the release nanny has a smooth runway for the next release and that the developers working on the feature can get there feature in on time.
Eric On Wed, Aug 24, 2016 at 7:47 PM, Tom McKay <[email protected]> wrote: > > > On Wed, Aug 24, 2016 at 5:58 PM, Justin Sherrill <[email protected]> > wrote: > >> On 08/24/2016 05:48 PM, Tom McKay wrote: >> >> >> >> On Wed, Aug 24, 2016 at 5:36 PM, Chris Duryee <[email protected]> wrote: >> >>> >>> >>> On 08/24/2016 05:33 PM, Tom McKay wrote: >>> > Katello and foreman are nearing dev freeze in early September but >>> there are >>> > a few features centered around Atomic Host and Atomic Registry that >>> will >>> > need changes introduced in pulp-2.10. While I understand pulp-2.10 is >>> > currently still in beta, I was hoping we could bring it into katello >>> now >>> > ahead of dev freeze so the dependent integration could be completed. >>> > >>> > If we did bring in pulp-2.10, it would have to be with the >>> understanding >>> > that breakages on both sides would need to be fixed prior to katello >>> > releasing. I know this is usually how things go anyways but I just >>> wanted >>> > to state it up front. >>> > >>> > Also, are there resources to do this work? If I understand things >>> > correctly, it's not just as simple as updating a repo file to point to >>> > pulp-2.10, but that changes to runcible would also need to be made? Is >>> this >>> > something that could be done ASAP? Sooner means more time to shake out >>> > issues. >>> >>> 2.10 should have additive-only changes from 2.9, I don't think runcible >>> would change unless it was to support something new in 2.10. >>> >> >> We would be passing username/password for docker registries w/ >> authentication. Not sure if there are other changes too, @partha? >> >> >> Generally when pulling in a new pulp release, we only initially introduce >> changes required to maintain existing functionality. New functionality is >> added after that is done in one or more PRs. >> >> > Of course, so yes @beav is correct. > > >> >> >>> > >>> > Thoughts? >>> > >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "foreman-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering Ph.D. Student - North Carolina State University -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
