Bug ID 1113638
Summary Request: A Bugzilla workflow to report out of date packages
Classification openSUSE
Product openSUSE.org
Version unspecified
Hardware Other
OS Other
Status NEW
Severity Minor
Priority P5 - None
Component Bugzilla
Assignee bnc-team-screening@forge.provo.novell.com
Reporter sean@suspend.net
QA Contact novbugzilla-bugs@forge.provo.novell.com
Found By ---
Blocker ---

Hello,

I've been transitioning my infrastructure to openSUSE over the past few months
and have been particularly attracted to the development model of Factory/TW ->
LEAP -> SLE. openSUSE provides options and choice for users regardless of what
end of the innovation timeline they want to jump in on. 

I'm primarily using TW and have identified a good amount of packages that were
out of date. I've updated a lot of these on my own and submitted requests, I
really enjoy the scrappy 'make the project how you want it to be' atmosphere.
For others, I've filed bug reports to give the maintainers a chance to Rev the
package; this could be a more complicated package or something that's more
critical to the core functionality of the distribution.

I'd like to request feedback on a potential new workflow in Bugzilla.
Tumbleweed -> Component = "Out of date package". This would allow users to file
out of date package submissions without needing to go to the catch-all 'Other'
bucket like I've been using today. I'd also like to volunteer to create a wiki
page detailing how users can file these reports (along with a quick tutorial on
how they can rev the package on their own, if possible). I've received feedback
from a few project members that "out of date packages are not a bug"
conflicting with "you should file a bug report if you see something out of
date"; this could help set consistent guidelines for the community on this
topic, help keep TW fresh and new packages flowing into the rest of the
distribution and identify packages where the maintainers are absent or have
abandoned the package so we can identify a new project owner. 

I'd appreciate any feedback on this idea, thanks.

Sean


You are receiving this mail because: