https://bugzilla.redhat.com/show_bug.cgi?id=1908526
Fabrice Bauzac-Stehly <noon(a)mykolab.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(noon(a)mykolab.com) |
--- Comment #20 from Fabrice Bauzac-Stehly <noon(a)mykolab.com> ---
Concerning the submission to rawhide, looking at step 12 of
https://fedoraproject.org/wiki/New_package_process_for_existing_contributors ,
I am not clear which Resolution I should choose for the closure of a bug such
as this one. I have chosen Resolution: RAWHIDE, but Resolution: NEXTRELEASE
seems just as good, I'm unsure about the difference. Maybe I haven't yet
stumbled upon the doc that explains it.
I'm currently trying to learn a lot about the updates system and procedures and
bodhi and so on, which I'm not familiar with.
To submit an update for f34 or f33, it looks like I have to prepare a test case
that will allow testers to try and see that python-opentracing works, correct?
It might be quite involving, users would have to spawn a container with a
jaegertracing server, run some test Python program and see things happening in
the jaegertracing web UI... This might take some time until I can finally
submit updates for f33/f34 or even epel8.
When you say that I can associate the updates with bugs, do you mean with this
bug? Or should I create new bugs, one for each update?
I didn't know about anitya, it looks neat, it reminds me of debian's
"uscan"
facility but with a web UI.
Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component