Internally @rpm5.org we're starting to discuss how maintenance and
development releases for rpm should be done.

So its time to ask:
     How often should rpm-5.0.Z releases be done?
     What should be in the rpm-5.1 roadmap? And approx what release  
date?

Currently pending is a rpm-5.0.2 release to fix two
moderately severe problems:

     1) rpm -Uvh foo.rpm does not stop with failed dependencies
	because the return code of rpmtsCheck() was always 0
	(the traditional behavior was to return 0, logic to check
	the return code was what caused the flaw).

     2) RPMTAG_FILESTATES is always "normal" because the
	tag was added to header's earlier due to a --rollback
	code refactoring, before the values were set correctly.

There is also significant development in cvs HEAD that is ready
for "release", perhaps as rpm-5.0.Z or perhaps as rpm-5.1, depending
on one's POV. See the NEWS file in cvs HEAD for additional details.

So its time to commit to some release dates, as well as to start  
scheduling
deployment of new "features", for both rpm-5.0.Z and rpm-5.1.

The major difference between a rpm-5.0.Z and a rpm-5.1 release is
that library names change in rpm-5.1. So large incompatible changes
belong in rpm-5.1, not rpm-5.0.Z.

Any other "features" or implementation requests for rpm?

73 de Jeff