Re: [Pulp-dev] Migrating Sprint to Custom Field [happening tomorrow]

2018-03-08 Thread Robin Chan
#4 is done and here https://pulp.plan.io/projects/pulp/wiki/Sprint_Plans I'm going to revise my suggestion on sprint candidate. I think we can keep Sprint Candidate flag and set sprint = Sprint 34. And that will allow us to flag items for Sprint 35 (next sprint). Jeff - feel free to just make a

Re: [Pulp-dev] Migrating Sprint to Custom Field [happening tomorrow]

2018-03-08 Thread Brian Bouterse
I'm porting these today. I'll handle items 1-3. If we really don't like what it looks like we can revert. For item 4, I think we should make a wiki page with the sprint start/end dates per sprint. I'll reply with links to the newly created things so everyone can see it what we've got. On Wed,

Re: [Pulp-dev] Migrating Sprint to Custom Field [happening tomorrow]

2018-03-07 Thread Tatiana Tereshchenko
Thank you! My late but big +1. Tanya On Tue, Mar 6, 2018 at 11:04 PM, Brian Bouterse wrote: > Thanks for all the feedback! With many +1s and no -1s, I'm going to make > this change tomorrow. I'll send out links to the result when it is done. > > -Brian > > > On Mon, Mar 5,

Re: [Pulp-dev] Migrating Sprint to Custom Field [happening tomorrow]

2018-03-06 Thread Brian Bouterse
Thanks for all the feedback! With many +1s and no -1s, I'm going to make this change tomorrow. I'll send out links to the result when it is done. -Brian On Mon, Mar 5, 2018 at 12:43 PM, Jeff Ortel wrote: > +1 > > > On 03/02/2018 04:17 PM, Brian Bouterse wrote: > > Redmine's