On 06/06/16 07:59, Tomas Strachota wrote:
> On 06/01/2016 09:04 AM, Tomas Strachota wrote:
>> On 05/31/2016 05:02 PM, Dominic Cleal wrote:
>>> On 31/05/16 15:03, Dominic Cleal wrote:
>>>> In preparation for the first 1.12 release candidate, I've branched the
>>>> develop branch on these repos to 1.12-stable: foreman, smart-proxy,
>>>> foreman-installer, foreman-selinux, community-templates,
>>>> foreman-packaging.
>>>>
>>>> I'd like to be able to release RC1 in the next week or so, and would
>>>> love some help to get the following items complete:
>>>>
>>>> 1) Fixing regressions in 1.12:
>>>> http://projects.theforeman.org/projects/foreman/issues?query_id=99
>>>> https://github.com/theforeman/foreman/labels/1.12.0
>>>>
>>>> 2) Documenting 1.12 changes - we've got lots of Puppet and smart proxy
>>>> changes to document in this release. The full task list is at:
>>>> https://github.com/theforeman/theforeman.org/issues/555
>>>>
>>>> 3) Installer releases - we need to start releasing new major/minor
>>>> versions of our installer modules to the Forge. I think they're mostly
>>>> ready.
>>>
>>> 4) Hammer CLI releases - currently we'll be shipping Hammer CLI 0.6.1
>>> with 0.6.2 of hammer_cli_foreman, but if a new version could be cut from
>>> master if there's something to release, these can be updated.
>>
>> There are some changes worth releasing. I'll do 0.7 this week.
>>
> 
> The hammer 0.7 had to be postponed a bit due to this regression: 
> http://projects.theforeman.org/issues/15257
> 
> I hope this will get fixed this week. I'd still like to release 0.7 for 
> the Foreman 1.12.

No worries, thanks for the update. RC1 should be out today or tomorrow,
so RC2 would be in a further 1.5 to 2 weeks, giving you some time.

-- 
Dominic Cleal
domi...@cleal.org

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to