reopen 544515
thanks
> Rather than chasing VCS revisions, I'm waiting for the project to make
> a proper release as a regular tarball. See the discussion for this at
> <URL:http://void.printf.net/pipermail/be-devel/2009-November/000309.html>.
>
> I'm closing this report; once the project makes a proper versioned
> release, if there's no corresponding activity from this package's
> maintainer, a new bug report would be appropriate at that time.
It is reasonable for users to expect new releases for the packages, even
from version control if the project isn't releasing regularly. The
current release in Debian is:
0.0.193+bzr.r217-2
Which is
revno: 217
committer: W. Trevor King <wk...@drexel.edu>
branch nick: be-bugfix
timestamp: Fri 2008-11-14 00:00:51 -0500
message:
Closed bug 210 (target options not parsed).
I imagine this has been fixed for a while...
Over a year old. The bug report's asked version was from 2009-07-23 and
latest seems to be:
revno: 330 [merge]
committer: Chris Ball <c...@laptop.org>
branch nick: be
timestamp: Tue 2009-10-06 10:56:47 -0400
If the release is near, it wold be more appropriate to
- Keep this bug open
- Mark it pending
- Close it, when release happens
Marking it wontfix won't help users to get improvements for the
packages. I would also be wary at having to ask to issue yet another bug
for the same problem in the future. How is this better than the outlined
actions above?
Please also consider point, that someone else that might be also
requesting a newer version via reportbug wouldn't see that one was
already previously requested.
It wouldn't be "chasing packages" if the project is followed, say in 6
month intervals.
Jari Aalto
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
