Per the release schedule, the code for 2.15.3 is now frozen. There are a
total of 8 issues spread across core, rpm, and docker. This is ready for
release engineering. The current beta date for 2.15.3 is March 13th.

https://pulp.plan.io/issues?query_id=59

@milan, these two issues [0][1] are shown as stories so they are not
included in 2.15.3. They should be included in 2.16 though since they are
already merged. Will that work?

[0]: https://pulp.plan.io/issues/3353
[1]: https://pulp.plan.io/issues/3339

Thanks,
Brian


On Mon, Mar 5, 2018 at 11:18 AM, Brian Bouterse <bbout...@redhat.com> wrote:

> Any Pulp2 core or plugin code that you want included in the 2.15.3 release
> must be:
>
> a) merged to master by 22:00 UTC, March 6th
> b) be associated with a bugfix issue. stories, refactors, and tasks are
> not included in z-stream releases.
>
> If you want/need to adjust this date, please reply reply on-list.
>
> Thanks!
> Brian
>


On Mon, Mar 5, 2018 at 11:18 AM, Brian Bouterse <bbout...@redhat.com> wrote:

> Any Pulp2 core or plugin code that you want included in the 2.15.3 release
> must be:
>
> a) merged to master by 22:00 UTC, March 6th
> b) be associated with a bugfix issue. stories, refactors, and tasks are
> not included in z-stream releases.
>
> If you want/need to adjust this date, please reply reply on-list.
>
> Thanks!
> Brian
>
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Reply via email to