Reuben Thomas wrote: > diff --git a/top/README-release b/top/README-release > index 69841d2..0299c82 100644 > --- a/top/README-release > +++ b/top/README-release > @@ -40,7 +40,7 @@ Here are most of the steps we (maintainers) follow > when making a release. > # "TYPE" must be stable, beta or alpha > make TYPE > > -* Test the tarball. copy it to a few odd-ball systems and ensure that > +* Test the tarball. Copy it to a few odd-ball systems and ensure that > it builds and passes all tests. > > * While that's happening, write the release announcement that you will > > Changelog: > > 2011-08-19 Reuben Thomas <r...@sc3d.org> > > * top/README-release: Fix typo.
Thanks. Pushed. > (Is this paragraph actually necessary, though? These days, if more > "odd-ball" systems are needed for testing, they should be added to > nix, surely?) IMHO, it is needed, at least for some projects. "odd-ball" may merely mean with a less-common kernel or distro release, a system with less-common file system types, etc. ZFS, btrfs and ocfs2 support come to mind for coreutils, not to mention something NFS-mounted. For parted, s390x is important, as well as powerpc64, which brings up endianness. Then there are ARM variants, etc. It would be great if nix would add a PPC-based build system.
