Aloha Michał, Do you have a bug fix you are most proud of? (like it was super difficult to fix or most enlightening)
For my second question let me place you in a scenario. It is only a couple of days to release. A new Amarok version gets released to packagers (i.e. only in a few days to the public) which promises a vast amount of improvements in every possible area of software quality (reliability, speed, user experience...). Upstream urges us to include it in the new release as it carries a considerable amount of vital fixes. Currently the archive holds a not too old git snapshot of Amarok and in fact we have seen a number of critical bugs, so those issues likely got fixed in between the snapshot and the final tagging. However there has been a number of branch merges upstream so that the codebase got changed a lot between our snapshot and the release essentially disqualifying cherry-picking. There is a freeze exception standing for Amarok. No other Kubuntu developer is around as everyone is at Riddell's, attending a wibbly wobbly timey wimey party. Due to the closeness to release you need to make a decisions ASAP. What do you do and how do you reason your decision? -- kubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
