On 8/27/05, Bryce Harrington <bryce@...260...> wrote:
For even releases, we use the tallied bug counts like we've done before, but for odd releases (starting with 0.43), we instead count RFE scores.
This may be a good idea, but consider that a feature needs much more time to be done well, on average, than a bug. A quick bug fix is good, but a "quick feature" is not always so. I don't think we have a lot of "easy" ones in the tracker anyway.
I bet there are a bunch of RFE's in the tracker that are already implemented, but just haven't been reviewed and closed.
From time to time I do a review and close such ones. Of course there
may be some left.
Knowing how good the Inkscape team is at knocking out features, I think we could set our goal at 400 points worth of features.
I think that's too high. Unless we count everything starting from 0.42. Also most RFEs are unprioritized at 5 (and unlike bugs, how are we to prioritize them - by difficulty? by importance?)
Meanwhile only the static rpm is missing for the 0.42.2, and we can make an announcement, at least on the front page.
I've done this.
Thanks.
I wasn't able to find where the release notes are for this release, though.
They're not on the web, only in the tarball. It's just 0.42 relnotes with a few bugfixes added at the end.
Does anyone knows if Kees will be able to do static rpms? If not, are there any volunteers?
Yes, I spoke to him about RPMs after the last release. He said he will no longer do static RPMs. I think he feels that they cause more problems than they solve. I don't completely agree, but I see his point.
I'm out of my depth here, but my impression was that they worked relatively well. I think even autopackage had more bugs reported than static rpms.
Certainly I think Inkscape is an important enough project these days that we could shift more of the packaging responsibility to the distros if we wanted. Otherwise, I think he's documented the process well enough that someone else could take over this duty.
There's at least one bug report whose reporter is waiting for the static rpm to test the fix. So I think we shouild keep providing them, if only for consistency. Volunteers?