launchpad-dev team mailing list archive

[Jelmer Vernooij <jelmer@xxxxxxxxxxxxx>]

On Wed, 2010-11-17 at 04:54 +1300, Robert Collins wrote:
> So, when I started this role, I put performance and continuous
> deployment - release features when they are done - as my kanban cards.
> These things are where I've been putting all my ongoing-project focus
> (vs day to day stuff like helping with design and code discussions).
> 
> It seems to me that our continuous deployment project is nearly
> complete, and its time to start thinking about what I should take on
> to replace it.
It's great to finally see this happen!

> I've a few candidates already, and I'm interested in what all of you
> think would help you most. Thanks go to Gary who I've already run this
> past.
> 
> The candidates I have already are:
>  - fixing a bunch of baseline issues - like: overuse of interfaces,
> scripts not establishing participations, sqlbase migration. Time
> consuming, tricky things that need some attention to detail, but which
> when done will significantly simplify much of our code base.
These seem to me like they're just separate tech-debt issues, for which
we already have a clear idea of how to exactly to resolve them, but that
we just haven't taken the time for yet. They're very useful to fix, but
I don't think they benefit from attention by the TA as much as the other
items.

>  - test suite parallelisation: parallelisation initially, then
> parallelisation in our CI/landing robot
>  - data mapping layer: Build and deploy across the whole code base a
> dedicated persistence layer.
>    This would be a choke point through which all database access goes,
> would include the group based idiom I've been rabbiting on about, and
> to be successful would define an iron-clad contract which we can
> confidently replace with a testable test double. I'd be looking to
> form a working-group for this - a group of interested folk seconded
> from their regular team to work with me on developing and deploying
> this project wide.
I think these two items would be of most use.

Cheers,

Jelmer

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