[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#356826: PTS: could e-mail when DEHS detects new upstream release



On 22/01/08 at 08:13 +0100, Raphael Hertzog wrote:
> On Mon, 21 Jan 2008, Raphael Geissert wrote:
> > > PTS could e-mail whenever DEHS detects a new upstream release of the
> > > package being monitored by a watch file.  This would be particularly
> > > usefull in case where upstream packages don't have a mailing list to
> > > notify interested parties of new releases.
> > 
> > This has been partially implemented in the DEHS backend, what's left now is to 
> > make the backend store a list of upstream versions for which a notification 
> > was sent and to make the PTS deliver the messages.
> > 
> > I'm explicitly CC'ing owner@packages.qa.d.o to see how this can be done 
> > (adding the 'newversion' tag/keyword to the PTS and making a default:off).
> 
> I'm not sure it's really worth a new tag but on the other hand I'm not
> sure which actual tag to use. summary could probably be used.

Yes, summary sounds good.

> But for me, ideally this should be filing bugs about new upstream versions
> not sending mails to the PTS because we really want to inform the
> maintainer and not only the followers. I'm sure using a usertag to track
> them and combining this with some regexp to detect bugs manually filed
> with some common subject ("New upstream version") would work quite well.
> And if the code runs often enough, it will probably be the first to submit
> a bug about a new upstream version in most cases.

I'd don't really like the idea of filing wishlist bugs automatically.
"new upstream version" bugs sometimes have more value than an automated
ping, because it provides a point of contact if the maintainer need to
ask why he should really update his package (instead of saying "let's
release with this version", for example).
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |



Reply to: