On Tue, May 30, 2017 at 3:08 PM, Emilien Macchi <emil...@redhat.com> wrote: > On Tue, May 30, 2017 at 8:36 PM, Matthew Thode > <prometheanf...@gentoo.org> wrote: >> We have a problem in requirements that projects that don't have the >> cycle-with-intermediary release model (most of the cycle-with-milestones >> model) don't get integrated with requirements until the cycle is fully >> done. This causes a few problems. >> >> * These projects don't produce a consumable release for requirements >> until end of cycle (which does not accept beta releases). >> >> * The former causes old requirements to be kept in place, meaning caps, >> exclusions, etc. are being kept, which can cause conflicts. >> >> * Keeping the old version in requirements means that cross dependencies >> are not tested with updated versions. >> >> This has hit us with the mistral and tripleo projects particularly >> (tagged in the title). They disallow pbr-3.0.0 and in the case of >> mistral sqlalchemy updates. >> >> [mistral] >> mistral - blocking sqlalchemy - milestones >> >> [tripleo] >> os-refresh-config - blocking pbr - milestones >> os-apply-config - blocking pbr - milestones >> os-collect-config - blocking pbr - milestones > > These are cycle-with-milestones., like os-net-config for example, > which wasn't mentioned in this email. It has the same releases as > os-net-config also, so I'm confused why these 3 cause issue, I > probably missed something. > > Anyway, I'm happy to change os-*-config (from TripleO) to be > cycle-with-intermediary. Quick question though, which tag would you > like to see, regarding what we already did for pike-1? >
I ran into a case where I wanted to add python-tripleoclient to test-requirements for tripleo-heat-templates but it's not in the global requirements. In looking into adding this, I noticed that python-tripleoclient and tripleo-common are not cycle-with-intermediary either. Should/can we update these as well? tripleo-common is already in the global requirements but I guess since we've been releasing non-prerelease versions fairly regularly with the milestones it hasn't been a problem. Thanks, -Alex > Thanks, > >> [nova] >> os-vif - blocking pbr - intermediary >> >> [horizon] >> django-openstack-auth - blocking django - intermediary >> >> >> So, here's what needs doing. >> >> Those projects that are already using the cycle-with-intermediary model >> should just do a release. >> >> For those that are using cycle-with-milestones, you will need to change >> to the cycle-with-intermediary model, and do a full release, both can be >> done at the same time. >> >> If anyone has any questions or wants clarifications this thread is good, >> or I'm on irc as prometheanfire in the #openstack-requirements channel. >> >> -- >> Matthew Thode (prometheanfire) >> >> >> __________________________________________________________________________ >> 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 >> > > > > -- > Emilien Macchi > > __________________________________________________________________________ > 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 __________________________________________________________________________ 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