Foreman 1.3 has almost 80 issues tracked

Development
1

Hello all,

we have three weeks to RC1 and there are so many issues there. Please
help me to bring this number down a bit.

I am not accepting issues/features into the 1.3 release any longer,
except urgent ones.

Also I would like to ask Tomas/Martin to retarged those features/issues
for CLI, which are not targeted for the 1.3 release.

Thanks for cooperation!

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

2

> Hello all,
>
> we have three weeks to RC1 and there are so many issues there. Please
> help me to bring this number down a bit.
>
> I am not accepting issues/features into the 1.3 release any longer,
> except urgent ones.

I disagree with this approach. We've traditionally taken patches into
the feature branch right up until the RC1 was released and then things
got more stringent.

··· On 08/19/2013 11:23 AM, Lukas Zapletal wrote:

Also I would like to ask Tomas/Martin to retarged those features/issues
for CLI, which are not targeted for the 1.3 release.

Thanks for cooperation!

3

Let me put this right.

Please do not put new issues (without code) on 1.3 target, except
important ones.

If you have a patch/feature already, there is no doubt ticket needs to
be created and scheduled for 1.3.

··· On Mon, Aug 19, 2013 at 12:43:17PM -0400, Sam Kottler wrote: > > I am not accepting issues/features into the 1.3 release any longer, > > except urgent ones. > > I disagree with this approach. We've traditionally taken patches into > the feature branch right up until the RC1 was released and then things > got more stringent.

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

4

>>> I am not accepting issues/features into the 1.3 release any longer,
>>> except urgent ones.
>> I disagree with this approach. We've traditionally taken patches into
>> the feature branch right up until the RC1 was released and then things
>> got more stringent.
> Let me put this right.
>
> Please do not put new issues (without code) on 1.3 target, except
> important ones.

I think what we need to do is put together some criteria for what can be
targeted in the initial RC and when development freeze happens. Since
we've always done development work right up until the first RC we should
probably have a bigger conversation if we want to change it.

··· On 08/19/2013 02:57 PM, Lukas Zapletal wrote: > On Mon, Aug 19, 2013 at 12:43:17PM -0400, Sam Kottler wrote:

If you have a patch/feature already, there is no doubt ticket needs to
be created and scheduled for 1.3.

5

Okay, after some discussion with Dominic and Greg on the IRC, I will
follow this historical approach when RC1 is treated as a dev freeze
milestone.

Everything is open now, feel free to spam me with features and issues.

··· On Mon, Aug 19, 2013 at 04:35:11PM -0400, Sam Kottler wrote: > I think what we need to do is put together some criteria for what can be > targeted in the initial RC and when development freeze happens. Since > we've always done development work right up until the first RC we should > probably have a bigger conversation if we want to change it.

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman