On Tue, Feb 23, 2016 at 05:32:44PM -0500, James Slagle wrote:
> On Tue, Feb 23, 2016 at 5:18 PM, Devananda van der Veen
> wrote:
> > Responding to your points out of order, since that makes more sense to me
> > right now ...
> >
> >> Since currently DIB claims to be backwards compatible, we just n
On Tue, Feb 23, 2016 at 5:18 PM, Devananda van der Veen
wrote:
> Responding to your points out of order, since that makes more sense to me
> right now ...
>
>> Since currently DIB claims to be backwards compatible, we just need to
>> leave master backwards compatible with Kilo and Liberty Ironic,
Responding to your points out of order, since that makes more sense to me
right now ...
Since currently DIB claims to be backwards compatible, we just need to
> leave master backwards compatible with Kilo and Liberty Ironic, which
> means not deleting the bash ramdisk element. If Ironic wants to r
On Wed, Feb 17, 2016 at 6:27 AM, Dmitry Tantsur wrote:
> Hi everyone!
>
> Yesterday on the Ironic midcycle we agreed that we would like to remove
> support for the old bash ramdisk from our code and gate. This, however, pose
> a problem, since we still support Kilo and Liberty. Meaning:
Hi, I jus
On 02/17/2016 08:30 AM, Dmitry Tantsur wrote:
> On 02/17/2016 02:22 PM, John Trowbridge wrote:
>>
>>
>> On 02/17/2016 06:27 AM, Dmitry Tantsur wrote:
>>> Hi everyone!
>>>
>>> Yesterday on the Ironic midcycle we agreed that we would like to remove
>>> support for the old bash ramdisk from our code
On 02/17/2016 02:22 PM, John Trowbridge wrote:
On 02/17/2016 06:27 AM, Dmitry Tantsur wrote:
Hi everyone!
Yesterday on the Ironic midcycle we agreed that we would like to remove
support for the old bash ramdisk from our code and gate. This, however,
pose a problem, since we still support Kilo
On 02/17/2016 06:27 AM, Dmitry Tantsur wrote:
> Hi everyone!
>
> Yesterday on the Ironic midcycle we agreed that we would like to remove
> support for the old bash ramdisk from our code and gate. This, however,
> pose a problem, since we still support Kilo and Liberty. Meaning:
>
> 1. We can't
My preference is option 4, however with a slight difference, and that is
that we only apply the DIB cap to the job that¹s testing the bash ramdisk.
We can say that the bash ramdisk is deprecated in liberty and will not be
receiving any further updates, so we¹re capping the DIB version, but
because
Hi everyone!
Yesterday on the Ironic midcycle we agreed that we would like to remove
support for the old bash ramdisk from our code and gate. This, however,
pose a problem, since we still support Kilo and Liberty. Meaning:
1. We can't remove gate jobs completely, as they still run on Kilo/Lib
