Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-26 Thread Carlos Soriano Sanchez
Hi Frederic,

This is useful, thanks!

- Original Message -
| Hi,
| 
| Philip Withnall wrote:
| 
| > On Wed, 2015-11-25 at 11:07 +0100, Frederic Peters wrote:
| > > I'm a bit surprised by 1) but we could certainly automatically
| > > produce
| > > a list of maintainers / modules/ time/commits since last release, if
| > > that could be useful.
| > 
| > I think 1) would be useful because I have a load of modules which I am
| > not sure if they need to follow the main GNOME release schedule. I had
| > a nagging fear they should, but then nobody poked me about doing a
| > release, so I forgot to check up further. As a result, a lot of my
| > modules haven’t had releases following the schedule. (Sorry if I have
| > been a total pain because of this.)
| > 
| > Would such a list be useful for the release team, as a way of tracking
| > who needs nagging? If so, then I hope producing it should not be too
| > much of a drain on your time — if it is a drain, then you probably
| > shouldn’t do it.
| 
| This was mostly done manually (at least as far I am concerned), but
| here is an experiment,
|   https://people.gnome.org/~fpeters/health/wanted-releases.html
| 
| And the red modules are first targets.
| 
| (this has been generated from my local clones, updated a few hours
| ago, if it's something we want to pursue it would be quite nice to
| have this automated and running on GNOME infrastructure) (the disk
| requirements exclude openshift).
| 
| 
| Fred
| 
| [code at https://git.gnome.org/browse/releng/tree/tools/health/]
| ___
| desktop-devel-list mailing list
| desktop-devel-list@gnome.org
| https://mail.gnome.org/mailman/listinfo/desktop-devel-list
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-26 Thread Frederic Peters
Philip Withnall wrote:

> > This was mostly done manually (at least as far I am concerned), but
> > here is an experiment,
> >   https://people.gnome.org/~fpeters/health/wanted-releases.html
> > 
> > And the red modules are first targets.
> > 
> > (this has been generated from my local clones, updated a few hours
> > ago, if it's something we want to pursue it would be quite nice to
> > have this automated and running on GNOME infrastructure) (the disk
> > requirements exclude openshift).
> 
> Nice! If it's not much effort to get this running on GNOME
> infrastructure, I think it would be useful, and have it linked from the
> release reminder e-mails.

Actually I already had https://bugzilla.gnome.org/show_bug.cgi?id=743833
(yeah for bugzilla suggesting duplicates), I added a comment.


> What do the x/y numbers mean?

Numbers are numbers of commits since last tag, first number omits the
translation commits.


Fred
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-26 Thread Philip Withnall
On Wed, 2015-11-25 at 21:40 +0100, Frederic Peters wrote:
> Hi,
> 
> Philip Withnall wrote:
> 
> > On Wed, 2015-11-25 at 11:07 +0100, Frederic Peters wrote:
> > > I'm a bit surprised by 1) but we could certainly automatically
> > > produce
> > > a list of maintainers / modules/ time/commits since last release,
> > > if
> > > that could be useful.
> > 
> > I think 1) would be useful because I have a load of modules which I
> > am
> > not sure if they need to follow the main GNOME release schedule. I
> > had
> > a nagging fear they should, but then nobody poked me about doing a
> > release, so I forgot to check up further. As a result, a lot of my
> > modules haven’t had releases following the schedule. (Sorry if I
> > have
> > been a total pain because of this.)
> > 
> > Would such a list be useful for the release team, as a way of
> > tracking
> > who needs nagging? If so, then I hope producing it should not be
> > too
> > much of a drain on your time — if it is a drain, then you probably
> > shouldn’t do it.
> 
> This was mostly done manually (at least as far I am concerned), but
> here is an experiment,
>   https://people.gnome.org/~fpeters/health/wanted-releases.html
> 
> And the red modules are first targets.
> 
> (this has been generated from my local clones, updated a few hours
> ago, if it's something we want to pursue it would be quite nice to
> have this automated and running on GNOME infrastructure) (the disk
> requirements exclude openshift).

Nice! If it's not much effort to get this running on GNOME
infrastructure, I think it would be useful, and have it linked from the
release reminder e-mails.

