Bug#356826: PTS: could e-mail when DEHS detects new upstream release
tag 356826 pending
thanks
On 23/01/2008, Raphael Hertzog <hertzog@debian.org> wrote:
> On Tue, 22 Jan 2008, atomo64@gmail.com wrote:
> > 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.
>
> That's the case: the testing mail is sent both the the maintainer and to
> 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.
>
> Well, the tag mechanism is nice but I definitely don't want to add many
> very-specific keywords until it gets unmanageable. So I won't create a new
> keyword... if you want to send a mail to the PTS send it to the summary
> keyword (you send a mail to
> <srcpkg>_summary@packages.qa.debian.org but in the To: field you only put
> <srcpkg>@packages.debian.org to hide the keyword specific email address).
Ok, I'll change it in my next commit.
>
> > > 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.
>
> Well, maybe the right way is to let some time pass as suggested by Lucas
> and others. Provide the real-time information on the web page, but only
> open a bug when two weeks have elapsed and when the new version is
> neither in unstable nor in experimental.
I will go the "notifying via the PTS" way for now.
I'll also provide the required information for Lucas to also notify
about new upstream releases on his monthly mail.
>
> 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
Reply to: