Mihai, I believe your changes made it into 2.16.0. On Tue, Mar 13, 2018 at 9:54 PM, Mihai Ibanescu <mihai.ibane...@gmail.com> wrote:
> Does that mean that https://github.com/pulp/pulp_rpm/pull/1093 did not > make the cut? > > I think it would be a shame for that to be pushed to 2.17. But I'm biased > since it's my code :-) > > On Tue, Mar 13, 2018 at 6:33 PM, Tatiana Tereshchenko <ttere...@redhat.com > > wrote: > >> The code for 2.16.0 is now frozen. There are a total of 9 >> stories/tasks/refactors prepared for the release: >> >> https://pulp.plan.io/issues?query_id=61 >> >> Tanya >> >> On Tue, Mar 13, 2018 at 11:05 AM, Tatiana Tereshchenko < >> ttere...@redhat.com> wrote: >> >>> Any Pulp2 core or plugin code that you want included in the 2.16.0 >>> release must be: >>> >>> a) merged to master by 22:00 UTC, March 13th >>> b) associated with a story, refactor, task or a bugfix issue. >>> >>> If you want/need to adjust this date, please reply on list. >>> >>> Thanks, >>> Tanya >>> >>> >> >> On Tue, Mar 13, 2018 at 11:05 AM, Tatiana Tereshchenko < >> ttere...@redhat.com> wrote: >> >>> Any Pulp2 core or plugin code that you want included in the 2.16.0 >>> release must be: >>> >>> a) merged to master by 22:00 UTC, March 13th >>> b) associated with a story, refactor, task or a bugfix issue. >>> >>> If you want/need to adjust this date, please reply on list. >>> >>> Thanks, >>> Tanya >>> >>> >> >> _______________________________________________ >> 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