Openbmc test Release tagging for Community Release

Openbmc test Release tagging for Community Release

[George Keishing]

[-- Attachment #1: Type: text/plain, Size: 571 bytes --]

Hi All,

We are going to tag a openbmc test release soon for the community master 
release testing. So, expect 2.3 tag version soon there in a week time from 
now, once the test code and master are stable.

As part of the release tagging in test, we are freezing any new changes 
for now in test except for CI/CT fixes required to support testing the 
Master 2.6 . 

Recent  release 2.2 stable. 
https://github.com/openbmc/openbmc-test-automation/releases 

Thanks and Regards,
   George Keishing
   IBM Systems &Technology Lab, Firmware Development,



[-- Attachment #2: Type: text/html, Size: 1285 bytes --]

Re: Openbmc test Release tagging for Community Release

[krtaylor]

On 1/17/19 10:38 AM, George Keishing wrote:
> Hi All,
> 
> We are going to tag a openbmc test release soon for the community master 
> release testing. So, expect 2.3 tag version soon there in a week time 
> from now, once the test code and master are stable.

No, we are in the middle of a test cycle for the 2.6 release. We agreed 
and switched from the informal tags to a formal release process last 
June/July. Why do we need to tag master at an earlier level? Please come 
to a release planning meeting and let's talk about what you need.

> As part of the release tagging in test, we are freezing any new changes 
> for now in test except for CI/CT fixes required to support testing the 
> Master 2.6 .

I don't understand this at all. What is "release tagging in test"? We 
have a 2.6 branch and master (which is also at 2.6+ level).

Kurt (krtaylor)