Hello dear Pharo community, I'm looking for fogbugz issues where a slice that was ready to be integrated became outdated because of other issues that were integrated before. In other words: the author of a slice writes it in Pharo-30XXX. Then, a responsible of integration wants to merge it in a Pharo-30YYY (where YYY > XXX), and the slice is rejected because it is old. Note: the reason of rejection can be a merge conflict, but I'm particularly interested in more subtle cases, where the reason was not that clear. Regards, MartÃn
On Tue, Jun 17, 2014 at 3:39 PM, Martin Dias <tinchodias@gmail.com> wrote:
Hello dear Pharo community,
I'm looking for fogbugz issues where a slice that was ready to be integrated became outdated because of other issues that were integrated before.
In other words: the author of a slice writes it in Pharo-30XXX. Then, a responsible of integration wants to merge it in a Pharo-30YYY (where YYY > XXX), and the slice is rejected because it is old.
Note: the reason of rejection can be a merge conflict, but I'm particularly interested in more subtle cases, where the reason was not that clear.
Regards, MartÃn
Clara found a possible sample: https://code.google.com/p/pharo/issues/detail?id=6621 The integration was delayed because slice was written to fix an old version of Nautilus. Thanks Clara
participants (1)
-
Martin Dias