Home_greyopenFATE - openSUSE feature tracking > #305591
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Define Purpose for each openSUSE Build Service Project

Feature state

Buildservice
Evaluation By Productmanager

Description

define purpose for each project, like:

  • add-on package
  • fresh packages + libraries (eg. games)
  • bleeding edge packages (eg. zypp:svn)
  • backports for older distributions (eg. zypp:Backport)
  • playground (eg. all home projects)
So,
  • this sets users expectations
  • purpose could be indicated by naming conventions, or even better
    by project flags
  • purpose must be shown in the search result for this method to work

References

http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00056.html

Discussion


icons/user_comment.png A. J. wrote: (8 years ago)

This sounds like a good idea. What needs to be done to make this happen?

icons/user_comment.png A. S. wrote: (8 years ago)

I think we can fullfill this request by two independend features:

  • Project classification setting to be set by the project owner (this is handled in #306232)
  • Automatic QA validation how a package will influence the system, for example:
  • replace base packages
  • replace files
  • replace libaries
  • just being an add-on

icons/user_comment.png A. S. wrote: (4 years ago)

The project classification is possible via setting attribute OBS:QualityCategory to one of the allowed values:

Stable
Testing
Development
Private

However, there is no webui and osc support yet, so this is basically unused. webui project creation should make it easy to set it and search in webui/osc/software needs to use it.

Last change: 4 years ago
Voting
Score: 6
  • Negative: 0
  • Neutral: 0
  • Positive: 6
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint