Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-27 Thread Eric D Helms
The work to transfer tool_belt officially to theforeman for use is now complete. The foreman configs have been moved into the repository, the old repository deleted and the original transferred. I have created a team to manage the repository based on the top code committers to date. If you'd like

Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-26 Thread Eric D Helms
I've began this process by capturing what I believe is everything from [1] as an PR to the mainline tool_belt repository: https://github.com/ehelms/tool_belt/pull/58 Once this is approved, I will do the delete and transfer dance. [1] https://github.com/theforeman/tool_belt On Mon, Oct 23,

Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-23 Thread Andrew Kofink
+1 I guess the foreman and katello config files will still live separately (i.e. katello_35.yaml and foreman_16.yaml) but in the same repo. On Mon, Oct 23, 2017 at 5:59 AM, Daniel Lobato Garcia wrote: > On 10/20, Eric D Helms wrote: > > For quite a few releases now, we've

Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-23 Thread Greg Sutcliffe
On Fri, 2017-10-20 at 16:59 -0400, Eric D Helms wrote: > > If there are no objections, I will perform this next Wednesday or > Thursday. +1 -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups

Re: [foreman-dev] Centralizing tool_belt in theforeman Github

2017-10-22 Thread Ewoud Kohl van Wijngaarden
On Fri, Oct 20, 2017 at 04:59:33PM -0400, Eric D Helms wrote: For quite a few releases now, we've been using a little tool named tool_belt as a CLI to perform release tasks such as finding cherry picks, or building koji configurations. The larger idea of the repository is you define a release