If you have any critical fixes that you think should be included in 1.15
in any of the core projects, please reply to this read to raise
attention over them. Maintainers feel free to set the 1.15 label to
any PR of that nature.
Note that we will be branching puppet modules as well and soon after
drop puppet 3 in master. Since I'd like backport as little as possible,
please try to get your PRs in before branching.
···
On Fri, Mar 10, 2017 at 07:43:48PM +0100, Daniel Lobato Garcia wrote:
> As per http://projects.theforeman.org/projects/foreman/wiki/Foreman_115_Schedule,
> 1.15 is due to be branched soon, in 2 weeks approximately.
>
> Please help to make develop more stable during this process, be it through
> thorough testing, bugfixing or improving documentation.
>
> Help with updating the manual would be appreciated, see the list of
> tasks in:
> - https://github.com/theforeman/theforeman.org/issues/765
>
> Some translations are nearing 100% completion, we welcome contributions
> that help finishing them for the next release:
> - https://www.transifex.com/foreman/foreman/foreman/
>
> If you have any critical fixes that you think should be included in 1.15
> in any of the core projects, please reply to this read to raise
> attention over them. Maintainers feel free to set the 1.15 label to
> any PR of that nature.
otherwise the syncing from community-templates before the release will be much
harder.
···
On pátek 10. března 2017 19:43:48 CET Daniel Lobato Garcia wrote:
> As per
> http://projects.theforeman.org/projects/foreman/wiki/Foreman_115_Schedule,
> 1.15 is due to be branched soon, in 2 weeks approximately.
>
> Please help to make develop more stable during this process, be it through
> thorough testing, bugfixing or improving documentation.
>
> Help with updating the manual would be appreciated, see the list of
> tasks in:
> - https://github.com/theforeman/theforeman.org/issues/765
>
> Some translations are nearing 100% completion, we welcome contributions
> that help finishing them for the next release:
> - https://www.transifex.com/foreman/foreman/foreman/
>
> If you have any critical fixes that you think should be included in 1.15
> in any of the core projects, please reply to this read to raise
> attention over them. Maintainers feel free to set the 1.15 label to
> any PR of that nature.
We're planning to do the branching on all projects on March 28th -
please keep it in mind and try to get
things that would be important for 1.15 by then.
I do not have commit access everywhere, so please check the following
list and reply if you
could take care of cherry-picking and branching:
foreman - Daniel - dlobatog
foreman-installer - Stephen - stbenjam
smart-proxy - Daniel - dlobatog - (or Dmitri - witlessb if you prefer)
foreman-selinux - Lukas - lzap
foreman-packaging - Eric - ehelms theforeman.org - Daniel - dlobatog
translations - Daniel - dlobatog
community-templates - Daniel - dlobatog
hammer-cli - Tomas? Martin?
hammer-cli-foreman - Tomas? Martin?
puppet-foreman - ?
puppet-foreman_proxy - ?
···
On Fri, Mar 10, 2017 at 7:43 PM, Daniel Lobato Garcia wrote:
> As per http://projects.theforeman.org/projects/foreman/wiki/Foreman_115_Schedule,
> 1.15 is due to be branched soon, in 2 weeks approximately.
>
> Please help to make develop more stable during this process, be it through
> thorough testing, bugfixing or improving documentation.
>
> Help with updating the manual would be appreciated, see the list of
> tasks in:
> - https://github.com/theforeman/theforeman.org/issues/765
>
> Some translations are nearing 100% completion, we welcome contributions
> that help finishing them for the next release:
> - https://www.transifex.com/foreman/foreman/foreman/
>
> If you have any critical fixes that you think should be included in 1.15
> in any of the core projects, please reply to this read to raise
> attention over them. Maintainers feel free to set the 1.15 label to
> any PR of that nature.
>
> Best,
>
> --
> Daniel Lobato Garcia
>
> @dLobatog
> blog.daniellobato.me
> daniellobato.me
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
> Keybase: https://keybase.io/elobato
> We're planning to do the branching on all projects on March 28th -
> please keep it in mind and try to get
> things that would be important for 1.15 by then.
>
> I do not have commit access everywhere, so please check the following
> list and reply if you
> could take care of cherry-picking and branching:
>
> foreman - Daniel - dlobatog
> foreman-installer - Stephen - stbenjam
> smart-proxy - Daniel - dlobatog - (or Dmitri - witlessb if you prefer)
> foreman-selinux - Lukas - lzap
> foreman-packaging - Eric - ehelms
> theforeman.org - Daniel - dlobatog
> translations - Daniel - dlobatog
> community-templates - Daniel - dlobatog
> hammer-cli - Tomas? Martin?
> hammer-cli-foreman - Tomas? Martin?
I'll take care of hammer branching and release.
···
On Tue, Mar 14, 2017 at 2:28 PM, Daniel Lobato wrote:
puppet-foreman - ?
puppet-foreman_proxy - ?
On Fri, Mar 10, 2017 at 7:43 PM, Daniel Lobato Garcia > elobatocs@gmail.com wrote:
If you have any critical fixes that you think should be included in 1.15
in any of the core projects, please reply to this read to raise
attention over them. Maintainers feel free to set the 1.15 label to
any PR of that nature.
>> We're planning to do the branching on all projects on March 28th -
>> please keep it in mind and try to get
>> things that would be important for 1.15 by then.
>>
>> I do not have commit access everywhere, so please check the following
>> list and reply if you
>> could take care of cherry-picking and branching:
>>
>> foreman - Daniel - dlobatog
>> foreman-installer - Stephen - stbenjam
>> smart-proxy - Daniel - dlobatog - (or Dmitri - witlessb if you prefer)
yes can do.
-d
···
On Wed, Mar 15, 2017 at 8:10 AM, Tomas Strachota wrote:
> On Tue, Mar 14, 2017 at 2:28 PM, Daniel Lobato wrote:
foreman-selinux - Lukas - lzap
foreman-packaging - Eric - ehelms theforeman.org - Daniel - dlobatog
translations - Daniel - dlobatog
community-templates - Daniel - dlobatog
hammer-cli - Tomas? Martin?
hammer-cli-foreman - Tomas? Martin?
I’ll take care of hammer branching and release.
puppet-foreman - ?
puppet-foreman_proxy - ?
On Fri, Mar 10, 2017 at 7:43 PM, Daniel Lobato Garcia >> elobatocs@gmail.com wrote:
If you have any critical fixes that you think should be included in 1.15
in any of the core projects, please reply to this read to raise
attention over them. Maintainers feel free to set the 1.15 label to
any PR of that nature.
I will begin branching Foreman, theforeman.org, community-templates
and translations in approximately 5 hours.
If you have signed up to branch any of the projects in this thread,
please feel free to do so any time today.
Remember, after branching, we still have time to submit patches to
ensure the release is stable during the RC period.
Expect a new RC to come out every week approximately since now.
Thanks for your collaboration!
···
On Thu, Mar 16, 2017 at 11:45 AM, Dmitri Dolguikh wrote:
> On Wed, Mar 15, 2017 at 8:10 AM, Tomas Strachota wrote:
>> On Tue, Mar 14, 2017 at 2:28 PM, Daniel Lobato wrote:
>>> We're planning to do the branching on all projects on March 28th -
>>> please keep it in mind and try to get
>>> things that would be important for 1.15 by then.
>>>
>>> I do not have commit access everywhere, so please check the following
>>> list and reply if you
>>> could take care of cherry-picking and branching:
>>>
>>> foreman - Daniel - dlobatog
>>> foreman-installer - Stephen - stbenjam
>>> smart-proxy - Daniel - dlobatog - (or Dmitri - witlessb if you prefer)
>
> yes can do.
> -d
>
>>> foreman-selinux - Lukas - lzap
>>> foreman-packaging - Eric - ehelms
>>> theforeman.org - Daniel - dlobatog
>>> translations - Daniel - dlobatog
>>> community-templates - Daniel - dlobatog
>>> hammer-cli - Tomas? Martin?
>>> hammer-cli-foreman - Tomas? Martin?
>>
>> I'll take care of hammer branching and release.
>>
>>> puppet-foreman - ?
>>> puppet-foreman_proxy - ?
>>>
>>>
>>> On Fri, Mar 10, 2017 at 7:43 PM, Daniel Lobato Garcia >>> wrote:
>>>> As per http://projects.theforeman.org/projects/foreman/wiki/Foreman_115_Schedule,
>>>> 1.15 is due to be branched soon, in 2 weeks approximately.
>>>>
>>>> Please help to make develop more stable during this process, be it through
>>>> thorough testing, bugfixing or improving documentation.
>>>>
>>>> Help with updating the manual would be appreciated, see the list of
>>>> tasks in:
>>>> - https://github.com/theforeman/theforeman.org/issues/765
>>>>
>>>> Some translations are nearing 100% completion, we welcome contributions
>>>> that help finishing them for the next release:
>>>> - https://www.transifex.com/foreman/foreman/foreman/
>>>>
>>>> If you have any critical fixes that you think should be included in 1.15
>>>> in any of the core projects, please reply to this read to raise
>>>> attention over them. Maintainers feel free to set the 1.15 label to
>>>> any PR of that nature.
>>>>
>>>> Best,
>>>>
>>>> --
>>>> Daniel Lobato Garcia
>>>>
>>>> @dLobatog
>>>> blog.daniellobato.me
>>>> daniellobato.me
>>>>
>>>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
>>>> Keybase: https://keybase.io/elobato
>>>
>>>
>>>
>>> --
>>> Daniel Lobato
>>>
>>> @dlobatog
>>> daniellobato.me
>>>
>>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
>>>
>>> --
>>> 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.
>
> --
> 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.
···
On Tue, Mar 28, 2017 at 1:57 PM, Daniel Lobato wrote:
> Hi all,
>
> I will begin branching Foreman, theforeman.org, community-templates
> and translations in approximately 5 hours.
> If you have signed up to branch any of the projects in this thread,
> please feel free to do so any time today.
>
> Remember, after branching, we still have time to submit patches to
> ensure the release is stable during the RC period.
> Expect a new RC to come out every week approximately since now.
>
> Thanks for your collaboration!
>
> On Thu, Mar 16, 2017 at 11:45 AM, Dmitri Dolguikh wrote:
>> On Wed, Mar 15, 2017 at 8:10 AM, Tomas Strachota wrote:
>>> On Tue, Mar 14, 2017 at 2:28 PM, Daniel Lobato wrote:
>>>> We're planning to do the branching on all projects on March 28th -
>>>> please keep it in mind and try to get
>>>> things that would be important for 1.15 by then.
>>>>
>>>> I do not have commit access everywhere, so please check the following
>>>> list and reply if you
>>>> could take care of cherry-picking and branching:
>>>>
>>>> foreman - Daniel - dlobatog
>>>> foreman-installer - Stephen - stbenjam
>>>> smart-proxy - Daniel - dlobatog - (or Dmitri - witlessb if you prefer)
>>
>> yes can do.
>> -d
>>
>>>> foreman-selinux - Lukas - lzap
>>>> foreman-packaging - Eric - ehelms
>>>> theforeman.org - Daniel - dlobatog
>>>> translations - Daniel - dlobatog
>>>> community-templates - Daniel - dlobatog
>>>> hammer-cli - Tomas? Martin?
>>>> hammer-cli-foreman - Tomas? Martin?
>>>
>>> I'll take care of hammer branching and release.
>>>
>>>> puppet-foreman - ?
>>>> puppet-foreman_proxy - ?
>>>>
>>>>
>>>> On Fri, Mar 10, 2017 at 7:43 PM, Daniel Lobato Garcia >>>> wrote:
>>>>> As per http://projects.theforeman.org/projects/foreman/wiki/Foreman_115_Schedule,
>>>>> 1.15 is due to be branched soon, in 2 weeks approximately.
>>>>>
>>>>> Please help to make develop more stable during this process, be it through
>>>>> thorough testing, bugfixing or improving documentation.
>>>>>
>>>>> Help with updating the manual would be appreciated, see the list of
>>>>> tasks in:
>>>>> - https://github.com/theforeman/theforeman.org/issues/765
>>>>>
>>>>> Some translations are nearing 100% completion, we welcome contributions
>>>>> that help finishing them for the next release:
>>>>> - https://www.transifex.com/foreman/foreman/foreman/
>>>>>
>>>>> If you have any critical fixes that you think should be included in 1.15
>>>>> in any of the core projects, please reply to this read to raise
>>>>> attention over them. Maintainers feel free to set the 1.15 label to
>>>>> any PR of that nature.
>>>>>
>>>>> Best,
>>>>>
>>>>> --
>>>>> Daniel Lobato Garcia
>>>>>
>>>>> @dLobatog
>>>>> blog.daniellobato.me
>>>>> daniellobato.me
>>>>>
>>>>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
>>>>> Keybase: https://keybase.io/elobato
>>>>
>>>>
>>>>
>>>> --
>>>> Daniel Lobato
>>>>
>>>> @dlobatog
>>>> daniellobato.me
>>>>
>>>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
>>>>
>>>> --
>>>> 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.
>>
>> --
>> 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.
>
>
>
> --
> Daniel Lobato
>
> @dlobatog
> daniellobato.me
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
>
> --
> 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.
PS: If you're impatient enough to not wait until tomorrow, you can find
the builds that will be published at http://koji.katello.org/
···
On 03/28, Daniel Lobato wrote:
> Hi all,
>
> I will begin branching Foreman, theforeman.org, community-templates
> and translations in approximately 5 hours.
> If you have signed up to branch any of the projects in this thread,
> please feel free to do so any time today.
>
> Remember, after branching, we still have time to submit patches to
> ensure the release is stable during the RC period.
> Expect a new RC to come out every week approximately since now.
>
> Thanks for your collaboration!
>
> On Thu, Mar 16, 2017 at 11:45 AM, Dmitri Dolguikh wrote:
> > On Wed, Mar 15, 2017 at 8:10 AM, Tomas Strachota wrote:
> >> On Tue, Mar 14, 2017 at 2:28 PM, Daniel Lobato wrote:
> >>> We're planning to do the branching on all projects on March 28th -
> >>> please keep it in mind and try to get
> >>> things that would be important for 1.15 by then.
> >>>
> >>> I do not have commit access everywhere, so please check the following
> >>> list and reply if you
> >>> could take care of cherry-picking and branching:
> >>>
> >>> foreman - Daniel - dlobatog
> >>> foreman-installer - Stephen - stbenjam
> >>> smart-proxy - Daniel - dlobatog - (or Dmitri - witlessb if you prefer)
> >
> > yes can do.
> > -d
> >
> >>> foreman-selinux - Lukas - lzap
> >>> foreman-packaging - Eric - ehelms
> >>> theforeman.org - Daniel - dlobatog
> >>> translations - Daniel - dlobatog
> >>> community-templates - Daniel - dlobatog
> >>> hammer-cli - Tomas? Martin?
> >>> hammer-cli-foreman - Tomas? Martin?
> >>
> >> I'll take care of hammer branching and release.
> >>
> >>> puppet-foreman - ?
> >>> puppet-foreman_proxy - ?
> >>>
> >>>
> >>> On Fri, Mar 10, 2017 at 7:43 PM, Daniel Lobato Garcia > >>> wrote:
> >>>> As per http://projects.theforeman.org/projects/foreman/wiki/Foreman_115_Schedule,
> >>>> 1.15 is due to be branched soon, in 2 weeks approximately.
> >>>>
> >>>> Please help to make develop more stable during this process, be it through
> >>>> thorough testing, bugfixing or improving documentation.
> >>>>
> >>>> Help with updating the manual would be appreciated, see the list of
> >>>> tasks in:
> >>>> - https://github.com/theforeman/theforeman.org/issues/765
> >>>>
> >>>> Some translations are nearing 100% completion, we welcome contributions
> >>>> that help finishing them for the next release:
> >>>> - https://www.transifex.com/foreman/foreman/foreman/
> >>>>
> >>>> If you have any critical fixes that you think should be included in 1.15
> >>>> in any of the core projects, please reply to this read to raise
> >>>> attention over them. Maintainers feel free to set the 1.15 label to
> >>>> any PR of that nature.
> >>>>
> >>>> Best,
> >>>>
> >>>> --
> >>>> Daniel Lobato Garcia
> >>>>
> >>>> @dLobatog
> >>>> blog.daniellobato.me
> >>>> daniellobato.me
> >>>>
> >>>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
> >>>> Keybase: https://keybase.io/elobato
> >>>
> >>>
> >>>
> >>> --
> >>> Daniel Lobato
> >>>
> >>> @dlobatog
> >>> daniellobato.me
> >>>
> >>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
> >>>
> >>> --
> >>> 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.
> >
> > --
> > 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.
>
>
>
> --
> Daniel Lobato
>
> @dlobatog
> daniellobato.me
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
foreman-packaging RPMs have been branched to rpm/1.15 and updated per the
release process instructions (mmoll is awaiting one change to get in before
he branches the debian branch per IRC conversation).
Katello (katello, katello-installer, katello-packaging) have all been
officially branched, tags created in koji and mash scripts generated. If
anyone has time, a docs PR has been opened to create the 3.4 docs based off
of nightly [1]. There are currently 11 issues marked against 3.4.0 [2] any
help review or tackling them is much appreciated. Expect RC1 to align with
Foreman RC1 per the rough schedule [3].
The Katello puppet modules will need to be released in the next few days.
Ewoud has started a list of PRs he'd like to see get in before those
releases are cut [4]. Again, if anyone has some time to spare for review
and testing it would be much appreciated to ensure a smooth RC1.
I will begin branching Foreman, theforeman.org, community-templates
and translations in approximately 5 hours.
If you have signed up to branch any of the projects in this thread,
please feel free to do so any time today.
Remember, after branching, we still have time to submit patches to
ensure the release is stable during the RC period.
Expect a new RC to come out every week approximately since now.
We’re planning to do the branching on all projects on March 28th -
please keep it in mind and try to get
things that would be important for 1.15 by then.
I do not have commit access everywhere, so please check the following
list and reply if you
could take care of cherry-picking and branching:
foreman - Daniel - dlobatog
foreman-installer - Stephen - stbenjam
smart-proxy - Daniel - dlobatog - (or Dmitri - witlessb if you prefer)
yes can do.
-d
foreman-selinux - Lukas - lzap
foreman-packaging - Eric - ehelms theforeman.org - Daniel - dlobatog
translations - Daniel - dlobatog
community-templates - Daniel - dlobatog
hammer-cli - Tomas? Martin?
hammer-cli-foreman - Tomas? Martin?
I’ll take care of hammer branching and release.
puppet-foreman - ?
puppet-foreman_proxy - ?
On Fri, Mar 10, 2017 at 7:43 PM, Daniel Lobato Garcia > >>>> elobatocs@gmail.com wrote:
If you have any critical fixes that you think should be included in
1.15
in any of the core projects, please reply to this read to raise
attention over them. Maintainers feel free to set the 1.15 label to
any PR of that nature.
> > foreman-packaging RPMs have been branched to rpm/1.15 and updated per
> > the release process instructions
>
> Where are the 1.15 build targets and tags?
>
They should now be present.
···
On Thu, Mar 30, 2017 at 5:42 AM, Dominic Cleal wrote:
> On 30/03/17 04:25, Eric D Helms wrote:
