2015-06-01 17:32 GMT+02:00 Alan Pevec <ape...@gmail.com>:
>> *Plan C* would be to just let projects tag stable point releases from
>> time to time. That would solve all the original stated problems. And
>> that would solve objections 2 and 3, which I think are the most valid ones.
>
> and *Plan D* would be to start doing automatic per-project
> micro-versions on each commit: e.g. 2015.1.N where N is increased on
> each commit. There's just TBD item how to provide source tarballs for
> this.

+1 for micro-versions rather than raw git checksums.

> This would solve 3. reference points for OSSAs and relnotes.
> Solution for 2. could be to add doc/source/release-notes.rst for each
> project wishing to maintain it, docs are already published for each
> branch e.g. http://docs.openstack.org/developer/keystone/kilo/
>
> Cheers,
> Alan
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to