----- Original Message -----
 I'm ok with consolidating the etherpads, but then maybe we should
add
 some info to clearly identify what pipelines or CIs are impacted by
 each issue, for example issues with packstack or p-o-i impact on
 delorean-master-promotion but not in Tripleo CI.
  
+1 to this. Also, let's keep in mind that both etherpads are parsed by
http://dashboards.rdoproject.org/rdo-dev, so we'll need to adapt it as well.
Javier
 
 On Mon, Nov 7, 2016 at 2:59 PM, Wesley Hayutin <whayutin(a)redhat.com> wrote:
 > Greetings,
 >
 > I think it would make sense to use one etherpad to track the status of
 > openstack master.  There are several etherpads and it's confusing to use
 > and
 > get status.
 >
 > Is it reasonable to:
 >
 > move all work to [1], maybe we need to rename it.
 > move any items from [2] to [1]
 >
 > There was quite a bit of duplicate work going on in both etherpads over the
 > last week with memcache, and ping test issues.
 >
 > Thanks
 >
 > [1] 
https://etherpad.openstack.org/p/tripleo-ci-status
 > [2] 
https://etherpad.openstack.org/p/delorean_master_current_issues
 >
 > _______________________________________________
 > rdo-list mailing list
 > rdo-list(a)redhat.com
 > 
https://www.redhat.com/mailman/listinfo/rdo-list
 >
 > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
 
 _______________________________________________
 rdo-list mailing list
 rdo-list(a)redhat.com
 
https://www.redhat.com/mailman/listinfo/rdo-list
 
 To unsubscribe: rdo-list-unsubscribe(a)redhat.com