From owner-freebsd-questions@FreeBSD.ORG Fri Dec 12 19:28:07 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E1E51065673 for ; Fri, 12 Dec 2008 19:28:07 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.187]) by mx1.freebsd.org (Postfix) with ESMTP id CBAE98FC08 for ; Fri, 12 Dec 2008 19:28:06 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so1532801fkk.11 for ; Fri, 12 Dec 2008 11:28:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ItDB8HyUNevgBtnEbbZ+Fgc7NPKAd6PSzk2iaHqFpT0=; b=Zr+n6RWbVTvyGQm2DmHVmk+BjVxlC2rGBwUcozB6rdy41yNW3yNBb+3nb8WXTbKJZC bUnq838Ssiw+bY6ZY/QE5tsRxiGWY2mmhITsBX3sPS1bdKll4BEeKViebXKb/GrBS0/t ho8fL9cjRo4bsb0s/eePIUc30L2qDjzRR80D0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=B6dLl5W8CrhgeVRniccj+c0bmNVu2/CSOhrG7lj6YQ/JEJRGqf9bQEIHGwAnIcVGqf 4JTTLCqeKGQ5/mOEPSClcND/hEWT+KSiJMig3EUBa6W8+4F6gmzRIRhPDuqqoGCa7G5t XgJAQA8O88l5lag6UYg2+jiB0liP/OQFiiWpY= Received: by 10.103.171.6 with SMTP id y6mr2004922muo.31.1229110085574; Fri, 12 Dec 2008 11:28:05 -0800 (PST) Received: by 10.103.169.16 with HTTP; Fri, 12 Dec 2008 11:28:05 -0800 (PST) Message-ID: <4ad871310812121128y18db1c19n8aa45dcc75794739@mail.gmail.com> Date: Fri, 12 Dec 2008 14:28:05 -0500 From: "Glen Barber" To: "Maxim Khitrov" In-Reply-To: <26ddd1750812121113o1590d54r9962ec3d22a20bdb@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200811121259.25046.jonathan+freebsd-questions@hst.org.za> <20081112120147.GA62386@slackbox.xs4all.nl> <18754.42851.295211.155980@jerusalem.litteratus.org> <4ad871310812121028m4e368da4n69e06d592e312eb0@mail.gmail.com> <26ddd1750812121113o1590d54r9962ec3d22a20bdb@mail.gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Release schedules X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 19:28:07 -0000 On Fri, Dec 12, 2008 at 2:13 PM, Maxim Khitrov wrote: > > This discussion has come up countless number of times and the answer > is always the same - all of us would rather wait for quality, but we'd > also like some very rough timeline estimates that don't fall back into > the past. Notice that I said nothing about them having to be 100% > accurate. The questions are about the published timelines, the answers > are about the process. Hence, nothing ever gets resolved. It makes no > sense at all to have a published timeline, but claim that it is > irrelevant because "it's done when it's done." Do you not agree? > I agree to a point. I wouldn't push something out if it was less than what could/should be expected. I haven't been a FreeBSD user long enough to remember the (previously quoted) "5.0 debacle", but I'm sure if I waited for a new release only to be disappointed, who knows what OS I may have went with. Yes, keeping users informed on the status of releases is nice -- that's what we have the ML for. > For example, RC2 builds were scheduled for 29 September 2008. When > that day comes (or same week perhaps), whoever has the ability to > change the release schedule page should update it regardless of what > happened. If RC2 builds started, that should be reflected in the > 'actual' column. Otherwise, if it's a minor change in the timeline, > put the new expected date in. As is the case of 7.1 release, if the > person honestly has no idea when RC2 will happen, put in 'December', > 'January', 'Second half of January'... 'Sometime next year' if it's > that uncertain. Anything at all; it takes 5 minutes to do. In the > worst case, your estimate will need to be updated again in a month or > two. In the best case, the release will be made before the expected > date. I, for one, promise not to complain about that. :) > If the sacrifice is an out-of-date column in a webpage while bugs are being worked out, in my opinion, that's fine with me. (IMHO) -- Glen Barber