[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

debian amd64 timeline



This email is not meant to start another flamewar, it is just to educate
some uninformed individuals about the circumstances and how long the
amd64 port has actually been waiting.


2003/04/24 - debian-x86-64 alioth project created [0]
2003/05/12 - debian-x86-64-devel - list created [1]
2003/05/23 - debian-x86-64-devel - arch name "amd64" [2]
2003/05/25 - debian-x86-64 - list created [3]
2003/08/21 - debian-x86-64 - Martin Schulze suggests renaming the port list to debian-amd64 [4]
2003/08/30 - debian-amd64 - list renamed [5]
2003/09/11 - debian-amd64 alioth project created [6]
2004/02/10 - debian-amd64 - John Goerzen sets up a pure64 autobuilder [7]
2004/02/11 - debian-amd64 - John Goerzen creates pure64 chroot image [8]
2004/02/12 - debian-amd64 - 3000 packages compiled [9]
2004/02/19 - debian-amd64 - 5616 packages compiled [10]
2004/03/03 - debian-amd64 - John Goerzen asked ftpmaster for archive space with no response, 6000 packages compiled [11]
2004/03/21 - billie (SCC) checked into dak cvs [12]
2004/03/30 - debian-amd64 - John Goerzen discussed adding amd64 to the archive with DPL [13]
2004/04/17 - debian-amd64 - almost working debian-installer created [14]
2004/04/27 - "amd64" arch support added to dpkg cvs [15]
2004/05/08 - Bug 248043 - ftp.debian.org: Request for new architecture: amd64 - no response from ftpmaster [16]
2004/05/10 - debian-amd64 - wanna-build setup on alioth [17]
2004/05/11 - debian-amd64 - (4527/8115) packages compiled [18]
2004/05/16 - debian-amd64 - (6843/7879) packages compiled [19]
2005/05/25 - debian-amd64 - working (but buggy) debian-installer created [20]
2004/06/01 - dpkg uploaded supporting "x86-64" instead [21]
2004/06/11 - debian-devel-annouce - (7719/7972) packages compiled, request publically for support [22]
2004/06/15 - Scott James Remnant refused to use "amd64" name and took the issue to tech-ctte [23]
2004/06/18 - email sent to ftpmaster about their questions on amd64 port per DPL's request - no response from ftpmaster [24]
2004/06/23 - tech-ctte decision to use name "amd64" [25]
2004/07/01 - debian-devel-announce - (8160/8376) packages compiled, request publically for support [26]
2004/07/06 - Daniel Silverstone comments on irc that an announcement would be made by ftpmaster within a few weeks. [27]
2004/07/13 - debian-devel - GR Proposal to release sarge with amd64 [28]
2004/07/19 - dpkg uploaded supporting "amd64" per tech-ctte [29]
2004/07/25 - Announcement of pending Sarge freeze [30]
2004/07/31 - Debian Sarge freeze begins...


As you can see from the timeline amd64 has been above other included
archs (hurd/sh) level of support for over 5 months now. No one from
ftpmaster has yet to respond to any requests for information as far as
I know. Also notice that _no one_ was processed by the DAM in a 5 month
period between Feb 25 and Jul 27 (a few got processed since yesterday).
I think it is understandable that some people involved with the amd64
port could be very upset. A little communication from ftpmaster would
have helped this situation immensely.

Chris Cheney


[0] http://alioth.debian.org/projects/debian-x86-64/
[1] http://lists.alioth.debian.org/pipermail/debian-x86-64-devel/2003-May/000000.html
[2] http://lists.alioth.debian.org/pipermail/debian-x86-64-devel/2003-May/000020.html
[3] http://lists.debian.org/debian-amd64/2003/05/msg00000.html
[4] http://lists.debian.org/debian-amd64/2003/08/msg00022.html
[5] http://lists.debian.org/debian-amd64/2003/08/msg00104.html
[6] http://alioth.debian.org/projects/debian-amd64/
[7] http://lists.debian.org/debian-amd64/2004/02/msg00206.html
[8] http://lists.debian.org/debian-amd64/2004/02/msg00216.html
[9] http://lists.debian.org/debian-amd64/2004/02/msg00235.html
[10] http://lists.debian.org/debian-amd64/2004/02/msg00336.html
[11] http://lists.debian.org/debian-amd64/2004/03/msg00015.html
[12] http://cvs.debian.org/dak/billie?cvsroot=dak
[13] http://lists.debian.org/debian-amd64/2004/03/msg00121.html
[14] http://lists.debian.org/debian-amd64/2004/04/msg00099.html
[15] http://cvs.debian.org/dpkg/archtable?cvsroot=dpkg
[16] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=248043
[17] http://lists.debian.org/debian-amd64/2004/05/msg00107.html
[18] http://lists.debian.org/debian-amd64/2004/05/msg00138.html
[19] http://lists.debian.org/debian-amd64/2004/05/msg00167.html
[20] http://lists.debian.org/debian-amd64/2004/05/msg00244.html
[21] http://lists.debian.org/debian-devel-changes/2004/06/msg00107.html
[22] http://lists.debian.org/debian-devel-announce/2004/06/msg00002.html
[23] http://lists.debian.org/debian-ctte/2004/06/msg00037.html
[24] http://lists.debian.org/debian-devel/2004/07/msg02041.html
[25] http://lists.debian.org/debian-ctte/2004/06/msg00115.html
[26] http://lists.debian.org/debian-devel-announce/2004/07/msg00001.html
[27] http://lists.debian.org/debian-amd64/2004/07/msg00034.html
[28] http://lists.debian.org/debian-devel/2004/07/msg00508.html
[29] http://lists.debian.org/debian-devel-changes/2004/07/msg01720.html
[30] http://lists.debian.org/debian-devel-announce/2004/07/msg00016.html

Attachment: signature.asc
Description: Digital signature


Reply to: