On 05/31/2012 12:14 PM, Stefan Rossbach wrote:
> Norman how the hell it was possible to commit this change ?
>
> See: http://saros-build.imp.fu-berlin.de/gerrit/#/c/107/
>
> This patch requires another patch.
Hell, is certainly not the right word. The big question is how we want to
handle this from a process point of view.
Who should submit changes? E.g. for the release branch it should be the RM,
what about the development branch? Everyone with submit rights should submit
their own changes?
How to handle dependencies? Right now the system is configured to use
cherry-pick, while having many advantages, it does allow the user to
cherry-pick a change that has dependencies.
I really like the cherry-pick as it is allows to include changes that are
ready even if the entire chain of changes has not been approved. E.g. if I
address findbug warnings and create one commit per warning, I am not blocked
because one of the patches is not ready yet.
my two cents here, there is not much to change right now.
holger
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dpp-devel mailing list
Dpp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