What do the x/y numbers mean?

Philip

signature.asc
Description: This is a digitally signed message part
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-25 Thread Frederic Peters
Hi,

Philip Withnall wrote:

> On Wed, 2015-11-25 at 11:07 +0100, Frederic Peters wrote:
> > I'm a bit surprised by 1) but we could certainly automatically
> > produce
> > a list of maintainers / modules/ time/commits since last release, if
> > that could be useful.
> 
> I think 1) would be useful because I have a load of modules which I am
> not sure if they need to follow the main GNOME release schedule. I had
> a nagging fear they should, but then nobody poked me about doing a
> release, so I forgot to check up further. As a result, a lot of my
> modules haven’t had releases following the schedule. (Sorry if I have
> been a total pain because of this.)
> 
> Would such a list be useful for the release team, as a way of tracking
> who needs nagging? If so, then I hope producing it should not be too
> much of a drain on your time — if it is a drain, then you probably
> shouldn’t do it.

This was mostly done manually (at least as far I am concerned), but
here is an experiment,
  https://people.gnome.org/~fpeters/health/wanted-releases.html

And the red modules are first targets.

(this has been generated from my local clones, updated a few hours
ago, if it's something we want to pursue it would be quite nice to
have this automated and running on GNOME infrastructure) (the disk
requirements exclude openshift).


Fred

[code at https://git.gnome.org/browse/releng/tree/tools/health/]
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-25 Thread Milan Crha
On Wed, 2015-11-25 at 10:52 +, Philip Withnall wrote:
> Would such a list be useful for the release team, as a way of
> tracking who needs nagging? If so, then I hope producing it should
> not be too much of a drain on your time — if it is a drain, then you
> probably shouldn’t do it.

Hi,
it would be nice, if anything like this will be implemented, to have
the notifications on the opt-in bases.

I understand the need for maintainers of tons of modules which do not
receive any active development, but for me, whom has only few packages,
would be the notification a simple spam and thus quite annoying thing.
I'm fine the Friday notification about the following Monday release. I
have also setup a calendar notifications about the releases.

Just my opinion on the matter.
Bye,
Milan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-25 Thread Philip Withnall
On Wed, 2015-11-25 at 11:07 +0100, Frederic Peters wrote:
> Bastien Nocera wrote:
> 
> > > It's been some months we have those reminder emails sent to
> > > devel-announce-list.  Maintainers, make sure you are subscribed.
> > > 
> > > Maintainers (bis), please do try to respect the Monday 23:59 UTC
> > > deadline, it's really not fun to chase maintainers for days
> > > during
> > > release weeks.  If you know you will be late, tell us, either by
> > > email
> > > at release-t...@gnome.org or simply by pinging us on #release-
> > > team.
> > 
> > I'd rather somebody helped me 1) know which of my modules need
> > releasing 2) do releases.
> 
> We can of course assist in producing tarballs, just ping us.
> 
> I'm a bit surprised by 1) but we could certainly automatically
> produce
> a list of maintainers / modules/ time/commits since last release, if
> that could be useful.

I think 1) would be useful because I have a load of modules which I am
not sure if they need to follow the main GNOME release schedule. I had
a nagging fear they should, but then nobody poked me about doing a
release, so I forgot to check up further. As a result, a lot of my
modules haven’t had releases following the schedule. (Sorry if I have
been a total pain because of this.)

Would such a list be useful for the release team, as a way of tracking
who needs nagging? If so, then I hope producing it should not be too
much of a drain on your time — if it is a drain, then you probably
shouldn’t do it.

Philip

signature.asc
Description: This is a digitally signed message part
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-25 Thread Frederic Peters
Bastien Nocera wrote:

> > It's been some months we have those reminder emails sent to
> > devel-announce-list.  Maintainers, make sure you are subscribed.
> > 
> > Maintainers (bis), please do try to respect the Monday 23:59 UTC
> > deadline, it's really not fun to chase maintainers for days during
> > release weeks.  If you know you will be late, tell us, either by
> > email
> > at release-t...@gnome.org or simply by pinging us on #release-team.
> 
> I'd rather somebody helped me 1) know which of my modules need
> releasing 2) do releases.

