On 22/01/2008, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> On Mon, 21 Jan 2008, Raphael Geissert wrote:
> >
> > 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 [EMAIL PROTECTED] 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.
I asked about adding a new tag because summary is by default sent to
the maintainer unless I've never really payed too much attention and
the testing migration email is sent to both, the maintainer and the
PTS.
When discussing about this topic with several people some have asked
me not to make the PTS send the notifications by default. And for the
sake of simplicity I think it is far easier to use the PTS'
subscription system with a new tag and let then decide whether to make
it the default or not.
>
> 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.
With the current design DEHS would email the PTS immediately after it
finds a new upstream version.
As others have expressed their concern, I don't think auto bug filing
is the best way to do this.
>
> Cheers,
> --
> Raphaël Hertzog
>
> Le best-seller français mis à jour pour Debian Etch :
> http://www.ouaza.com/livre/admin-debian/
>
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
Say NO to Microsoft Office broken standard.
See http://www.noooxml.org/petition
