Starting with stable/liberty, each project now owns when to do point
releases for their stable branches (rather than a large coordinated
stable branch point release that the stable-maint-core team does).
There are a couple of core projects which have not done a stable/liberty
point release sin
> On 27 Jan 2016, at 19:14, Matt Riedemann wrote:
>
> Starting with stable/liberty, each project now owns when to do point releases
> for their stable branches (rather than a large coordinated stable branch
> point release that the stable-maint-core team does).
>
> There are a couple of core
On 1/28/2016 9:35 AM, Renat Akhmerov wrote:
On 27 Jan 2016, at 19:14, Matt Riedemann wrote:
Starting with stable/liberty, each project now owns when to do point releases
for their stable branches (rather than a large coordinated stable branch point
release that the stable-maint-core team
> On 28 Jan 2016, at 17:40, Matt Riedemann wrote:
>
> With regards to the trove 'plugin' stuff, it adds a new dependency on
> python-troveclient which was not in sahara 1.0.0 in liberty GA, so IMO it's
> not valid to release that in 1.0.1 and expect people to have to start
> packaging and pic
On 1/29/2016 12:08 AM, Renat Akhmerov wrote:
On 28 Jan 2016, at 17:40, Matt Riedemann wrote:
With regards to the trove 'plugin' stuff, it adds a new dependency on
python-troveclient which was not in sahara 1.0.0 in liberty GA, so IMO it's not
valid to release that in 1.0.1 and expect peop