From: "3.2.3" <ifoufo@yahoo.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: When is Gentoo 1.4 going to be released?
Date: Tue, 22 Oct 2002 14:21:09 -0400 [thread overview]
Message-ID: <3DB59715.455ADC02@yahoo.com> (raw)
In-Reply-To: 3DB5A6D8.2070108@fastwebnet.it
Stefano Peluchetti wrote:
>
> Thomas T. Veldhouse wrote:
> > People are looking for a general idea of a release schedule. I can not
> > blame them for asking and I can not blame them for being frustrated when
> > they don't get an answer, even if it is a ballpark figure.
>
> I am 100% of your opinion.
> If you search in the forums you will see that also A LOT of gentoo users
> thinks the same.
whoa right there. a lot of people are on crack, too. especially where
concerns a bunch wondering when someone is going to hurry up and give
them something for free.
enough software in this world is tossed over the fence according to a
schedule. i don't need any more software that was developed to a
schedule. i've got enought of that at work. i need software that is
actually ready when it is ready, whenever that is. i'm glad there is
some. eye on the ball, not some bean counter's stopwatch.
i don't know how realistic it is, but it seems to be expected to have a
schedule for software if someone is paying for the development. and that
causes an awful lot of crappy software to get developed. not to mention,
missed schedules anyway. a pmi study showed only 27% of software
projects meet schedule (up from 19% a decade ago). so much for software
schedules. what works for highway construction doesn't have much to do
with software.
a ballpark figure has been given more than once, and missed more than
once. i say, enough. it's plain to see there is no point in such straw
men, especially in free, volunteer, community efforts. obviously it will
be ready when it's ready. and only when it's ready should i want it. -i
wouldn't have it any other way!- in certain circumstances i would expect
to hear, "are we there yet?" from the backseat. this is not one of them.
> In fact the status of the development is covered by an incredible mistery...
that is so untrue. bugs.gentoo.org. it's completely transparent.
regards,
chris calloway
next prev parent reply other threads:[~2002-10-22 18:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 15:25 [gentoo-dev] When is Gentoo 1.4 going to be released? Iago Sineiro
2002-10-21 20:31 ` Michael Boman
2002-10-21 23:25 ` Jyrinx
2002-10-22 1:48 ` Jean-Michel Smith
2002-10-22 7:08 ` Iago Sineiro
2002-10-22 9:51 ` Luke Maurer
2002-10-22 13:45 ` Rigo Ketelings
2002-10-22 14:49 ` Luke Maurer
2002-10-21 20:33 ` Evan Read
2002-10-22 15:28 ` Thomas T. Veldhouse
2002-10-22 17:15 ` [gentoo-dev] " 3.2.3
2002-10-22 19:28 ` [gentoo-dev] " Stefano Peluchetti
2002-10-22 17:55 ` Thomas T. Veldhouse
2002-10-22 18:21 ` 3.2.3 [this message]
2002-10-22 19:15 ` [gentoo-dev] " Matt Beland
2002-10-22 19:43 ` Tom Syroid
2002-10-22 20:06 ` Matt Beland
2002-10-23 12:13 ` Thomas T. Veldhouse
2002-10-22 20:42 ` Stefano Peluchetti
2002-10-21 20:48 ` [gentoo-dev] " Fred Van Andel
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 16:20 [gentoo-dev] " Thomas T. Veldhouse
2002-10-27 20:25 ` Thomas M. Beaudry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DB59715.455ADC02@yahoo.com \
--to=ifoufo@yahoo.com \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox