OK, an update on this. The current plan of record after the team meeting
today goes something like this:
1) Identify tests that are moving to the new plugin repo, and remove
them from the heat repo.
2) Start using the utils (base classes ) from the plugin repo in the
remaining heat tests.
3)
>
> Does anybody remember what the mechanism for dealing with this that was
agreed at the PTG was?
The etherpad [1] shows actions that we(me and Thomas) agree to do, and
that's all for PTG discussion (the online attendee number is 0 for that
session).
Following with a recap in meeting to share
On Wed, Nov 29, 2017 at 9:51 PM, Zane Bitter wrote:
> On 19/11/17 03:08, Rabi Mishra wrote:
>
>> Hi All,
>>
>> As part of community goal[1] for Queens, we've completed the repo split
>> and created the new project[2].
>>
>> The next objective to is to use the new plugin in
On 19/11/17 03:08, Rabi Mishra wrote:
Hi All,
As part of community goal[1] for Queens, we've completed the repo split
and created the new project[2].
The next objective to is to use the new plugin in our jobs. As we've
merged some changes after the split, I've synced them and fixed some