Fully automating patch state updates

Jeremy Kerr jk at ozlabs.org
Fri Mar 25 19:02:21 EST 2011

Hi Guilherme,

> I've seen the tools/patchwork-update-commits script and I'm planning to
> work on making a fully automated version of it, which fetches the master
> branch, scans the commits on it and updates the state of patches. I think
> this would be a nice addition to Patchwork.
> For that to work, though, the first thing we need is to know where's the
> master branch of a project.  The patch below makes that possible by adding
> a free form char field to store the URL to the project's master branch.
> It's not a URLField because that only allows http[s] URLs, which is not
> what we want.

OK, this makes sense. I'd suggest calling this "source_tree" instead, with the 
intention of using any VCS URL there; "branch" means different things to 
different VCSes.

> I couldn't find anything about how Patchwork deals with DB schema
> migrations, but I wrote a migration script together with the other ones,
> which, AFAICT have to be applied manually?

Yes, they have to be applied manually at the moment. I'll add DB versioning 

> Is there anything I've missed
> or would this be everything that's needed to add a new field to a model
> class?

Yep, you've got it all :)



More information about the Patchwork mailing list