launchpad-dev team mailing list archive

["Francis J. Lacoste" <francis.lacoste@xxxxxxxxxxxxx>]

Hi,

Launchpad is a huge code base and there are changes that have ripples across 
the whole application.

Everyone have decent amount of work queued up in front of them.

Given the above, when making a change that will ripple across the code base 
let's adopt the following behaviour:

1- Consider going all the way and making the ripple changes across all 
applications, disregarding your immediate area of responsibility. Down the 
line, we are all Launchpad developpers and in the end responsible for the 
whole application.

   The alternative is to hands off part of the work to others. Hands off are 
bad: they slow completion, and they creates disruption in the flow for the 
other teams.

2- If going all the way is really too much, the next best thing is to notify 
as soon as you find out that it's too much the relevant people (and the 
launchpad-dev list) of the upcoming change and additional work that are 
coming. Being notified once the code is landed is really, really, really too 
late.

For illustration purpose only, two recent examples of rippled changes that 
should happen differently next time:

- New way to handle OOPS in cron scripts
- Refactoring of the build record history


-- 
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx

Attachment: signature.asc
Description: This is a digitally signed message part.