updates-testing notification changes

[Luke Macken]

As decided during last weeks QA meeting[0], bodhi will no longer spam
fedora-test-list with updates-testing notifications.

Bodhi now has RSS feeds that support querying updates using any combination
of release, status, or type:

   
https://admin.fedoraproject.org/updates/rss/rss2.0?status={pending,testin...

If you want to see a list of updates-testing packages that you have
installed on your local system, install the bodhi-client[1] package and run
`bodhi --testable`.  From here, your testing feedback is encouraged and
will help ensure that we don't push any broken packages out to our users.

I also added support for anonymous access and feedback, so discussions about
test updates can now be held inside of bodhi.  At the moment, anonymous
feedback is able to effect an updates karma.  This is subject to
changing in the future, so if anyone notices this feature getting
abused, please let me know.

        http://bodhi.fedoraproject.org

luke

[0]: http://fedoraproject.org/wiki/QA/Meetings/20071114
[1]: https://hosted.fedoraproject.org/projects/bodhi/wiki/CLI

[Rahul Sundaram]

Luke Macken wrote:
>  As decided during last weeks QA meeting[0], bodhi will no longer
> spam
>  fedora-test-list with updates-testing notifications.
>  
>  Bodhi now has RSS feeds that support querying updates using any combination
>  of release, status, or type:
>  
>     
> https://admin.fedoraproject.org/updates/rss/rss2.0?status={pending,testin...
>  
>  If you want to see a list of updates-testing packages that you have
>  installed on your local system, install the bodhi-client[1] package and run
>  `bodhi --testable`.  From here, your testing feedback is encouraged and
>  will help ensure that we don't push any broken packages out to our users.
>  
>  I also added support for anonymous access and feedback, so discussions about
>  test updates can now be held inside of bodhi.  At the moment, anonymous
>  feedback is able to effect an updates karma.  This is subject to
>  changing in the future, so if anyone notices this feature getting
>  abused, please let me know.
>  
>          http://bodhi.fedoraproject.org 
Is there anything I can do to get a list of test update announcements as 
email as has been happening so far?

Rahul

[Gilbert Sebenste]

On Wed, 28 Nov 2007, Rahul Sundaram wrote:

>  Luke Macken wrote:
> > As decided during last weeks QA meeting[0], bodhi will no longer spam
> > fedora-test-list with updates-testing notifications.
>
>  Is there anything I can do to get a list of test update announcements as 
>  email as has been happening so far? 
I second that one!

*******************************************************************************
Gilbert Sebenste                                                     ********
(My opinions only!)                                                  ******
*******************************************************************************

[Luke Macken]

On Wed, Nov 28, 2007 at 12:37:45PM -0600, Gilbert Sebenste wrote:
>  On Wed, 28 Nov 2007, Rahul Sundaram wrote:
>
> > Luke Macken wrote:
> >> As decided during last weeks QA meeting[0], bodhi will no longer spam
> >> fedora-test-list with updates-testing notifications.
> >
> > Is there anything I can do to get a list of test update announcements as 
> > email as has been happening so far?
>
>  I second that one! 
I'll see what I can do about getting a digest of push updates sent out,
similar to the rawhide report.

luke

[Luke Macken]

On Wed, Nov 28, 2007 at 02:25:44PM -0500, Luke Macken wrote:
>  On Wed, Nov 28, 2007 at 12:37:45PM -0600, Gilbert Sebenste wrote:
>  > On Wed, 28 Nov 2007, Rahul Sundaram wrote:
>  >
>  >> Luke Macken wrote:
>  >>> As decided during last weeks QA meeting[0], bodhi will no longer spam
>  >>> fedora-test-list with updates-testing notifications.
>  >>
>  >> Is there anything I can do to get a list of test update announcements as 
>  >> email as has been happening so far?
>  >
>  > I second that one!
>  
>  I'll see what I can do about getting a digest of push updates sent out,
>  similar to the rawhide report. 
I implemented this in changeset 15cff3005c0b[0].  It will send a single mail
with the string representations of all of the latest testing updates
after each push.  They'll look different than the normal update notices;
if you guys don't like them, let me know and I can generate the other
ones instead.

This code path isn't exactly the easiest to test, so I updated our
production instance with it.  We'll see if it works during the next push
;)

comments/suggests welcome!

luke

[0]: http://hg.fedoraproject.org/hg/hosted/bodhi?cs=15cff3005c0b

[Michael Schwendt]

On Wed, 28 Nov 2007 16:09:10 -0500, Luke Macken wrote:

>  > I'll see what I can do about getting a digest of push
> updates sent out,
>  > similar to the rawhide report.
>  
>  I implemented this in changeset 15cff3005c0b[0].  It will send a single mail
>  with the string representations of all of the latest testing updates
>  after each push.  They'll look different than the normal update notices;
>  if you guys don't like them, let me know and I can generate the other
>  ones instead.
>  
>  This code path isn't exactly the easiest to test, so I updated our
>  production instance with it.  We'll see if it works during the next push
>  ;)
>  
>  comments/suggests welcome! 
No spec changelog diffs?

If you cannot use treediff (as used in the rawhide report) because of
disk space constraints, it should still be possible to it similarly as
in the Extras build report (which maintains a history of src.rpm
changelogs in a small database in order to generate the diffs).

[Luke Macken]

On Wed, Nov 28, 2007 at 10:26:10PM +0100, Michael Schwendt wrote:
>  On Wed, 28 Nov 2007 16:09:10 -0500, Luke Macken wrote:
>  
>  > > I'll see what I can do about getting a digest of push updates sent out,
>  > > similar to the rawhide report.
>  > 
>  > I implemented this in changeset 15cff3005c0b[0].  It will send a single mail
>  > with the string representations of all of the latest testing updates
>  > after each push.  They'll look different than the normal update notices;
>  > if you guys don't like them, let me know and I can generate the other
>  > ones instead.
>  > 
>  > This code path isn't exactly the easiest to test, so I updated our
>  > production instance with it.  We'll see if it works during the next push
>  > ;)
>  > 
>  > comments/suggests welcome!
>  
>  No spec changelog diffs?
>  
>  If you cannot use treediff (as used in the rawhide report) because of
>  disk space constraints, it should still be possible to it similarly as
>  in the Extras build report (which maintains a history of src.rpm
>  changelogs in a small database in order to generate the diffs). 
Good call, changelogs are pretty crucial.
I switched it back to producing a single digest of our normal
update-notices until I find a better way of doing it.

luke