From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Last mile to 1.0?
Date: Sat, 16 Jul 2005 10:46:00 -0700 [thread overview]
Message-ID: <7vwtnqhcfb.fsf@assigned-by-dhcp.cox.net> (raw)
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.
next reply other threads:[~2005-07-16 17:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 17:46 Junio C Hamano [this message]
2005-07-16 18:36 ` Last mile to 1.0? Eric W. Biederman
2005-07-17 0:49 ` Junio C Hamano
2005-07-17 1:18 ` David Lang
2005-07-18 5:44 ` Junio C Hamano
2005-07-18 4:53 ` Alexey Nezhdanov
2005-07-18 5:35 ` Junio C Hamano
2005-07-18 6:48 ` Alexey Nezhdanov
2005-07-18 7:38 ` Junio C Hamano
2005-07-23 8:15 ` Ryan Anderson
2005-07-23 12:56 ` Gene Heskett
2005-07-24 0:53 ` [PATCH 0/6] A bit better dumb server support Junio C Hamano
2005-07-23 8:50 ` Last mile to 1.0? Ryan Anderson
2005-07-23 13:14 ` Gene Heskett
2005-07-23 14:47 ` Kevin Smith
2005-07-23 17:09 ` Junio C Hamano
2005-07-24 3:12 ` Alexey Nezhdanov
2005-07-29 22:41 ` Petr Baudis
2005-07-30 2:11 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 5:40 barkalow
2005-07-30 8:07 ` Junio C Hamano
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=7vwtnqhcfb.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).