I do not know what release plan Linus has in mind, and also expect things to be quieter next week during OLS and kernel summit, but I think we are getting really really close.
Here are the things I think we would want to see before we hit 1.0: - Remaining feature enhancements and fixes. - Anonymous pull from packed archives on remote sites via non-rsync, non-ssh transport. Many people are behind corporate firewalls that do not pass anything but outgoing http(s) and some do not even pass outgoing ssh. The recent addition of git-daemon by Linus would greatly alleviate the situation, but we may also end up wanting something HTTP reachable. - Documentation. - Many files under Documentation/ directory have become stale. I've tried to do one pass of full sweep recently, but I'd like somebody else to make another pass to make sure that the usage strings in programs, what the programs do, and what Documentation says they do match. Also, the spelling and grammar fixes, which I am very bad at and have not done any attempt, needs to be done. Volunteers? - Are all the files in Documentation/ reachable from git(7) or otherwise made into a standalone document using asciidoc by the Makefile? I haven't looked into documentation generation myself (I use only the text files as they are); help to update the Makefile by somebody handy with asciidoc suite is greatly appreciated here. Volunteers? - We may want to describe more Best Current Practices, along the lines of "Working with Others" section in the tutorial. Please write on your faviorite topic and send patches in ;-)) - Publicity. I would be very happy to see somebody with good writing and summarizing skills to prepare an article to be published on LWN.NET to coincide with the 1.0 release. An update to GIT traffic would also be nice. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html