Hi,

On Feb 3, 2008 1:45 PM, Jeff Johnson <n3npq@mac.com> wrote:
> 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.

I'm obviously just following along, but I would say rpm-5.0.z releases
as often as you can manage with just fixes. Any new features should go
in 5.1, IMO. That reduces the consumer's work considerably since you'd
know that bumps in z for x.y.z were just bug fixes and should be
applied instead of always looking for potential breakage with each
release.

Thanks for RPM.

--
Dan