Open Stack

I totally forgot xstatic deliverables adopts the "independent" release
mode when I sent the mail.
I know the policy is only applied to cycle-based deliverables, but I
totally forgot it......
xstatic deliverables I am talking about fit into "independent deliverables".

On Wed, Mar 4, 2020 at 10:42 PM Radomir Dopieralski <rdopiera at redhat.com> wrote:
>
> I think it makes a lot of sense to make them independent, especially since the releases often contain security fixes, so that they should be included in any older supported releases of Horizon as well.
>
> On Tue, Mar 3, 2020 at 3:02 PM Sean McGinnis <sean.mcginnis at gmx.com> wrote:
>>
>> On 3/3/20 4:11 AM, Akihiro Motoki wrote:
>> > Thanks Thierry for the detail explanation.
>> > The horizon team will update the corresponding repos for new minor
>> > releases and follow the usual release process.
>> > One question: we have passed the milestone-2. Is it better to wait
>> > till Victoria dev cycle is open?
>> >
>> > Thanks,
>> > Akihiro
>>
>> We are past the deadline for inclusion in ussuri. But that said, these
>> are things that are currently being used by the team, so I think it's a
>> little misleading in its current state. I think we should get these new
>> releases done in this cycle if possible.
>>
>> Part of this is also the assumption that these will be cycle based. I
>> wonder if this are more appropriate as independent deliverables? That
>> means they are not tied to a specific release cycle and can be released
>> whenever there is something to be released. At least something to think
>> about.
>>
>> https://releases.openstack.org/reference/release_models.html#cycle-with-intermediary
>>
>> > On Fri, Feb 28, 2020 at 1:47 AM Thierry Carrez <thierry at openstack.org> wrote:
>> >> Thierry Carrez wrote:
>> >>> The way we've been handling this in the past was to ignore past releases
>> >>> (since they are not signed by the release team), and push a new one
>> >>> through the releases repository. It should replace the unofficial one in
>> >>> PyPI and make sure all is in order.
>> >> Clarification with a practical example:
>> >>
>> >> xstatic-hogan 2.0.0.2 is on PyPI, but has no tag in the
>> >> openstack/xstatic-hogan repo, and no deliverable file in openstack/releases.
>> >>
>> >> Solution is to resync everything by proposing a 2.0.0.3 release that
>> >> will have tag, be in openstack/releases and have a matching upload on PyPI.
>> >>
>> >> This is done by:
>> >>
>> >> - bumping BUILD at
>> >> https://opendev.org/openstack/xstatic-hogan/src/branch/master/xstatic/pkg/hogan/__init__.py#
>> >>
>> >> - adding a deliverables/_independent/xstatic-hogan.yaml file in
>> >> openstack/releases defining a tag for 2.0.0.3
>> >>
>> >> - removing the "deprecated" line from
>> >> https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml#L542
>> >>
>> >> Repeat for every affected package :)
>> >>
>> >> --
>> >> Thierry Carrez (ttx)
>> >>
>>
>
>
> --
> Radomir Dopieralski