RC1 was released successfully this morning, thanks for everybody's work!
Issues that are high priority or blockers for 1.8.0 will continue to
show up on this list once triaged: http://bit.ly/172VbxZ. If you think
something needs adding there, let me know please. Corresponding PRs
should also be labeled as "1.8 priority".
Documentation still needs work, which I'm tracking on this ticket:
https://github.com/theforeman/theforeman.org/issues/307
Question for Hammer folks, do you plan on releasing in the next week or
so, or it be later? Currently 1.8 ships 0.1.4 (and 1.7 shipped 0.1.3).
I expect to have one more release candidate in just under two weeks
time, on the assumption there will be some important bugs found and
fixes going in, then will make a call after RC2 as to whether to cut .0
or a further RC.
remains pretty much up to date too.
Cheers,
···
--
Dominic Cleal
Red Hat Engineering
> RC1 was released successfully this morning, thanks for everybody's work!
>
> Issues that are high priority or blockers for 1.8.0 will continue to
> show up on this list once triaged: http://bit.ly/172VbxZ. If you think
> something needs adding there, let me know please. Corresponding PRs
> should also be labeled as "1.8 priority".
>
> Documentation still needs work, which I'm tracking on this ticket:
> https://github.com/theforeman/theforeman.org/issues/307
>
> Question for Hammer folks, do you plan on releasing in the next week or
> so, or it be later? Currently 1.8 ships 0.1.4 (and 1.7 shipped 0.1.3).
>
I hope to merge last blockers next week and release the week after.
The major issue pending merge is smart variables and override values
support [1]. Once we merge this one I'd like to extract strings and give
translators a few days for updates.
T.
[1] https://github.com/theforeman/hammer-cli-foreman/pull/153/files
···
On 03/11/2015 01:39 PM, Dominic Cleal wrote:
I expect to have one more release candidate in just under two weeks
time, on the assumption there will be some important bugs found and
fixes going in, then will make a call after RC2 as to whether to cut .0
or a further RC.
Foreman 18 Schedule - Foreman
remains pretty much up to date too.
Cheers,
Just a reminder, this list is growing and any help to clear the new open
issues would be appreciated, thanks.
···
On 11/03/15 12:39, Dominic Cleal wrote:
> Issues that are high priority or blockers for 1.8.0 will continue to
> show up on this list once triaged: http://bit.ly/172VbxZ. If you think
> something needs adding there, let me know please. Corresponding PRs
> should also be labeled as "1.8 priority".
–
Dominic Cleal
Red Hat Engineering
Okay, thanks for the update. I think those features are more important
than fitting it into our release process, so we can perhaps look at
including it in 1.8.1 or RC3 if we get that far.
···
On 12/03/15 09:44, Tomas Strachota wrote:
> On 03/11/2015 01:39 PM, Dominic Cleal wrote:
>> RC1 was released successfully this morning, thanks for everybody's work!
>>
>> Issues that are high priority or blockers for 1.8.0 will continue to
>> show up on this list once triaged: http://bit.ly/172VbxZ. If you think
>> something needs adding there, let me know please. Corresponding PRs
>> should also be labeled as "1.8 priority".
>>
>> Documentation still needs work, which I'm tracking on this ticket:
>> https://github.com/theforeman/theforeman.org/issues/307
>>
>> Question for Hammer folks, do you plan on releasing in the next week or
>> so, or it be later? Currently 1.8 ships 0.1.4 (and 1.7 shipped 0.1.3).
>>
>
> I hope to merge last blockers next week and release the week after.
>
> The major issue pending merge is smart variables and override values
> support [1]. Once we merge this one I'd like to extract strings and give
> translators a few days for updates.
–
Dominic Cleal
Red Hat Engineering
