Moving katello-packaging to foreman-packaging

Development
1

Per the previous plan proposal, for which no objections were raised, I have
started this migration process. There are a number of grouped PRs open to
foreman-packaging [1] to move the various packages into a katello/
sub-directory for now. There is a large PR open to katello-packaging to
inevitably remove and deprecate the repository (except for Katello 3.5 and
below) [2].

[1] https://github.com/theforeman/foreman-packaging/pulls
[2] https://github.com/Katello/katello-packaging/pull/575

··· -- Eric D. Helms Red Hat Engineering
2

I should also note, any currently open PRs against katello-packaging will
have to be re-opened against foreman-packaging. I will ping each PR
individually and eventually close each if there is no action taken.

Eric

··· On Sat, Nov 4, 2017 at 12:27 PM, Eric D Helms wrote:

Per the previous plan proposal, for which no objections were raised, I
have started this migration process. There are a number of grouped PRs open
to foreman-packaging [1] to move the various packages into a katello/
sub-directory for now. There is a large PR open to katello-packaging to
inevitably remove and deprecate the repository (except for Katello 3.5 and
below) [2].

[1] https://github.com/theforeman/foreman-packaging/pulls
[2] https://github.com/Katello/katello-packaging/pull/575

–
Eric D. Helms
Red Hat Engineering

–
Eric D. Helms
Red Hat Engineering

3

+1 from me

··· On Mon, Nov 6, 2017 at 4:15 PM, Greg Sutcliffe wrote:

On 06/11/17 13:20, Eric D Helms wrote:

An important part I missed with the migration and initial proposal is
around maintainers. I am proposing that all katello-packagers be given
commit access to foreman-packaging as part of this move.

+1 from me, all good candidates :slight_smile:

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

+1 for Justin, Stephen and John :slight_smile:

··· On Tue, Nov 7, 2017 at 8:01 AM, Ondrej Prazak wrote: > +1 from me > > On Mon, Nov 6, 2017 at 4:15 PM, Greg Sutcliffe > wrote: >> >> On 06/11/17 13:20, Eric D Helms wrote: >> > An important part I missed with the migration and initial proposal is >> > around maintainers. I am proposing that all katello-packagers be given >> > commit access to foreman-packaging as part of this move. >> >> +1 from me, all good candidates :) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.

–
Beste Grüße/Kind regards,

Evgeni Golov
Software Engineer

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O’Neill, Eric Shander

5

The work for this transition has completed. All packages have been moved at
this point, and katello-packaging fully deprecated. The packaging PR
testing on foreman-packaging has been updated to account for these new
packages as well as the rubygem-katello, katello-installer and
hammer_cli_katello nightly RPM builds have been updated for this shift.
Thanks for all the reviews and encouragement.

Per standard policy, I will wait a week and add the individuals nominated
to the packagers group.

Eric

··· On Tue, Nov 7, 2017 at 3:08 AM, Evgeni Golov wrote:

+1 for Justin, Stephen and John :slight_smile:

On Tue, Nov 7, 2017 at 8:01 AM, Ondrej Prazak oprazak@redhat.com wrote:

+1 from me

On Mon, Nov 6, 2017 at 4:15 PM, Greg Sutcliffe greg@emeraldreverie.org > > wrote:

On 06/11/17 13:20, Eric D Helms wrote:

An important part I missed with the migration and initial proposal is
around maintainers. I am proposing that all katello-packagers be given
commit access to foreman-packaging as part of this move.

+1 from me, all good candidates :slight_smile:

–
You received this message because you are subscribed to the Google
Groups

“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an

email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

–
Beste Grüße/Kind regards,

Evgeni Golov
Software Engineer

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O’Neill, Eric Shander

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering

6

I recall we only did nightlies so I assume KATELLO-3.5 from
katello-packaging is still active. Correct?

