Originally posted by bug77
View Post
Announcement
Collapse
No announcement yet.
Fedora 25 Not Scheduling A Mass Rebuild Is Raising Some Concerns
Collapse
X
-
-
Originally posted by Mystro256 View PostI still feel like this isn't a problem, given Fedora's goals. If Fedora had an LTS/enterprise support, then I would say timing would probably actually matter, but this is often filled by distros like CentOS, Scientific Linux or RHEL (which is in turn based on fedora anyway).
Haven't you heard that RHEL/CentOS are going to stay something like Fedora Enterprise Edition? They plan to update major desktop software with every point release.
Comment
-
Originally posted by chilek View Post
Haven't you heard that RHEL/CentOS are going to stay something like Fedora Enterprise Edition? They plan to update major desktop software with every point release.
Do you have a source for your claim?
Comment
-
Originally posted by Michael_S View PostI've never worked anywhere that consistently delivered software on deadline, and none of my employers have to deal with the sheer amount of code that the Fedora team does. I think expecting them to meet projected dates is absurd - they would either need to ship garbage, or fall much further behind upstream projects.
There's plenty if software that has time-based releases. You just have to remember the iron triangle rule and let scope float.
Comment
-
Originally posted by bug77 View Post
You must have missed Ubuntu (and derivatives). Or Chrome. Or Firefox.
There's plenty if software that has time-based releases. You just have to remember the iron triangle rule and let scope float.
Comment
-
Originally posted by RahulSundaram View Post
Chrome and Firefox is nowhere near the amount of code that Fedora deals with. Firefox is just one of the tens of thousands of components that Fedora ships. Ubuntu focuses on time over other factors. Fedora is explicitly not a time based release but a hybrid release where release criteria is considered more important than a strict schedule. This isn't hard to understand. Different projects have different scope and goals.
And the size of the project hardly matters at all. It's about whether you have the discipline to keep unfinished work out of your release branch.
Plus, in al my years as a software developmer, I haven't seen a situation where something marketed as "hybrid" doesn't translate into "mess". One of my favourites is the "hybrid agile" development method. You see that almost everywhere where management gets that agile is a thing, but doesn't truly get what it means.
Comment
-
Originally posted by bug77 View Post
Oh, it is hard to understand. If you're going for scope, stop publishing (tentative) roadmaps, that's all there is to it.
The schedule and roadmaps are published because this is an open source project and there are needs to coordinate internally with thousands of contributors spread across the globe and externally with other projects since Fedora contributors are deeply involved with including glibc, gcc, gnome etc.
Originally posted by bug77 View Post
And the size of the project hardly matters at all. It's about whether you have the discipline to keep unfinished work out of your release branch.
Originally posted by bug77
Plus, in al my years as a software developmer, I haven't seen a situation where something marketed as "hybrid" doesn't translate into "mess". One of my favourites is the "hybrid agile" development method. You see that almost everywhere where management gets that agile is a thing, but doesn't truly get what it means.
Comment
Comment