[Starlingx-discuss] [Release] [Build] Preparation and discussion about StarlingX release 2.0

Tue Aug 6 14:26:01 UTC 2019

If I don't hear any objections by end of day (8 pm UTC), I'll assume 
that RC1 is the testing priority. I'll implement option a.  The build of 
V2.0 RC1 completes at midnight (4 am UTC), and the master build gets 
pushed back 4 hours from it's current slot.

Scott

On 2019-08-06 9:48 a.m., Scott Little wrote:
> Good point.
>
> I don't think we closed on that issue during the last release 
> meeting.  Or at least it wasn't captured in the minutes.  Was there an 
> action to talk it over with the testers?
>
> CENGN doesn't really have capacity to efficiently build both loads in 
> parallel.  They need to be serial.  I would assume the testing 
> priority will shift RC1, and we would want that load delivering at 
> midnight EST (4 am UTC), with the master build shifting to 4am EST (8 
> am UTC).  Call this option a.
>
> Option b is to leave master delivering at midnight EST (4 am UTC), and 
> RC1 delivers at 4 am.
>
> Thoughts?
>
> Scott
>
>
> On 2019-08-05 12:58 p.m., Cabrales, Ada wrote:
>> Nice to see this happening.
>>
>> One question: would the two ISOs (master, RC1) will be available at 
>> similar times? Or how is the build process to be scheduled?
>>
>> A.
>>
>>> -----Original Message-----
>>> From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com]
>>> Sent: Friday, August 2, 2019 1:56 PM
>>> To: starlingx-discuss at lists.starlingx.io
>>> Subject: Re: [Starlingx-discuss] [Release] [Build] Preparation and 
>>> discussion
>>> about StarlingX release 2.0
>>>
>>>  From the meeting just now, Scott & Dean agreed that they can base the
>>> branch off of a SHA, so there is no need for a freeze.
>>>
>>> They will finish some script changes for this (thanks guys) and, 
>>> assuming
>>> Monday's sanity is green, will start creating the branch on Tuesday.
>>>
>>> After the sanity on the RC1 branch is done, we'll announce that the 
>>> branch is
>>> ready to use.
>>>
>>> More details here and at [0] on the modified sequence...
>>>
>>> 1 Start (no freeze required since we're branching from a SHA, not 
>>> from Head)
>>>      - on Tuesday
>>>      - Dean will start at ~9:30 his time (CDT) (10:30 EDT)
>>>      - assuming sanity is Green
>>>      - Dean will branch from the SHA for that sanity's build 2. 
>>> Scott/Dean create
>>> RC1 branch and make required build changes.
>>>      - Dean will make sure he's able to do the SHA thing
>>>      - this will be based on Monday's sanity, which will be based on 
>>> the commits
>>> up to Sunday evening
>>>      - i.e. UTC 0130 am Monday
>>> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190805T01
>>> 30
>>> 3. Scott triggers RC1 build, both ISO and Docker images.
>>>      - Scott has a few script changes to do, will work to knock 
>>> those off today
>>>      - we agreed on these build paths
>>>      - Release path
>>>              .../starlingx/release/2.0.##/centos
>>>              .../starlingx/release/2.0/2.0.##/centos
>>>      - RC path
>>>              .../starlingx/rc/2.0/centos/timestamp
>>> 4. Ada's team runs sanity and confirm RC1 build passes sanity.
>>> 5. Release Team announces that the RC1 branch is now available.
>>>
>>> Note: Developers push changes to master and for Medium & High 
>>> priority LPs
>>> also cherry pick their commit to the RC1 branch.
>>>
>>> [0] https://etherpad.openstack.org/p/stx-releases
>>>
>>> -----Original Message-----
>>> From: Zvonar, Bill
>>> Sent: Friday, August 2, 2019 1:36 PM
>>> To: starlingx-discuss at lists.starlingx.io
>>> Subject: RE: [Starlingx-discuss] [Release] [Build] Preparation and 
>>> discussion
>>> about StarlingX release 2.0
>>>
>>> Proposed next steps (to be discussed in meeting today...
>>>
>>> 1. Release Team announces a freeze on master for TBD time (see Note) 2.
>>> Scott/Dean create RC1 branch and make required build changes.
>>> 3. Scott triggers RC1 build, both ISO and Docker images.
>>> 4. Ada's team runs sanity and confirm RC1 build passes sanity.
>>> 5. Release Team announces that the RC1 branch is now available.
>>>
>>> Note: Developers push changes to master and for High priority LPs 
>>> also cherry
>>> pick their commit to the RC1 branch.
>>>
>>> -----Original Message-----
>>> From: Dean Troyer <dtroyer at gmail.com>
>>> Sent: Friday, August 2, 2019 1:19 PM
>>> To: starlingx-discuss at lists.starlingx.io
>>> Subject: Re: [Starlingx-discuss] [Release] [Build] Preparation and 
>>> discussion
>>> about StarlingX release 2.0
>>>
>>> On Fri, Aug 2, 2019 at 8:58 AM Zvonar, Bill <Bill.Zvonar at windriver.com>
>>> wrote:
>>>> Scott - if you can provide a brief summary here of what you think 
>>>> the steps
>>> are beforehand, that'd be great.
>>>
>>> I ran a dry-run of the branching process this morning using the 
>>> following:
>>>
>>> Branch: r/stx.2.0
>>> Tag: v2.0.0.rc0
>>>
>>> Tagging the branch point makes it easier later to pull a list of 
>>> changes for the
>>> next RC or the release tag...
>>>
>>> I did find a couple of tweaks required in the branch-stx.sh script 
>>> to account
>>> for the OpenDev change and only branching the Gerrit repos:
>>> https://review.opendev.org/#/c/674342/
>>>
>>> The wiki pages [0] and [1] have been updated to match my current
>>> understanding (above) of the release naming and process.
>>>
>>> dt
>>>
>>> [0] https://wiki.openstack.org/wiki/StarlingX/Release_Plan
>>> [1] https://wiki.openstack.org/wiki/StarlingX/Release_Process
>>>
>>> -- 
>>> Dean Troyer
>>> dtroyer at gmail.com
>>>
>>> _______________________________________________
>>> Starlingx-discuss mailing list
>>> Starlingx-discuss at lists.starlingx.io
>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>>> _______________________________________________
>>> Starlingx-discuss mailing list
>>> Starlingx-discuss at lists.starlingx.io
>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>> _______________________________________________
>> Starlingx-discuss mailing list
>> Starlingx-discuss at lists.starlingx.io
>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>
>
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss