Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Request for a version/ revision/ release number for the whole Cygwin release/ distribution Date: Mon, 4 Oct 2004 12:49:51 +0200 Message-ID: <0C7AD907113E984F9C2AF0B651D0D3DE07BBBB@exmid04.africa.enterprise.root> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Mike Kenny - BCX - Infrastructure Services" To: "David Christensen" , X-OriginalArrivalTime: 04 Oct 2004 10:49:51.0807 (UTC) FILETIME=[E04C54F0:01C4A9FF] X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i94AoWfN020628 > -----Original Message----- > From: cygwin-owner AT cygwin DOT com > [mailto:cygwin-owner AT cygwin DOT com]On Behalf > Of David Christensen > Sent: Sunday, October 03, 2004 4:15 AM > To: cygwin AT cygwin DOT com > Subject: RE: Request for a version/ revision/ release number for the > whole Cygwin release/ distribution .... .... > > I don't think there are enough potential volunteer man-hours to make > such a thing feasible. > > I disagree. Assume for a moment that all Cygwin project member > development efforts can be put into the following bins: > > 1. Code development. > > 2. Design documentation. > > 3. Test suite development. > > 4. Test suite documentation. > > 5. Test suite execution and reporting. > > 6. User documentation. > > 7. Packaging for distribution. > > 8. Infrastructure development. > > 9. Infrastructure administration. > > 10. Version control/ configuration management of all of the above. > > 11. Personnel leadership and project management. > > It would seem that bin #1 is consuming the majority of the effort. I > think that by changing priorities and re-allocating people and > resources, it should be possible to create integration tests and a > "stable" distribution. Such would increase Cygwin's acceptance and > usage for potentially hundreds of millions of people. Is this not a > good thing? It seems to me that as it is a volunteer community, the people in question would need to volunteer to be re-allocated. This does not seem to be happening. :-) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/