Z:gnu-www-ja-maintainer-tips--c2cd3d-=3Cb=3EAim for a quick first relea/en

Aim for a quick first release. Whether your package is new or you've adopted an older one, your number one priority should be making a first release as soon as possible. If you've adopted a package, it's sufficient to fix a few bugs and push that out. In fact, just updating the infrastructure files (e.g., Autoconf/Automake, gnulib modules, etc.) is enough to justify a new release when you've first taken over a package. If your package is new, don't be afraid to put out an early version that is not yet feature complete. In any case, a release (with proper announcements) will draw attention to your package in the form of potential users or even other developers. It is the best way to let people know that an old package has been revived or that a new package exists at all. (About making releases.)