On Tue, Dec 15, 2015 at 03:55:47PM +0000, Peter Robinson wrote:
>> On 11/20/2015 04:13 PM, Josh Boyer wrote:
>> >Hi All,
>> >
>> >Really no different from any of the last major version rebases we've
>> >done. We'll likely rebase F23 to the 4.3.y kernel around the time
>> >4.3.1 or 4.3.2 is released upstream. Until then, the stabilization
>> >branch is tracking what should eventually be merged into F23.
>> >
>> >F22 will follow sometime thereafter. F21 will not be rebased to 4.2
>> >or 4.3 and will go EOL with 4.1.13. Please migrate off of F21 as soon
>> >as possible.
>> >
>> >If you have questions, please let us know.
>>
>> 4.3.3 has now been release but no sign of it in F23.
>
> It won't be submitted until January. We don't want to do a major rebase
> the week before most of us go away on PTO. There is a COPR that
Does it make sense to consider just going straight to 4.4 then given
it'll be out early Jan?
That's a good question. Let's assume 4.4 is released on Jan 10, which is
a bit longer than normal because of the holidays. 4.4.1 would be out
roughly around the beginning of Feb, as long as the normal schedule
holds up. So we'd be on 4.2.y for all of Jan, but it will be EOL before
then.
Being on 4.3 for a month isn't a terrible thing. It will help narrow
down regressions vs. just skipping to 4.4. On the other hand, more
churn is more churn.
I think we're going to have to just see how the upstream releases go. I
know that doesn't answer the question, but we can keep an eye on it now
that you've brought it up.
josh