Am 19.07.2013 13:39, schrieb Dirk Müller:
Hi Christian,
submitting a change and I don't want to wait for a review.
This way you're spending my time on figuring out why C:O:M is broken in Jenkins and then need to figure out what you tried to do and fix it properly. This costs me a lot more time than looking at a review and commenting on it. We even work in the same timezone ;-)
Let's not be so harsh. Both you and me also broke Master in the past. I think we're spending far too much time on fixing Jenkins (which translated to fixing openSUSE / SLES issues upstream isn't aware of) rather than developing features. In the past, it was decided to very closely track upstream, which creates much more breakage than Christian (me / you) could ever create.
Is it really a problem to revert or fix commits if you're not satisfied with them?
I consider reverting changes difficult when it is not really obvious what you were trying to fix, besides that it is an obviously rude behavior that I would like to avoid.
I trust you that there is a bug you're facing, and I would appreciate if you'd help me / us understanding how to fix it, especially when the commit is wrong. You're pushing the problem on to me who is _also_ trying to have working packages and test suites that pass, and I consider that not well balanced.
I could argue that you also submit stuff sometimes which isn't obvious or even optimal. I guess if you (me/everybody) would spend more time on providing proper changes entries or a comment / NOTE in the spec file, we all would have to spend less time reasoning about commits of others. However, this wasn't received very well the last time I brought it up, so let's at least try to better notify each other (as Dirk suggests). -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org