Hey all,
I've tagged a new release for the-new-hotness, 0.8.0. There's not yet an SOP for the-new-hotness so I'll be writing that along the way as I deploy it in the next few days.
The changelog is included below:
0.8.0 ----- - rebase-helper has been removed from the-new-hotness. For a detailed discussion that lead to this decision, see issue #145.
- the-new-hotness now integrates with mdapi to determine the latest available versions of packages rather than repoquery. This fixes a bug where the-new-hotness would report that the latest rawhide build was the build in EPEL 7 (Issue #98)
- The ``userstring`` setting has been replaced by a ``user_email`` setting. This setting is tuple in the form ('User Name', '<email address>').
- Several configuration URLs have been updated to use HTTPS
- Log entries are now emitted with their full Python path included so debugging is easier.
- the-new-hotness now authenticates with Koji using Kerberos
On Tue, 31 Jan 2017 09:49:37 -0500 Jeremy Cline jeremy@jcline.org wrote:
Hey all,
I've tagged a new release for the-new-hotness, 0.8.0. There's not yet an SOP for the-new-hotness so I'll be writing that along the way as I deploy it in the next few days.
The changelog is included below:
0.8.0
rebase-helper has been removed from the-new-hotness. For a detailed discussion that lead to this decision, see issue #145.
the-new-hotness now integrates with mdapi to determine the latest
available versions of packages rather than repoquery. This fixes a bug where the-new-hotness would report that the latest rawhide build was the build in EPEL 7 (Issue #98)
- The ``userstring`` setting has been replaced by a ``user_email``
setting. This setting is tuple in the form ('User Name', '<email address>').
Several configuration URLs have been updated to use HTTPS
Log entries are now emitted with their full Python path included so
debugging is easier.
- the-new-hotness now authenticates with Koji using Kerberos
Nice. Do you need privs to deploy it or would you like me to deploy it or is it already deployed? ;)
kevin
On 01/31/2017 12:38 PM, Kevin Fenzi wrote:
On Tue, 31 Jan 2017 09:49:37 -0500 Jeremy Cline jeremy@jcline.org wrote:
Hey all,
I've tagged a new release for the-new-hotness, 0.8.0. There's not yet an SOP for the-new-hotness so I'll be writing that along the way as I deploy it in the next few days.
The changelog is included below:
0.8.0
rebase-helper has been removed from the-new-hotness. For a detailed discussion that lead to this decision, see issue #145.
the-new-hotness now integrates with mdapi to determine the latest
available versions of packages rather than repoquery. This fixes a bug where the-new-hotness would report that the latest rawhide build was the build in EPEL 7 (Issue #98)
- The ``userstring`` setting has been replaced by a ``user_email``
setting. This setting is tuple in the form ('User Name', '<email address>').
Several configuration URLs have been updated to use HTTPS
Log entries are now emitted with their full Python path included so
debugging is easier.
- the-new-hotness now authenticates with Koji using Kerberos
Nice. Do you need privs to deploy it or would you like me to deploy it or is it already deployed? ;)
kevin
It's not deployed yet. I don't think I currently have the privileges to deploy it and I eventually I will need those, but a little hand-holding the first time would be very much appreciated.
On 01/31/2017 09:49 AM, Jeremy Cline wrote:
Hey all,
I've tagged a new release for the-new-hotness, 0.8.0. There's not yet an SOP for the-new-hotness so I'll be writing that along the way as I deploy it in the next few days.
The changelog is included below:
0.8.0
rebase-helper has been removed from the-new-hotness. For a detailed discussion that lead to this decision, see issue #145.
the-new-hotness now integrates with mdapi to determine the latest
available versions of packages rather than repoquery. This fixes a bug where the-new-hotness would report that the latest rawhide build was the build in EPEL 7 (Issue #98)
The ``userstring`` setting has been replaced by a ``user_email`` setting. This setting is tuple in the form ('User Name', '<email address>').
Several configuration URLs have been updated to use HTTPS
Log entries are now emitted with their full Python path included so
debugging is easier.
- the-new-hotness now authenticates with Koji using Kerberos
the-new-hotness-0.8.0 is now deployed to staging, thanks in large part to Kevin. If things go well I'll push it to production in a few days!
Hey all,
the-new-hotness-0.8.0 is now in production!
On 01/31/2017 02:49 PM, Jeremy Cline wrote:
Hey all,
I've tagged a new release for the-new-hotness, 0.8.0. There's not yet an SOP for the-new-hotness so I'll be writing that along the way as I deploy it in the next few days.
The changelog is included below:
0.8.0
rebase-helper has been removed from the-new-hotness. For a detailed discussion that lead to this decision, see issue #145.
the-new-hotness now integrates with mdapi to determine the latest
available versions of packages rather than repoquery. This fixes a bug where the-new-hotness would report that the latest rawhide build was the build in EPEL 7 (Issue #98)
The ``userstring`` setting has been replaced by a ``user_email`` setting. This setting is tuple in the form ('User Name', '<email address>').
Several configuration URLs have been updated to use HTTPS
Log entries are now emitted with their full Python path included so
debugging is easier.
- the-new-hotness now authenticates with Koji using Kerberos
On Tue, 14 Feb 2017 11:32:17 +0000 Jeremy Cline jeremy@jcline.org wrote:
Hey all,
the-new-hotness-0.8.0 is now in production!
Awesome. Thanks for getting this deployed.
kevin
infrastructure@lists.fedoraproject.org
-
Jeremy Cline -
Kevin Fenzi