On 12/21/2010 12:19 AM, Carsten Munk wrote:
2010/12/21 Arjan van de Ven <[email protected]
<mailto:[email protected]>>
On 12/20/2010 9:53 PM, Kangkai Yin wrote:
Hi,
Adding new package kernel-adaptation-oaktrail in project
Trunk:Testing. Please review and accept ASAP.
Justification for this new package:
The kernel for Oaktrail, fix #BMC 11588
ok this is getting silly
opening dummy bugs just to get past the paperwork, just so you can
claim you "fixed" a bug...
our bureaucrazy has gone waaaay too far.
We're in a development window, not in a "code freeze strict
bugfixes only" part of the schedule!
Well, and we're side-stepping program management totally by having
those dummy bugs. A new package should be a FEA# and approved by
program management as per
http://wiki.meego.com/Release_Engineering/Process#Package_quality_expectations_for_submissions_into_.2A:Testing_projects
ok that's another fun bureaucrazy ....
tracking desired features is very valuable; it helps people focus and it
helps corporations know where they want to invest their resources; it
helps then be reassured that the outcome is useful for a wide enough set
of customers that it's worth investing their resources.
but on the flip side, requiring that every little thing goes through
such an approval process goes to far if you ask me. The paperwork gets
way out of proportion with the actual work. In addition, if someone
implements something cool and contributes it to MeeGo, that's what
community contribution is about. We should be saying "thank you sir" not
"please fill out this stack of paperwork in threefold and we may let you
put it in".
Right now we just get another list of "dummy" FEA requests (which are
just bugzilla bugs anyway) that serve no other purpose than to get the
form filled in threefold.... the program or project is not getting value
out of those that I can see in any way, shape or form.
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
