launchpad-dev team mailing list archive

[Michael Nelson <michael.nelson@xxxxxxxxxxxxx>]

On Wed, Jan 27, 2010 at 5:12 AM, Tim Penhey <tim.penhey@xxxxxxxxxxxxx> wrote:
> Hi Julian,
>
> I'm trying to work out which bits need to be worked on next, at least from the
> code-team point of view.
>
> You mentioned that Michael Nelson is going to be doing some initial use case
> work feeding in to some mock-ups.

Hi Tim, I've just started looking at this today... so far I've just
created a dia diagram of the recipe tables at:

https://dev.launchpad.net/BuildBranchToArchive#Current%20db-devel%20schema

in an effort to help me understand any restrictions and/or
possibilities provided by the current schema.

I've also started some very early drafting of the UI design goals and
use cases at:

https://dev.launchpad.net/BuildBranchToArchiveUI

I'm planning to call jml tomorrow which will hopefully clarify a few
things in my head :), and I'll be sending out a request for comments
here to the dev list once I've better understood the issues, but feel
free to correct or add to the above now :)

>
> What do you see as the first use case?  We tend to think of "user wants to
> create a daily build of package x".  How are we wanting to present this to the
> user?  I guess this is part of what Michael will be looking at.

So the three that I've added at the moment are:
1. Manual build of the latest branch revision (opportunistic programmer)
2. Manual build of a specific branch revision (eg. for beta releases),
and of course,
3. Daily builds

>
> Are there any other infrastructural things that we are blocked on?  Is it now
> just workflow and UI work?

In addition to the remaining work that Julian mentioned, I think we
also need to:

* create the SPRBuild manifest (I don't think this is being done
currently, but I haven't checked thoroughly, ie, the SPRData and
Instructions related to the SPRBuild in the schema diagram).
* Additionally, we may want to do the above step *before* running the
build and then pass the manifests recipe text to the buildd slave
instead (currently
lp.soyuz.recipebuilder.RecipeBuilder._extraBuildArgs() is passing the
SPRecipe.builder_recipe as the recipe text).
* Decide on, implement and use the SPRBuildUpload content class (or
remove the table moving its attributes to SPRBuild).

Also, I'm guessing from past experience that as we flesh out the UI
we'll discover further infrastructure needs that we didn't think of
before considering the UI in detail - all part of the fun!

-Michael


>
> Tim
>
> _______________________________________________
> Mailing list: https://launchpad.net/~launchpad-dev
> Post to     : launchpad-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~launchpad-dev
> More help   : https://help.launchpad.net/ListHelp
>