No, it is not a good time. A project like Ubuntu should now be in freeze as they had about 3 months before release and definitely it should not have a break in something basic just because the language used to write the command break backword compatibilty
No, it is not a good time. A project like Ubuntu should now be in freeze as they had about 3 months before release
This bug was reported (and resolved by rolling back to the GNU coreutils version of cp) on June 30, a little over 15 weeks prior to the scheduled release date.
Which distros have a feature freeze that far in advance?
Ubuntu hasn’t even scheduled theirs for 26.10 yet; if you edit that url to look at previous releases’ schedules you can see their feature freeze and debian import freezes are typically about 2 months prior to release. (See here for descriptions of all of the different types of freezes…)
I’d say the month of June is actually a good time to be breaking and fixing things in a release that is due to come out in (checks notes) October.
No, it is not a good time. A project like Ubuntu should now be in freeze as they had about 3 months before release and definitely it should not have a break in something basic just because the language used to write the command break backword compatibilty
This bug was reported (and resolved by rolling back to the GNU coreutils version of
cp) on June 30, a little over 15 weeks prior to the scheduled release date.Which distros have a feature freeze that far in advance?
Ubuntu hasn’t even scheduled theirs for 26.10 yet; if you edit that url to look at previous releases’ schedules you can see their feature freeze and debian import freezes are typically about 2 months prior to release. (See here for descriptions of all of the different types of freezes…)
I like staying up to date about open source but holy cow is there too many of these “omg they broke something in testing”. Yah, that’s the point.