Re: [foreman-dev] Release process & permissions

2017-09-28 Thread Eric D Helms
Related to Dmitri's point, and I've thrown this question out with Katello releases at least every other release, do all the components that are currently released "together" need to be so these days? That is to say, can any of the "versioned together components" be released more independently but

Re: [foreman-dev] Building an Infra/Deployment/Platform Roadmap

2017-09-28 Thread Eric D Helms
This has been out for about a week with some comments and discussion so far on the etherpad. I want to give a round of mention and discussion via -dev list as well since sometimes etherpad is not obvious for updates. I have copied the etherpad here. I will leave this thread open for around a week,

Re: [foreman-dev] Release process & permissions

2017-09-28 Thread Dmitri Dolguikh
Why not distribute the release process? Each component can have (probably already does) multiple maintainers who are capable of doing most of the leg-work. The role of the release nanny then becomes coordinating the effort, making public announcements and such. Such an approach would help avoid

Re: [foreman-dev] Requesting discovery test for core PRs

2017-09-28 Thread Evgeni Golov
On Wed, Sep 27, 2017 at 7:26 PM, Timo Goebel wrote: > ... have you considered using some kind of a CDN for downloads, e.g. > cloudflare, if traffic is a concern? fastly.com is usually happy to sponsor bandwidth for FOSS projects, if you ask nicely (they sponsor one half of

Re: [foreman-dev] Release process & permissions

2017-09-28 Thread Ewoud Kohl van Wijngaarden
To release a gem to rubygems I'd recommend looking at how voxpupuli implemented this using Travis[1]. The same can be done for puppet[2]. That means you can push a tag to git and the release is there. There are also tools that help you bump. For puppet there is puppet-blacksmith[3]. How to do

Re: [foreman-dev] Release process & permissions

2017-09-28 Thread Ewoud Kohl van Wijngaarden
While I agree we should automate a lot, I agree with Eric. Doing a Foreman release should involve a human to keep the end-to-end quality. Just giving permissions is wrong. For example in Foreman 1.15.5 the installer was tagged and released before I could push in my changes. That communication

Re: [foreman-dev] SmartOS (Solaris 11), Joyent cloud

2017-09-28 Thread Greg Sutcliffe
On Wed, 2017-09-27 at 12:24 -0700, Dmitriy Morozovsky wrote: > Hello dear team. > I see you support Solaris 8,10 what about Solaris 11 or SmartOS > Our big infrastructure based on Joyent Cloud and we looking for > support of Foreman on Solaris 11 As with much of the OS support in Foreman, the

Re: [foreman-dev] Requesting discovery test for core PRs

2017-09-28 Thread Greg Sutcliffe
On Wed, 2017-09-27 at 19:26 +0200, Timo Goebel wrote: > ... have you considered using some kind of a CDN for downloads, e.g. > cloudflare, if traffic is a concern? > > > I'll see what I can do. The Rackspace billing does provide an > > extensive CSV of all charges (several MB, which for CSV is >

[foreman-dev] SmartOS (Solaris 11), Joyent cloud

2017-09-28 Thread Dmitriy Morozovsky
Hello dear team. I see you support Solaris 8,10 what about Solaris 11 or SmartOS Our big infrastructure based on Joyent Cloud and we looking for support of Foreman on Solaris 11 Thanks. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To