This is another view of that milestone data for 2.17.0: https://tinyurl.com/y96j92hl
On Mon, Jul 9, 2018 at 11:29 AM, Robin Chan <rc...@redhat.com> wrote: > Austin has agreed to be 2.17.0 build prime and handle responsibilities to > ensure a smooth build process. > > Given the desire to ensure we deliver all requested 2.17.0 content in a > timely manner, I'd like for us to use the milestone function of Redmine: > https://pulp.plan.io/versions/63 > > I'll work with team members, but will aim to ensure all planned work to be > added to this milestone be end of day. > > I believe this will be valuable to accomplish the following: > 1. Provide transparency around our planned content in 2.17.0 build > a. Allow QE team to review planned deliveries with respect to content > and verification required field values > b. Enable build prime to build whenever committed content is complete. > 2. Provide visibility with current progress toward our planned dev freeze > date. Redmine milestones provide: > a. Date burn down of how many days left > b. Report of redmine issues completed > 3. Will not take place of build team building from master - if other fixes > go in, they will be included. > > We will try this for 2.17.0 build. I understand that since we have Pulp > 3.0 and 3.1 milestones, this process will not work for 3.x.z builds, > however this proposal should help ease the burden of our current needs. > Please provide any feedback and especially if tomorrow you are surprised by > anything that is or isn't in the release. > > Thanks, > Robin Chan > > > On Thu, Jun 21, 2018 at 11:57 AM, Ina Panova <ipan...@redhat.com> wrote: > >> A 2.17.0 is being planned with some features and recent fixes. >> >> Here [0] is a release schedule page which outlines some tentative dates, >> starting with a dev freeze on July 30 2018. >> >> If this schedule needs to be adjusted, please reply with alternate dates. >> >> [0] https://pulp.plan.io/projects/pulp/wiki/2170_Release_Schedule >> >> >> -------- >> Regards, >> >> Ina Panova >> 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." >> >> _______________________________________________ >> 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