To call it out, the concerns are:
- A 2.18.2 build Z-release would be 3 weeks & if needed would be a higher
urgent need & done first
- We've never done them at the same time, so that would push the
2.19.0 build back 3 weeks, which would blow a katello date out of the water
- QE & build team staff & resources (virtual hw) for the standard build
schedule done serially or in parallel
- Some infrastructure migrations are in progress and need to be completed
before any builds can start.
So to state it plainly, if a 2.18.2 is needed, I think we will need to find
a way to not do the normal process/schedule.
Normally, we don't look at doing a .z stream and a .y release so close
together, because users can take the .y or cherry pick fixes back if
needed. However in this case, #4518 [1] does not exist in a 2.19.0 so we
can't cherry pick a fix from that back to a 2.18.1 build for internal
stakeholders.
Robin
On Fri, Mar 8, 2019 at 2:58 PM Matt Pusateri <mpusa...@redhat.com> wrote:
> Robin,
>
> So I make sure I understand the concern. If pulp 2.19 doesn't GA until
> 4/2/19, the concern is that it hasn't baked in long enough for Dev to pull
> it into Katello on 4/8/19?
>
> Matt P.
>
> On Fri, Mar 8, 2019 at 2:19 PM Robin Chan <rc...@redhat.com> wrote:
>
>> This is an early heads up on potential Pulp 2 build needs. I don't want
>> to alarm anyone - however I do want to bring to attention that we have some
>> issues to investigate and we may need to be creative to meet everyone's
>> needs for fixes as investigation gives us more information.
>>
>> Pulp 2.18.2 - #4518 [1]
>> We may need to provide a fix for an internal stakeholders not able to
>> take a 2.19.0 y-release at this time. For Pulp upstream users, the master
>> branch and a 2.19.0 is working as expected.
>>
>> Pulp 2.19 - driver #3740 [2]
>> Delivery 1 new feature for upstream Katello.
>> Katello has dev freeze ~April 8
>> As a starting point, I have put together a schedule that goes with
>> our usual Tuesday dates.
>>
>> - Dev Freeze date - March 12
>> - Beta Release - March 19
>> - RC date - March 26
>> - GA date - April 2
>>
>> There may be a need to take some discussion to an internal list to
>> discuss some dates or staffing concerns, but I wanted to share some
>> thoughts here and let everyone know we will be updating as we know more.
>>
>> ~Robin
>>
>> [1] https://pulp.plan.io/issues/4518
>> [2] https://pulp.plan.io/issues/3740
>> _______________________________________________
>> 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