We can of course assist in producing tarballs, just ping us.

I'm a bit surprised by 1) but we could certainly automatically produce
a list of maintainers / modules/ time/commits since last release, if
that could be useful.


Fred
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-25 Thread Bastien Nocera
On Tue, 2015-11-24 at 12:09 +0100, Frederic Peters wrote:
> Hi!
> 
> > Tarballs are due on 2015-11-23 before 23:59 UTC for the GNOME
> > 3.19.2
> > unstable release, which will be delivered on Wednesday. Modules
> > which
> > were proposed for inclusion should try to follow the unstable
> > schedule
> > so everyone can test them.  Please make sure that your tarballs
> > will
> > be uploaded before Monday 23:59 UTC: tarballs uploaded later than
> > that
> > will probably be too late to get in 3.19.2. If you are not able to
> > make a tarball before this deadline or if you think you'll be late,
> > please send a mail to the release team and we'll find someone to
> > roll
> > the tarball for you!
> 
> It's been some months we have those reminder emails sent to
> devel-announce-list.  Maintainers, make sure you are subscribed.
> 
> Maintainers (bis), please do try to respect the Monday 23:59 UTC
> deadline, it's really not fun to chase maintainers for days during
> release weeks.  If you know you will be late, tell us, either by
> email
> at release-t...@gnome.org or simply by pinging us on #release-team.

I'd rather somebody helped me 1) know which of my modules need
releasing 2) do releases.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-24 Thread Frederic Peters
Shaun McCance wrote:

> Question: If I don't intend to make a release because there haven't been
> any changes, do you want me to send an email saying so?

Nope, that's already something we check before chasing people :)

And while it's important to get stable releases out when the only
changes are translation updates it is ok to "ignore" them for (early)
development releases.


Fred
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-24 Thread Shaun McCance
On Tue, 2015-11-24 at 12:09 +0100, Frederic Peters wrote:
> Hi!
> 
> > Tarballs are due on 2015-11-23 before 23:59 UTC for the GNOME 3.19.2
> > unstable release, which will be delivered on Wednesday. Modules which
> > were proposed for inclusion should try to follow the unstable schedule
> > so everyone can test them.  Please make sure that your tarballs will
> > be uploaded before Monday 23:59 UTC: tarballs uploaded later than that
> > will probably be too late to get in 3.19.2. If you are not able to
> > make a tarball before this deadline or if you think you'll be late,
> > please send a mail to the release team and we'll find someone to roll
> > the tarball for you!
> 
> It's been some months we have those reminder emails sent to
> devel-announce-list.  Maintainers, make sure you are subscribed.
> 
> Maintainers (bis), please do try to respect the Monday 23:59 UTC
> deadline, it's really not fun to chase maintainers for days during
> release weeks.  If you know you will be late, tell us, either by email
> at release-t...@gnome.org or simply by pinging us on #release-team.

Question: If I don't intend to make a release because there haven't been
any changes, do you want me to send an email saying so?

--
Shaun


___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Maintainers, please read this. [Re: GNOME 3.19.2 unstable tarballs due]

2015-11-24 Thread Frederic Peters
Hi!

> Tarballs are due on 2015-11-23 before 23:59 UTC for the GNOME 3.19.2
> unstable release, which will be delivered on Wednesday. Modules which
> were proposed for inclusion should try to follow the unstable schedule
> so everyone can test them.  Please make sure that your tarballs will
> be uploaded before Monday 23:59 UTC: tarballs uploaded later than that
> will probably be too late to get in 3.19.2. If you are not able to
> make a tarball before this deadline or if you think you'll be late,
> please send a mail to the release team and we'll find someone to roll
> the tarball for you!

It's been some months we have those reminder emails sent to
devel-announce-list.  Maintainers, make sure you are subscribed.

Maintainers (bis), please do try to respect the Monday 23:59 UTC
deadline, it's really not fun to chase maintainers for days during
release weeks.  If you know you will be late, tell us, either by email
at release-t...@gnome.org or simply by pinging us on #release-team.


Thanks for your attention,

Fred
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list