On 09/16/2016 12:10 AM, Daniel Axtens wrote:
> 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 re
On 16/09/16 15:10, Daniel Axtens wrote:
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 bee
On Fri, Sep 16, 2016 at 03:10:15PM +1000, Daniel Axtens wrote:
> Hi,
>
> > +@python_2_unicode_compatible
> > +class SeriesRevision(models.Model):
> > +
> > +group = models.ForeignKey(Series, related_name='revisions',
> > + related_query_name='revision', null=True,
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.DateTimeFie
On 13/09/16 07:53, Stephen Finucane wrote:
Add a series model. This model is intentionally very minimal to allow
as much dynaminism as possible. It is expected that patches will be
migrated between series as new data is provided.
Signed-off-by: Stephen Finucane
Co-authored-by: Andrew Donnellan
Add a series model. This model is intentionally very minimal to allow
as much dynaminism as possible. It is expected that patches will be
migrated between series as new data is provided.
Signed-off-by: Stephen Finucane
Co-authored-by: Andrew Donnellan
Reviewed-by: Andy Doan
---
v2:
- Resolve is
