Repository integrity (Re: OpenBMC v1.0.5 released.)

[Joel Stanley]

Hey Patrick,

On Wed, Aug 24, 2016 at 6:33 AM, Patrick Williams <patrick at stwcx.xyz> wrote:
> Due to a major regression, I re-tagged v1.0.5 with the kernel updates
> removed.  The change log is therefore just:

I don't think we should ever overwrite a tag that has hit the public
repository. There's no harm in doing a quick second tag.

This is particularity important in the context of Brad's account
becoming compromised recently.

Can tags be pushed to Gerrit and reviewed through it's interface?

Would Github's protected branches feature have stopped you from being
able to make this change?

 https://help.github.com/articles/about-protected-branches/

Cheers,

Joel

>      * Cache all inventory properties and preserve inventory during BMC
>        firmware update (openbmc/openbmc#487)
>      * Update the power button behavior on Barreleye to:
>          * Short press: Only power on. Remove the power off action.
>          * Long press (>3 seconds): Hard power off.
>
> On Mon, Aug 22, 2016 at 12:57:34PM -0500, Patrick Williams wrote:
>> Another fix release for the v1.0.x stable tree was tagged today.
>>
>> https://github.com/openbmc/openbmc/releases/tag/v1.0.5
>>
>> Changes since v1.0.4:
>>     * Cache all inventory properties and preserve inventory during BMC
>>       firmware update (openbmc/openbmc#487)
>>     * Update the power button behavior on Barreleye to:
>>         * Short press: Only power on. Remove the power off action.
>>         * Long press (>3 seconds): Hard power off.
>>     * Kernel version update:
>>         * Stable release 4.4.18
>>         * Ensure the LEDs stay at the same state on boot (openbmc/linux#98)
> --
> Patrick Williams
>
> _______________________________________________
> openbmc mailing list
> openbmc at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc
>