Hi, > +@python_2_unicode_compatible > +class SeriesRevision(models.Model): > + > + group = models.ForeignKey(Series, related_name='revisions', > + related_query_name='revision', null=True, > + blank=True) > + date = models.DateTimeField() > + submitter = models.ForeignKey(Person) > + version = models.IntegerField(default=1, > + help_text='Version of series revision as ' > + 'indicated by the subject prefix(es)') > + total = models.IntegerField(help_text='Number of patches in series as ' > + 'indicated by the subject prefix(es)') > +
OK, so I've been thinking about this and having some chats around the office. One of the things that keeps coming up in discussions about series support is "What do we call a series?". Currently we look at the cover letter, if present, and then there's been quite a bit of debate about what to do if a cover letter is not present. Personally, I've been thinking about how I remember people talking about series. I remember saying things like "Bob's hotplug series", "Jane's Radix MMU series", "Daniel's sparse patch series" or "Ben's PCI cleanups". I'd quite like patchwork to be able to represent patch series in a way that matches as naturally as possible with how the humans who use Patchwork perceive them. As such, I'd like it if we could name series. And I'd like at least maintainers, or perhaps series authors, etc. to be able to give series names in patchwork. I don't really mind whether this attaches to a Series or to a SeriesRevision. I realise this makes the models a bit more heavy-weight. Thoughts? Regards, Daniel _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
