Re: [Pulp-dev] Pulpcore RC5 Release Planning
I started working on an RC5 release but ran out of time today. I'll finish up and release tomorrow first thing. David On Tue, Sep 10, 2019 at 2:00 PM Austin Macdonald wrote: > There was a new feature, but it was missed because it wasn't in the > release notes: https://github.com/pulp/pulpcore-plugin/pull/125 > > The docker plugin is already using the new filter, so a new rc would be > helpful. > > On Tue, Sep 3, 2019 at 12:12 PM Ina Panova wrote: > >> Thank for clarification, then there is no need for an extra rc release. >> >> >> >> >> Regards, >> >> Ina Panova >> Senior Software Engineer| Pulp| Red Hat Inc. >> >> "Do not go where the path may lead, >> go instead where there is no path and leave a trail." >> >> >> On Tue, Sep 3, 2019 at 5:08 PM David Davis wrote: >> >>> The only core change in 4681 is that it raises an exception when there >>> is no default_related_name defined on a Detail model. So no plugin release >>> should be blocked by 4681. >>> >>> David >>> >>> >>> On Tue, Sep 3, 2019 at 11:00 AM Ina Panova wrote: >>> Brian, how about releasing RC5 earlier, for example Thursday Sep 5, and putting the blocker list to RC6? With the recent changes happened in core [0], plugins cannot release unless there is already a released core version that contains this change. For example, docker plugin would like to cut another beta but it is waiting on [0] being included and released in core. Thoughts? [0] https://pulp.plan.io/issues/4681 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, Sep 2, 2019 at 6:22 PM Brian Bouterse wrote: > tl;dr -- Let's release pulpcore and pulpcore-plugin on Tuesday Sept > 10th. Please identify any backwards incompatible changes or high-risk > changes as blockers here [2]. > > > It's been ~ 5 weeks since pulpcore and pulpcore-plugin have released. > There are several changes ready for each [0][1] . I propose we release > both > on Sept 10th. > > # Blockers > I made the blockers list here [2], and I put > https://pulp.plan.io/issues/5008 on it. It's possible this may be the > last RC (I'm not sure) so any significant change in pulpcore that we know > about should be a blocker. Please identify those by putting them onto the > etherpad. > > # Upgrade form RC4 -> RC5 > There was no migration editing or squashing in pulpcore so I believe > users should be able to upgrade from RC4 to RC5. > > # Plugin compatibility releases > As this time I see no breaking changes in the changelogs [0][1] so as > of now, it should not require plugins to produce compatibility releases. > > Concerns, questions, or any kind of feedback is welcome either on-list > or off. > > [0]: https://github.com/pulp/pulpcore/tree/master/CHANGES > [1]: https://github.com/pulp/pulpcore-plugin/tree/master/CHANGES > [2]: https://etherpad.net/p/pulpcore_rc5_blocker_list > > ___ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev > ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev >>> ___ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev >> > ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
Re: [Pulp-dev] Pulpcore RC5 Release Planning
There was a new feature, but it was missed because it wasn't in the release notes: https://github.com/pulp/pulpcore-plugin/pull/125 The docker plugin is already using the new filter, so a new rc would be helpful. On Tue, Sep 3, 2019 at 12:12 PM Ina Panova wrote: > Thank for clarification, then there is no need for an extra rc release. > > > > > Regards, > > Ina Panova > Senior Software Engineer| Pulp| Red Hat Inc. > > "Do not go where the path may lead, > go instead where there is no path and leave a trail." > > > On Tue, Sep 3, 2019 at 5:08 PM David Davis wrote: > >> The only core change in 4681 is that it raises an exception when there is >> no default_related_name defined on a Detail model. So no plugin release >> should be blocked by 4681. >> >> David >> >> >> On Tue, Sep 3, 2019 at 11:00 AM Ina Panova wrote: >> >>> Brian, >>> >>> how about releasing RC5 earlier, for example Thursday Sep 5, and putting >>> the blocker list to RC6? >>> With the recent changes happened in core [0], plugins cannot release >>> unless there is already a released core version that contains this change. >>> For example, docker plugin would like to cut another beta but it is >>> waiting on [0] being included and released in core. >>> >>> Thoughts? >>> >>> [0] https://pulp.plan.io/issues/4681 >>> >>> Regards, >>> >>> Ina Panova >>> Senior Software Engineer| Pulp| Red Hat Inc. >>> >>> "Do not go where the path may lead, >>> go instead where there is no path and leave a trail." >>> >>> >>> On Mon, Sep 2, 2019 at 6:22 PM Brian Bouterse >>> wrote: >>> tl;dr -- Let's release pulpcore and pulpcore-plugin on Tuesday Sept 10th. Please identify any backwards incompatible changes or high-risk changes as blockers here [2]. It's been ~ 5 weeks since pulpcore and pulpcore-plugin have released. There are several changes ready for each [0][1] . I propose we release both on Sept 10th. # Blockers I made the blockers list here [2], and I put https://pulp.plan.io/issues/5008 on it. It's possible this may be the last RC (I'm not sure) so any significant change in pulpcore that we know about should be a blocker. Please identify those by putting them onto the etherpad. # Upgrade form RC4 -> RC5 There was no migration editing or squashing in pulpcore so I believe users should be able to upgrade from RC4 to RC5. # Plugin compatibility releases As this time I see no breaking changes in the changelogs [0][1] so as of now, it should not require plugins to produce compatibility releases. Concerns, questions, or any kind of feedback is welcome either on-list or off. [0]: https://github.com/pulp/pulpcore/tree/master/CHANGES [1]: https://github.com/pulp/pulpcore-plugin/tree/master/CHANGES [2]: https://etherpad.net/p/pulpcore_rc5_blocker_list ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev >>> ___ >>> Pulp-dev mailing list >>> Pulp-dev@redhat.com >>> https://www.redhat.com/mailman/listinfo/pulp-dev >>> >> ___ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev > ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
Re: [Pulp-dev] Pulpcore RC5 Release Planning
Thank for clarification, then there is no need for an extra rc release. Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Tue, Sep 3, 2019 at 5:08 PM David Davis wrote: > The only core change in 4681 is that it raises an exception when there is > no default_related_name defined on a Detail model. So no plugin release > should be blocked by 4681. > > David > > > On Tue, Sep 3, 2019 at 11:00 AM Ina Panova wrote: > >> Brian, >> >> how about releasing RC5 earlier, for example Thursday Sep 5, and putting >> the blocker list to RC6? >> With the recent changes happened in core [0], plugins cannot release >> unless there is already a released core version that contains this change. >> For example, docker plugin would like to cut another beta but it is >> waiting on [0] being included and released in core. >> >> Thoughts? >> >> [0] https://pulp.plan.io/issues/4681 >> >> Regards, >> >> Ina Panova >> Senior Software Engineer| Pulp| Red Hat Inc. >> >> "Do not go where the path may lead, >> go instead where there is no path and leave a trail." >> >> >> On Mon, Sep 2, 2019 at 6:22 PM Brian Bouterse >> wrote: >> >>> tl;dr -- Let's release pulpcore and pulpcore-plugin on Tuesday Sept >>> 10th. Please identify any backwards incompatible changes or high-risk >>> changes as blockers here [2]. >>> >>> >>> It's been ~ 5 weeks since pulpcore and pulpcore-plugin have released. >>> There are several changes ready for each [0][1] . I propose we release both >>> on Sept 10th. >>> >>> # Blockers >>> I made the blockers list here [2], and I put >>> https://pulp.plan.io/issues/5008 on it. It's possible this may be the >>> last RC (I'm not sure) so any significant change in pulpcore that we know >>> about should be a blocker. Please identify those by putting them onto the >>> etherpad. >>> >>> # Upgrade form RC4 -> RC5 >>> There was no migration editing or squashing in pulpcore so I believe >>> users should be able to upgrade from RC4 to RC5. >>> >>> # Plugin compatibility releases >>> As this time I see no breaking changes in the changelogs [0][1] so as of >>> now, it should not require plugins to produce compatibility releases. >>> >>> Concerns, questions, or any kind of feedback is welcome either on-list >>> or off. >>> >>> [0]: https://github.com/pulp/pulpcore/tree/master/CHANGES >>> [1]: https://github.com/pulp/pulpcore-plugin/tree/master/CHANGES >>> [2]: https://etherpad.net/p/pulpcore_rc5_blocker_list >>> >>> ___ >>> Pulp-dev mailing list >>> Pulp-dev@redhat.com >>> https://www.redhat.com/mailman/listinfo/pulp-dev >>> >> ___ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev >> > ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
Re: [Pulp-dev] Pulpcore RC5 Release Planning
The only core change in 4681 is that it raises an exception when there is no default_related_name defined on a Detail model. So no plugin release should be blocked by 4681. David On Tue, Sep 3, 2019 at 11:00 AM Ina Panova wrote: > Brian, > > how about releasing RC5 earlier, for example Thursday Sep 5, and putting > the blocker list to RC6? > With the recent changes happened in core [0], plugins cannot release > unless there is already a released core version that contains this change. > For example, docker plugin would like to cut another beta but it is > waiting on [0] being included and released in core. > > Thoughts? > > [0] https://pulp.plan.io/issues/4681 > > Regards, > > Ina Panova > Senior Software Engineer| Pulp| Red Hat Inc. > > "Do not go where the path may lead, > go instead where there is no path and leave a trail." > > > On Mon, Sep 2, 2019 at 6:22 PM Brian Bouterse wrote: > >> tl;dr -- Let's release pulpcore and pulpcore-plugin on Tuesday Sept >> 10th. Please identify any backwards incompatible changes or high-risk >> changes as blockers here [2]. >> >> >> It's been ~ 5 weeks since pulpcore and pulpcore-plugin have released. >> There are several changes ready for each [0][1] . I propose we release both >> on Sept 10th. >> >> # Blockers >> I made the blockers list here [2], and I put >> https://pulp.plan.io/issues/5008 on it. It's possible this may be the >> last RC (I'm not sure) so any significant change in pulpcore that we know >> about should be a blocker. Please identify those by putting them onto the >> etherpad. >> >> # Upgrade form RC4 -> RC5 >> There was no migration editing or squashing in pulpcore so I believe >> users should be able to upgrade from RC4 to RC5. >> >> # Plugin compatibility releases >> As this time I see no breaking changes in the changelogs [0][1] so as of >> now, it should not require plugins to produce compatibility releases. >> >> Concerns, questions, or any kind of feedback is welcome either on-list or >> off. >> >> [0]: https://github.com/pulp/pulpcore/tree/master/CHANGES >> [1]: https://github.com/pulp/pulpcore-plugin/tree/master/CHANGES >> [2]: https://etherpad.net/p/pulpcore_rc5_blocker_list >> >> ___ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev >> > ___ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev > ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
Re: [Pulp-dev] Pulpcore RC5 Release Planning
Brian, how about releasing RC5 earlier, for example Thursday Sep 5, and putting the blocker list to RC6? With the recent changes happened in core [0], plugins cannot release unless there is already a released core version that contains this change. For example, docker plugin would like to cut another beta but it is waiting on [0] being included and released in core. Thoughts? [0] https://pulp.plan.io/issues/4681 Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, Sep 2, 2019 at 6:22 PM Brian Bouterse wrote: > tl;dr -- Let's release pulpcore and pulpcore-plugin on Tuesday Sept > 10th. Please identify any backwards incompatible changes or high-risk > changes as blockers here [2]. > > > It's been ~ 5 weeks since pulpcore and pulpcore-plugin have released. > There are several changes ready for each [0][1] . I propose we release both > on Sept 10th. > > # Blockers > I made the blockers list here [2], and I put > https://pulp.plan.io/issues/5008 on it. It's possible this may be the > last RC (I'm not sure) so any significant change in pulpcore that we know > about should be a blocker. Please identify those by putting them onto the > etherpad. > > # Upgrade form RC4 -> RC5 > There was no migration editing or squashing in pulpcore so I believe users > should be able to upgrade from RC4 to RC5. > > # Plugin compatibility releases > As this time I see no breaking changes in the changelogs [0][1] so as of > now, it should not require plugins to produce compatibility releases. > > Concerns, questions, or any kind of feedback is welcome either on-list or > off. > > [0]: https://github.com/pulp/pulpcore/tree/master/CHANGES > [1]: https://github.com/pulp/pulpcore-plugin/tree/master/CHANGES > [2]: https://etherpad.net/p/pulpcore_rc5_blocker_list > > ___ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev > ___ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
