The initial RC will be distributed via PyPI only. The plan is to work on
RPM packaging (and maybe debian/Ubuntu?) between the RC and the GA. I think
your idea makes sense though once we ship OS-specific packaging.
David
On Thu, Sep 20, 2018 at 7:38 AM Bryan Kearney wrote:
> Do you plan to
Do you plan to distribute rpms/.debs?
If so, instead of using the term supported you can instead deal with it
via how you distribute:
* Only generate native artifacts for the distros you test
* Generate pip/egg files and then it is up to the user to deploy wherever.
-- bk
On 9/19/18 4:06 PM,
On Wed, Sep 19, 2018 at 3:55 PM Dana Walker wrote:
> I agree with Brian 100% that if we say something is officially supported,
> we need to back that statement up, be that with Travis or some other level
> of testing, or bugfix support, etc.
>
> Looking at the multi-os docs for Travis that Brian
Containers are a possible solution to add more OS's to the matrix.[0]
However, I think containers do not support SELinux. Then we will not be
able to test any feature/issue related to SELinux.
[0] https://docs.travis-ci.com/user/docker/
On Wed, Sep 19, 2018 at 3:55 PM, Dana Walker wrote:
> I
I agree with Brian 100% that if we say something is officially supported,
we need to back that statement up, be that with Travis or some other level
of testing, or bugfix support, etc.
Looking at the multi-os docs for Travis that Brian linked to, it looks like
it's only two options, Linux or OSX,
I want to advocate we follow the policy even for Fedora. We can anecdotally
say in the distribution docs that we use Fedora in our development
environment and that we expect it to work there too.
Without CI it's hard to know on an everyday basis which specific versions
of a distribution are
What about Fedora? We use it in our development environment so I think I
would feel comfortable claiming official support for it as well it’s not in
our CI environment.
Other than that, your proposal sounds good to me.
David
On Fri, Sep 14, 2018 at 12:02 PM Brian Bouterse wrote:
> Here is
Here is what makes sense to me. Let's have Pulp claim official support for
any distro that we have CI for (Travis). This ensures every pull request
change and nightlies are tested and provable on all supported distros. I
believe support is about provable testing so without CI we can't ensure it
in