··· On Wed, Nov 08, 2017 at 11:49:55AM -0500, Eric D Helms wrote: >The work for this transition has completed. All packages have been moved at >this point, and katello-packaging fully deprecated. The packaging PR >testing on foreman-packaging has been updated to account for these new >packages as well as the rubygem-katello, katello-installer and >hammer_cli_katello nightly RPM builds have been updated for this shift.
7

>
>> The work for this transition has completed. All packages have been moved
>> at
>> this point, and katello-packaging fully deprecated. The packaging PR
>> testing on foreman-packaging has been updated to account for these new
>> packages as well as the rubygem-katello, katello-installer and
>> hammer_cli_katello nightly RPM builds have been updated for this shift.
>>
>
> I recall we only did nightlies so I assume KATELLO-3.5 from
> katello-packaging is still active. Correct?

Correct. That will be the last release still managed from kpackaging.

··· On Wed, Nov 8, 2017 at 1:55 PM, Ewoud Kohl van Wijngaarden < ewoud@kohlvanwijngaarden.nl> wrote: > On Wed, Nov 08, 2017 at 11:49:55AM -0500, Eric D Helms wrote:

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

–
Eric D. Helms
Red Hat Engineering

8

An important part I missed with the migration and initial proposal is
around maintainers. I am proposing that all katello-packagers be given
commit access to foreman-packaging as part of this move. All developers in
this group have shown to be solid participants in packaging, the ability to
build and maintain packages and understand the process. Those devs are:

  • Evgeni
  • Justin
  • Stephen
  • John
··· On Sat, Nov 4, 2017 at 12:28 PM, Eric D Helms wrote:

I should also note, any currently open PRs against katello-packaging will
have to be re-opened against foreman-packaging. I will ping each PR
individually and eventually close each if there is no action taken.

Eric

On Sat, Nov 4, 2017 at 12:27 PM, Eric D Helms ericdhelms@gmail.com > wrote:

Per the previous plan proposal, for which no objections were raised, I
have started this migration process. There are a number of grouped PRs open
to foreman-packaging [1] to move the various packages into a katello/
sub-directory for now. There is a large PR open to katello-packaging to
inevitably remove and deprecate the repository (except for Katello 3.5 and
below) [2].

[1] https://github.com/theforeman/foreman-packaging/pulls
[2] https://github.com/Katello/katello-packaging/pull/575

–
Eric D. Helms
Red Hat Engineering

–
Eric D. Helms
Red Hat Engineering

–
Eric D. Helms
Red Hat Engineering

9

+1

··· On Mon, Nov 06, 2017 at 08:20:26AM -0500, Eric D Helms wrote: >An important part I missed with the migration and initial proposal is >around maintainers. I am proposing that all katello-packagers be given >commit access to foreman-packaging as part of this move. All developers in >this group have shown to be solid participants in packaging, the ability to >build and maintain packages and understand the process. Those devs are: > > * Evgeni > * Justin > * Stephen > * John > >On Sat, Nov 4, 2017 at 12:28 PM, Eric D Helms wrote: > >> I should also note, any currently open PRs against katello-packaging will >> have to be re-opened against foreman-packaging. I will ping each PR >> individually and eventually close each if there is no action taken. >> >> >> Eric >> >> On Sat, Nov 4, 2017 at 12:27 PM, Eric D Helms >> wrote: >> >>> Per the previous plan proposal, for which no objections were raised, I >>> have started this migration process. There are a number of grouped PRs open >>> to foreman-packaging [1] to move the various packages into a `katello/` >>> sub-directory for now. There is a large PR open to katello-packaging to >>> inevitably remove and deprecate the repository (except for Katello 3.5 and >>> below) [2]. >>> >>> >>> [1] https://github.com/theforeman/foreman-packaging/pulls >>> [2] https://github.com/Katello/katello-packaging/pull/575
10

+1 from me, all good candidates :slight_smile:

··· On 06/11/17 13:20, Eric D Helms wrote: > An important part I missed with the migration and initial proposal is > around maintainers. I am proposing that all katello-packagers be given > commit access to foreman-packaging as part of this move.