Hey Team, We are getting very close to a Pulp 3 Core RC - so I'll ask you to take a look at any issues still not on the sprint that you believe would block a Pulp 3 Core RC.
The only gap I'm seeing is a few Katello P1 items that are not yet on our sprint [1]. Also, new tasks for 3.0 release [2]. And with other bandwidth, we should start planning/pre-planning for migrations, doc work and other next items post RC. Robin [1] https://tinyurl.com/ycqyl94z [2] https://tinyurl.com/pulp30new On Wed, Oct 17, 2018 at 3:55 PM David Davis <davidda...@redhat.com> wrote: > There are only two items left on the sprint and one probably requires a > member of the pulp_rpm team to work on it[0] while the other[1] probably > needs a bit of design work and/or discussion. I'll probably pick up the rpm > one tomorrow. If possible, we add should try to add some work to the > sprint. I'm happy to get stuff groomed if needed. > > [0] https://pulp.plan.io/issues/4062 > [1] https://pulp.plan.io/issues/4061 > > David > _______________________________________________ > 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
