[openFATE 306232] Quality Classification Of Projects

Feature added by: Adrian Schröter (adrianSuSE) Feature #306232, revision 1, last change by Title: Quality Classification Of Projects Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. * BROKEN -- project is known to be not working atm. -- openSUSE Feature: https://features.opensuse.org/306232

Feature changed by: Pavol Rusnak (prusnak) Feature #306232, revision 3 Title: Quality Classification Of Projects Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. * BROKEN -- project is known to be not working atm. + Discussion: + #1: Pavol Rusnak (prusnak) (2009-03-17 15:35:16) + Very similar to feature#305591. Please merge both ideas. -- openSUSE Feature: https://features.opensuse.org/306232

Feature changed by: Andreas Jaeger (a_jaeger) Feature #306232, revision 6 Title: Quality Classification Of Projects Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. * BROKEN -- project is known to be not working atm. Discussion: #1: Pavol Rusnak (prusnak) (2009-03-17 15:35:16) Very similar to feature#305591. Please merge both ideas. + #2: Andreas Jaeger (a_jaeger) (2009-06-09 16:00:42) + Adrian, can you merge 305591 and this one - and move them forward? -- openSUSE Feature: https://features.opensuse.org/306232

Feature changed by: Adrian Schröter (adrianSuSE) Feature #306232, revision 12 Title: Quality Classification Of Projects Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Info Provider: (Novell) Requested by: Adrian Schröter (adriansuse) Developer: (Novell) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. - * BROKEN -- project is known to be not working atm. + * PRIVATE -- project is known to be not working atm. Discussion: #1: Pavol Rusnak (prusnak) (2009-03-17 15:35:16) Very similar to feature#305591. Please merge both ideas. #2: Andreas Jaeger (a_jaeger) (2009-06-09 16:00:42) Adrian, can you merge 305591 and this one - and move them forward? -- openSUSE Feature: https://features.opensuse.org/306232

Feature changed by: Adrian Schröter (adrianSuSE) Feature #306232, revision 13 Title: Quality Classification Of Projects Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Info Provider: (Novell) Requested by: Adrian Schröter (adriansuse) Developer: (Novell) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. - * PRIVATE -- project is known to be not working atm. + * PRIVATE -- project is not intentended to be used. Discussion: #1: Pavol Rusnak (prusnak) (2009-03-17 15:35:16) Very similar to feature#305591. Please merge both ideas. #2: Andreas Jaeger (a_jaeger) (2009-06-09 16:00:42) Adrian, can you merge 305591 and this one - and move them forward? -- openSUSE Feature: https://features.opensuse.org/306232

Feature changed by: Lee Matheson (oldcpu) Feature #306232, revision 14 Title: Quality Classification Of Projects Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Info Provider: (Novell) Requested by: Adrian Schröter (adriansuse) Developer: (Novell) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. * PRIVATE -- project is not intentended to be used. Discussion: #1: Pavol Rusnak (prusnak) (2009-03-17 15:35:16) Very similar to feature#305591. Please merge both ideas. #2: Andreas Jaeger (a_jaeger) (2009-06-09 16:00:42) Adrian, can you merge 305591 and this one - and move them forward? + #3: Lee Matheson (oldcpu) (2010-04-23 20:44:44) + Feature 308469, while suggesting a differnet way, was also hoping to + move things forward in this reguard. As initiator of 308469, I would + also happy to see it merged with this and adopt an approach such as + this. -- openSUSE Feature: https://features.opensuse.org/306232

Feature changed by: jpxviii jpxviii (jpxviii) Feature #306232, revision 15 Title: Quality Classification Of Projects Buildservice: Evaluation Priority - Requester: Important + Requester: Mandatory Projectmanager: Important Info Provider: (Novell) Requested by: Adrian Schröter (adriansuse) Developer: (Novell) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. * PRIVATE -- project is not intentended to be used. Discussion: #1: Pavol Rusnak (prusnak) (2009-03-17 15:35:16) Very similar to feature#305591. Please merge both ideas. #2: Andreas Jaeger (a_jaeger) (2009-06-09 16:00:42) Adrian, can you merge 305591 and this one - and move them forward? #3: Lee Matheson (oldcpu) (2010-04-23 20:44:44) Feature 308469, while suggesting a differnet way, was also hoping to move things forward in this reguard. As initiator of 308469, I would also happy to see it merged with this and adopt an approach such as this. -- openSUSE Feature: https://features.opensuse.org/306232

Feature changed by: Sascha Peilicke (saschpe) Feature #306232, revision 16 Title: Quality Classification Of Projects Buildservice: Evaluation by engineering manager Priority Requester: Mandatory Projectmanager: Important Info Provider: (Novell) Requested by: Adrian Schröter (adriansuse) Developer: (Novell) Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. * PRIVATE -- project is not intentended to be used. Discussion: #1: Pavol Rusnak (prusnak) (2009-03-17 15:35:16) Very similar to feature#305591. Please merge both ideas. #2: Andreas Jaeger (a_jaeger) (2009-06-09 16:00:42) Adrian, can you merge 305591 and this one - and move them forward? #3: Lee Matheson (oldcpu) (2010-04-23 20:44:44) Feature 308469, while suggesting a differnet way, was also hoping to move things forward in this reguard. As initiator of 308469, I would also happy to see it merged with this and adopt an approach such as this. + #4: Sascha Peilicke (saschpe) (2010-11-16 13:56:32) + Seems to be a subset of feature #310604 -- openSUSE Feature: https://features.opensuse.org/306232

Feature changed by: Adrian Schröter (adrianSuSE) Feature #306232, revision 18 Title: Quality Classification Of Projects - Buildservice: Evaluation by engineering manager + Buildservice: Done + Milestone: 2.3 Priority Requester: Mandatory Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Technical Contact: Robert Lihm (rlihm) Partner organization: openSUSE.org Description: A Project should get a classification, set by the project owner about the general quality. This classification should have an influence to the software search for the end user (by default he wants stable stuff, but he might also looks for latest snapshots). Possible classifications are: * STABLE -- project is considered to be ready to use for End-Users * TESTING -- project should work from point of developer view, but needs verification * DEVELOPMENT -- project is random state, it might work. * PRIVATE -- project is not intentended to be used. Discussion: #1: Pavol Rusnak (prusnak) (2009-03-17 15:35:16) Very similar to feature#305591. Please merge both ideas. #2: Andreas Jaeger (a_jaeger) (2009-06-09 16:00:42) Adrian, can you merge 305591 and this one - and move them forward? #3: Lee Matheson (oldcpu) (2010-04-23 20:44:44) Feature 308469, while suggesting a differnet way, was also hoping to move things forward in this reguard. As initiator of 308469, I would also happy to see it merged with this and adopt an approach such as this. #4: Sascha Peilicke (saschpe) (2010-11-16 13:56:32) Seems to be a subset of feature #310604 + #5: Adrian Schröter (adriansuse) (2012-04-17 09:33:23) + The api part is done 2.3, so closing this one. The other requests are + still open for webui & software.o.o support. -- openSUSE Feature: https://features.opensuse.org/306232
participants (1)
-
fate_noreply@suse.de