[Pulp-dev] 2.17.0 Dev Freeze - Tuesday, July 31

[Brian Bouterse]

On Mon, Aug 6, 2018 at 6:50 PM, Robin Chan <rchan at redhat.com> wrote:

> I am checking in on build status.
> Thanks, David for sending a note about newly discovered [4] and marking it
> as required. Let's continue to use [0] to check that we have all the PR in.
>
> Please check my understanding below on a few items.
> 1. The commit for [1] should be included in 2.17.0 even thought it missed
> 2.16.3 because we will use a fresh branch from master when starting the
> 2.17 build process. No new issues need be created, correct?
>
Correct because any .0 release is a fresh branch from 2-master so all
commits merged there like the extra one in [1] will be included.

2. I marked the following issues as part of 2.17.0 [0] as I thought they
> were missing from our list - please speak up if you disagree (or got any of
> this wrong):
>  - weak dependency [2] based on conversations during internal meeting
>  - one of the issues/regressions for which we delayed the build [3]
>
Those issues look right to include. In terms of bookkeeping, that change
puts them on the release/milestone which is great. The Platform Target
Release which is used by our automation during releases still needs to be
set. The milestone is good to plan for what work will be done even for work
that is still in ASSIGNED. The Platform Target Release should only be set
after the issue is MODIFIED. I've not made any changes. If I should or if
there are questions, lmk how I can help.

For the docker one specifically, that has different version numbers, should
it be on 2.17.0 or $next_docker_version? I'm not sure.

>
> Thanks,
> Robin
>
> [0] https://tinyurl.com/y96j92hl
> [1] https://pulp.plan.io/issues/3090
> [2] https://pulp.plan.io/issues/3847
> [3] https://pulp.plan.io/issues/3899
> [4] https://pulp.plan.io/issues/3904
>
>
> On Fri, Aug 3, 2018 at 5:30 AM, Ina Panova <ipanova at redhat.com> wrote:
>
>> 2.17.0 Release is delayed due to unforeseen discovered issues.
>>
>> For the new tentative dates please check the release schedule [0]
>>
>> Thank you.
>>
>> [0] https://pulp.plan.io/projects/pulp/wiki/2170_Release_Schedule
>>
>>
>>
>> --------
>> Regards,
>>
>> Ina Panova
>> Software Engineer| Pulp| Red Hat Inc.
>>
>> "Do not go where the path may lead,
>>  go instead where there is no path and leave a trail."
>>
>> On Wed, Aug 1, 2018 at 4:17 AM, Robin Chan <rchan at redhat.com> wrote:
>>
>>> All Pulp2 core or plugin code included in the 2.17.0 release should
>>> already be:
>>> a) merged to master
>>> b) associated with a story, refactor, task or a bugfix issue.
>>>
>>> Sorry for the late notice, our release contact is out sick unexpectedly
>>> and I failed to handle this as the backup.
>>>
>>> The list of features & bug fixes to be included in 2.17.0 can be found
>>> here[0]. The beta schedule[1] shows the 2.17.0 beta release date as
>>> Tuesday August 7th.
>>>
>>> [0] https://tinyurl.com/y96j92hl
>>> [1] https://pulp.plan.io/projects/pulp/wiki/2170_Release_Schedule
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180807/68c93b27/attachment.htm>