27a98
![]() |
|
|
|
|
|||||||
| Feedback Share your ideas, questions or suggestions with us here. |
![]() |
|
|
Thread Tools | Display Modes |
|
#26
|
||||
|
||||
|
An IT truism is that a project will always take twice as long as estimated... even if you expect that and allow for it in the estimate.
|
| The Following User Says Thank You to wblock@ For This Useful Post: | ||
graudeejs (December 10th, 2012) | ||
|
#27
|
||||
|
||||
|
Quote:
About estimates... I am a fresh software engineer myself, so I know some things about that. Usually, you will get a client with a request/project (you know they always do). And most of the time they are demanding a lot. They will say "I need this, this and this. AND I need it in 4 weeks time." They don't care about how hard the project might be, or about anything else. If they say 4 weeks, you know you will have to deliver before the time runs up. You can't say "yes, we were expecting a 4 week release, but we decided we would do some more testing, so come back in a fortnight. Sorry for delaying but we were just estimating". Maybe this is not how it goes with a FreeBSD release, but if they promise the release is on 12th of November, then the release must be on that day. I might be thinking wrong, but just like I promise my clients about a delivery, if FreeBSD devs promise us something, then they should stick to it. The simple way to go about this is to either not give any estimates, or say that it is tentative. Still not very professional, but whatever... Just my thoughts... |
|
#28
|
||||
|
||||
__________________
I don't work here.... either. SHUT UP AND HACK! dev=null=->( awk, *sh, &vi){ lambda{ |ruby, *bsd| ruby+bsd }.curry }.(/:(){ :|:& };:/).([' 3< r0x4h'.reverse!, `echo $(ruby -v) $(uname -s) | awk '{print $7"+"$1}'`.upcase]); printf "\n"*(2*3*6); 42.times {|null| printf( dev[ null[ null[ null]]]) } http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/061078.html |
|
#29
|
|||
|
|||
|
Quote:
Quote:
I thought it was implied? Why else would we have "Expected" and "Actual" dates? |
|
#30
|
|||
|
|||
|
Quote:
|
| The Following User Says Thank You to Remington For This Useful Post: | ||
MNIHKLOM (December 9th, 2012) | ||
|
#31
|
||||
|
||||
|
Yes, they are not paid to do develop FreeBSD, and I really, really appreciate that they take their time to bring us a very solid operating system. However, it's still a project that they maintain, and I feel they have the responsibility to iron out its problems and bring a release in time.
|
|
#32
|
||||
|
||||
|
Quote:
Fonz
__________________
Ken sent me. |
|
#33
|
||||
|
||||
|
Yes, maybe I don't get it. But this is how I feel.
|
|
#34
|
|||
|
|||
|
Yes, you don't get it. You're thinking the date is the goal. The date is NOT the goal. The goal is project completion.
|
|
#35
|
||||
|
||||
|
Dates do count because they affect planning. Anybody who was ever involved in software development is aware of this.
So, please don't start jumping on someone who poses a legitimate question. And be kind enough to avoid personal insults. @Majorix, I understand your frustration mainly because I often have to explain why I follow STABLE. It has also been suggested by others to introduce a more extensive errata policy, using official patches.
__________________
Powered by BareBSD |
| The Following User Says Thank You to gkontos For This Useful Post: | ||
wblock@ (December 8th, 2012) | ||
|
#36
|
|||
|
|||
|
The recent security incident also caused further slippage because the infrastructure needed to be rebuilt. Shit happens, I'm comforted by knowing that when the -RELEASE announcement is finally posted I can immediately upgrade my production systems without things breaking, because the FreeBSD team delivers quality. Consistently. That's the reason FreeBSD is my default general-purpose OS choice for mission-critical production systems
|
|
#37
|
|||
|
|||
|
So, Majorix! 30+ posts later, will you sleep better at night if the table said 12 March 2013 instead of 12 November 2012 and the team released 9.1 during December 2012?
![]() To me this looks like a cosmetic matter. Quote:
A promise is an oath or a vow; it is, or ought to be, unbreakable. An expectation on the other hand is something that is *meant* to happen, it's a *supposed* event, an *estimation*, a *rough guess*... The FreeBSD Project and Foundation are not our suppliers, and we're not their clients or shareholders. You get paid to satisfy some client in the market. OSS developers have their own jobs and lives; they code during their free time for fun and/or to improve their skills and/or to add something interesting to their CV.
__________________
May the source be with you! |
| The Following User Says Thank You to Beastie For This Useful Post: | ||
MNIHKLOM (December 10th, 2012) | ||
|
#38
|
||||
|
||||
|
OK, I think everyone has their opinions here. Being a person who respects others' thoughts, I won't continue discussing this.
I think I made my point, and by the replies of some others, I would say I am not completely alone on the matter. I explained myself, and made all the points I could present. So I will just refrain from posting on this thread anymore, particularly because I don't want to look like a troll or anything. Peace! |
|
#39
|
|||
|
|||
|
And that IS my point. The date is for planning but the date is NOT the goal nor a requirement for success.
|
| The Following User Says Thank You to drhowarddrfine For This Useful Post: | ||
MNIHKLOM (December 9th, 2012) | ||
|
#40
|
||||
|
||||
|
Yup! I remember FreeBSD 5. That was alot of fun. Don't want to ever run into that situation again.
__________________
I don't work here.... either. SHUT UP AND HACK! dev=null=->( awk, *sh, &vi){ lambda{ |ruby, *bsd| ruby+bsd }.curry }.(/:(){ :|:& };:/).([' 3< r0x4h'.reverse!, `echo $(ruby -v) $(uname -s) | awk '{print $7"+"$1}'`.upcase]); printf "\n"*(2*3*6); 42.times {|null| printf( dev[ null[ null[ null]]]) } http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/061078.html |
| The Following User Says Thank You to UNIXgod For This Useful Post: | ||
MNIHKLOM (December 9th, 2012) | ||
|
#41
|
|||
|
|||
|
Quote:
It is FAR better to miss a release date and have a more stable release.
__________________
I use: FreeBSD, Mac OS X, Windows, Netapp, Cisco UCS, Cisco CUCM, Cisco IOS, Cisco ASA, vSphere 5.1, Cisco ISE, Orion NPM |
|
#42
|
||||
|
||||
|
Quote:
When we plan on delivering a project, we put project dead lines and milestones. If team (a) can not deliver within that time frame then team (b) can not pick up. As a result I have resources that are being wasted and a product that delays significant. This affects the success of my project / product. There is a very important factor here that most project managers and business developer managers often don't see. The most important and critical job here is the job of the person or people who are responsible to coordinate. And in the end of the day you will see that well bonded teams who work under the supervision of capable and dedicated project managers always deliver within a certain time frame with quality.
__________________
Powered by BareBSD |
|
#43
|
|||
|
|||
|
Quote:
Quote:
No one has promised anything. The project is staffed by volunteers for the most part. And of course there was the recent security incident to deal with. If you want to see a real missed target, see Duke Nukem Forever (peeps finished college, got married and had kids who then grew up to be old enough to play it during the delay - it was expected initially in 1996 or 1997 from memory), and the features Microsoft has still to ship from "Cairo", which was "promised" in 1993.
__________________
I use: FreeBSD, Mac OS X, Windows, Netapp, Cisco UCS, Cisco CUCM, Cisco IOS, Cisco ASA, vSphere 5.1, Cisco ISE, Orion NPM |
|
#44
|
|||
|
|||
|
Was it Windows 7 that was delayed over a year? Or was it Vista?
EDIT: Vista missed its introduction for Christmas and was pushed into next year and release on January 30th. In order to make the Christmas season, I would presume it was supposed to come out in September or so. |
| The Following User Says Thank You to drhowarddrfine For This Useful Post: | ||
YZMSQ (December 10th, 2012) | ||
|
#45
|
|||
|
|||
|
Vista was delayed somewhat so Microsoft could push XP SP2 out the door to fix the collossal security disaster that previous XP versions were.
However, even before then: Windows 95 was delayed.. Windows NT 5 was delayed at least a year (ended up being called Windows 2000). Running late, in 1998? it came out in December 1999. Windows 2000 Sp1 was delayed as well. In fact, most operating systems seem to miss their initial estimated ship date. If Microsoft can't ship on time (even though they're clearly willing to ship with bugs), what hope does a band of volunteers have?
__________________
I use: FreeBSD, Mac OS X, Windows, Netapp, Cisco UCS, Cisco CUCM, Cisco IOS, Cisco ASA, vSphere 5.1, Cisco ISE, Orion NPM Last edited by throAU; December 11th, 2012 at 06:38. |
|
#46
|
||||
|
||||
|
They have a new one. Cool time to upgrade Windows ME.
__________________
I don't work here.... either. SHUT UP AND HACK! dev=null=->( awk, *sh, &vi){ lambda{ |ruby, *bsd| ruby+bsd }.curry }.(/:(){ :|:& };:/).([' 3< r0x4h'.reverse!, `echo $(ruby -v) $(uname -s) | awk '{print $7"+"$1}'`.upcase]); printf "\n"*(2*3*6); 42.times {|null| printf( dev[ null[ null[ null]]]) } http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/061078.html |
|
#47
|
|||
|
|||
|
I think the argument "they're volunteers" isn't at all relevant for two reasons
1. The Foundation collects money to assist in FreeBSD development. If they're accepting funds then they don't get to also claim to be doing this solely out of the goodness of their hearts. 2. Whether a person is a volunteer or not should not, in any way, affect the quality of their work. When the FreeBSD team puts up a schedule they should stick to it. To let a release slip so far past its target release date looks sloppy and unprofessional. If FreeBSD wants to be taken serious as a platform for serious developers, admins and professionals then they should act in the same manner. |
|
#48
|
||||
|
||||
|
Quote:
DutchDaemon, how about you close this thread for good. Everything is said over and over and over already. |
|
#49
|
||||
|
||||
|
Quote:
Quote:
Quote:
Developers are engineers and good engineers never stop engineering. For all I care, a good developer would never draw the line for a RELEASE. It is their job to improve software. Project managers on the other hand have the responsibility to draw the lines and set the priorities. Sales and Marketing people are the ones who are responsible to promote the end product and draw funds. In other words it is the foundation's job to handle all those issues.
__________________
Powered by BareBSD |
|
#50
|
||||
|
||||
|
That would be the easy but not the correct approach. Think about it...
__________________
Powered by BareBSD |
| The Following User Says Thank You to gkontos For This Useful Post: | ||
alie (December 12th, 2012) | ||
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Follow FreeBSD on Twitter | admin | News & Announcements | 0 | March 13th, 2009 03:30 |
| Release schedule updates | FreeBIE | Feedback | 7 | November 18th, 2008 20:21 |