Re: [Bug-sysutils] Changes

[Jeff Bailey]

On Wed, 2004-05-19 at 04:48, David Weinehall wrote:
> (Since we have no other mailing-list at the moment, I'm sending the
>  status-updates here)

Most gnu projects just carry on discussion on bug- until the project
gets quite large.

> I've added one more option to chsh and also checked in changed versions
> of all manual-pages.

I need to hack on Savannah to get cvs commit messages going.  Doesn't
look like I can do this before debconf, though.

> Furthermore I've fixed a typo in the project-description on Savannah
> (unless sysutils is meant to compliment rather than coreutils...)

Well..  Praise is always good, isn't it? =)

> and changed status to Pre-Alpha.  I'm hoping that we should be able to
> go Alpha in a month or so.

How do you usually define these?  When I do commercial software I tend
to go with the following:

1) Alpha - Feature incomplete
2) Beta - Feature complete, known bugs.
3) Gamma - We believe that this version, without changes, could be
released.

The last one is basically a brown bag catcher. =)  I usually skip it in
Free Software projects.

> Unless someone has serious objections, I'm going to implement
> add-shell and remove-shell this weekend, probably together with
> write, wall, last, lastlog, faillog and possibly chpasswd.

None.  Thanks!

> BTW Jeff, what generated file I did I mistakenly check in?

COPYING.  When updating your autotools, do:

autoreconf -f -i -s

And it should leave it as a symlink (and many of the others).  If you
ever want to make a release tarball for handing to someone else, you can
do

make release

Which will produce a sysutils-YYYYMMDD.tar.gz,

or

make dist

Which produces a tarball with the version number.

Tks,
Jeff Bailey

-- 
I never know what to expect when you respond to my postings. No insult
intended, you are merely a surprise :)
 - Carlos O'Donnell

signature.asc
Description: This is a digitally signed message part