Because we have a policy of never releasing anything even a little bit backwards-incompatible in a minor release. imp, for example, has been removing obsolete drivers in main. We can remove old drives in a major release, but not in a minor one. That's why we can't release 13.1 from the main branch. -Alan On Thu, Apr 22, 2021 at 3:37 PM Ronald Klop <ronald-lists_at_klop.ws> wrote: > Hi, > > Just wondering a bit. Why wouldn't the FreeBSD project release 13.1 from > the main branch in about six months or some other time period? While making > some monthly errata releases in the meantime. > - This saves a lot of back porting of commits. > - It prevents branches with old code like the current 11-branch with an > old openssl version. Release early. > - Saves some people time in maintaining the branches. > - Saves time in coordinating the releases. Release often. > - Reduces the number of needed RC's. Because the main branch doesn't > divert a lot of what people are running in production. > - Most people start testing/production use after the release. So this > should be used as input for the main branch to improve the next release. > Currently the feedback of 13.0 is put in 14.0 which is 2 years in the > future. > > Just some thoughts. Which I really like. :-) > > Regards, > Ronald. > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Thu Apr 22 2021 - 20:00:40 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:28 UTC