[Bug 168310] Review Request: swish-e <bkyoung>

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: swish-e <bkyoung>


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=168310


j.w.r.degoede at hhs.nl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |j.w.r.degoede at hhs.nl




------- Additional Comments From j.w.r.degoede at hhs.nl  2006-04-22 05:06 EST -------
Bryon,

Jumping in fresh here, I just have been appointed sponsorship rights and as such
I'm looking through bugs in FE-NEEDSPONSOR. 

You are clearly willing to invest time in FE and seem to be doing your best,
however sofar things haven't been going really smoothly. Mainly I believe
because you've been doing your best too much.

I would like to suggest a way out of the current stale-mate, as it would be a
pitty to loose a potentially active volunteer for Fedora. Clearly the problem
isn't lack of involvement or not investing enough time, so I believe we should
be able to work this out.

Here is what I suggest:
-update your swish-e package to build and work properly under Fedora Core 5, 
 keeping all the packaging and reviewing guidelines into account.
-start a new review ticket for swish-e, or if swish-e has dependencies not yet 
 in FE-5 for one of those depencies. This current ticket is to cluttered to be
 of any use, put me in the CC for this ticket or mention it here.
-in this new review do _NOT_ keep posting new versions, if there is a new 
 upstream version, or you have some packaging improvements hold these back,
 you're free to incorperate those once your innitial submission is approved. But
 reviewing a target moving as fast as you've been moving in this ticket is 
 nearly impossible.
-wait (a week or so) for a full review to be done, a full review can be 
 recognised by the reviewer assigning the bug to him, changing the blocker bug 
 to FE-REVIEW and by a long list of MUST items being checked of one by one.
-this full review will probably contain a few must-fix and should-fix items,
 fix these (and only these, otherwise we have to start over again!) and post
 a new version.
-usually after one iteration, but sometimes more of must-fix -> new release your
 package will get approved and you are free to import and build it.
-After the initial version is approved, you're free to make improvements, but 
 you should still stick to all the guidelines, you no longer need a review for
 each new release.

I hope this can get things moving forward and welcome to the FE community!

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.