On 10/26/18 7:11 PM, Zane Bitter wrote:
> On 26/10/18 5:09 AM, Thomas Goirand wrote:
>> On 10/22/18 9:12 PM, Zane Bitter wrote:
>>> On 22/10/18 10:33 AM, Thomas Goirand wrote:
This can only happen if we have supporting distribution packages for
it.
IMO, this is a call for using
Zane Bitter writes:
> On 19/10/18 11:17 AM, Zane Bitter wrote:
>> I'd like to propose that we handle this by setting up a unit test
>> template in openstack-zuul-jobs for each release. So for Stein we'd have
>> openstack-python3-stein-jobs. This template would contain:
>>
>> * A voting gate
On 26/10/18 5:09 AM, Thomas Goirand wrote:
On 10/22/18 9:12 PM, Zane Bitter wrote:
On 22/10/18 10:33 AM, Thomas Goirand wrote:
This can only happen if we have supporting distribution packages for it.
IMO, this is a call for using Debian Testing or even Sid in the gate.
It depends on which
On 10/25/18 3:43 PM, Zane Bitter wrote:
On 25/10/18 1:38 PM, William M Edmonds wrote:
Zane Bitter wrote on 10/22/2018 03:12:46 PM:
> On 22/10/18 10:33 AM, Thomas Goirand wrote:
> > On 10/19/18 5:17 PM, Zane Bitter wrote:
> >> Integration Tests
> >> -
> >>
> >>
On 10/22/18 9:12 PM, Zane Bitter wrote:
> On 22/10/18 10:33 AM, Thomas Goirand wrote:
>> This can only happen if we have supporting distribution packages for it.
>> IMO, this is a call for using Debian Testing or even Sid in the gate.
>
> It depends on which versions we choose to support, but if
On 25/10/18 1:38 PM, William M Edmonds wrote:
Zane Bitter wrote on 10/22/2018 03:12:46 PM:
> On 22/10/18 10:33 AM, Thomas Goirand wrote:
> > On 10/19/18 5:17 PM, Zane Bitter wrote:
> >> Integration Tests
> >> -
> >>
> >> Integration tests do test, amongst other things,
Zane Bitter wrote on 10/22/2018 03:12:46 PM:
> On 22/10/18 10:33 AM, Thomas Goirand wrote:
> > On 10/19/18 5:17 PM, Zane Bitter wrote:
> >> Integration Tests
> >> -
> >>
> >> Integration tests do test, amongst other things, integration with
> >> non-openstack-supplied things
There seems to be agreement that this is broadly a good direction to
pursue, so I proposed a TC resolution. Let's shift discussion to the review:
https://review.openstack.org/613145
cheers,
Zane.
On 19/10/18 11:17 AM, Zane Bitter wrote:
There hasn't been a Python 2 release in 8 years, and
On Mon, Oct 22, 2018 at 04:33:49PM +0200, Thomas Goirand wrote:
> One of the reoccurring problem that I'm facing in Debian is that not
> only Python 3 version is lagging behind, but OpenStack dependencies are
> also lagging behind the distro. Often, the answer is "we don't support
> this or that
On 22/10/18 10:33 AM, Thomas Goirand wrote:
On 10/19/18 5:17 PM, Zane Bitter wrote:
We have traditionally held to the principle that we want each release to
support the latest release of CentOS and the latest LTS release of
Ubuntu, as they existed at the beginning of the release cycle.[2]
On Mon, Oct 22, 2018, at 7:33 AM, Thomas Goirand wrote:
> On 10/19/18 5:17 PM, Zane Bitter wrote:
snip
> > Integration Tests
> > -
> >
> > Integration tests do test, amongst other things, integration with
> > non-openstack-supplied things in the distro, so it's important that we
On 10/19/18 5:17 PM, Zane Bitter wrote:
> We have traditionally held to the principle that we want each release to
> support the latest release of CentOS and the latest LTS release of
> Ubuntu, as they existed at the beginning of the release cycle.[2]
> Currently this means in practice one version
On Fri, Oct 19, 2018 at 3:46 PM Zane Bitter wrote:
> On 19/10/18 12:30 PM, Clark Boylan wrote:
> > On Fri, Oct 19, 2018, at 8:17 AM, Zane Bitter wrote:
> >> Unit Tests
> >> --
> >>
> >> For unit tests, the most important thing is to test on the versions of
> >> Python we target. It's
On Fri, 19 Oct 2018, Zane Bitter wrote:
Just to make it easier to visualise, here is an example for how the Zuul
config _might_ look now if we had adopted this proposal during Rocky:
https://review.openstack.org/611947
And instead of having a project-wide goal in Stein to add
On 19/10/18 11:17 AM, Zane Bitter wrote:
I'd like to propose that we handle this by setting up a unit test
template in openstack-zuul-jobs for each release. So for Stein we'd have
openstack-python3-stein-jobs. This template would contain:
* A voting gate job for the highest minor version of
On 19/10/18 12:30 PM, Clark Boylan wrote:
On Fri, Oct 19, 2018, at 8:17 AM, Zane Bitter wrote:
Unit Tests
--
For unit tests, the most important thing is to test on the versions of
Python we target. It's less important to be using the exact distro that
we want to target, because unit
On 10/19/2018 01:58 PM, Andreas Jaeger wrote:
On 19/10/2018 18.30, Clark Boylan wrote:
> [...]
Because zuul config is branch specific we could set up every project
to use a `openstack-python3-jobs` template then define that template
differently on each branch. This would mean you only have to
On 19/10/2018 18.30, Clark Boylan wrote:
> [...]
Because zuul config is branch specific we could set up every project to use a
`openstack-python3-jobs` template then define that template differently on each
branch. This would mean you only have to update the location where the template
is
On Fri, Oct 19, 2018, at 8:17 AM, Zane Bitter wrote:
> There hasn't been a Python 2 release in 8 years, and during that time
> we've gotten used to the idea that that's the way things go. However,
> with the switch to Python 3 looming (we will drop support for Python 2
> in the U release[1]),
There hasn't been a Python 2 release in 8 years, and during that time
we've gotten used to the idea that that's the way things go. However,
with the switch to Python 3 looming (we will drop support for Python 2
in the U release[1]), history is no longer a good guide: Python 3
releases drop as
20 matches
Mail list logo
