Hello All,
I've prepared a release for v2.2.0-RC5
The vote is open for at least 72 hours and passes if a majority of at least
3 +1 PPMC votes are cast.
[ ] +1 Approve the release
[ ] -1 Do not release this package because ...
Changes since 2.1.0:
I think they should be nuked.
Rgds,
JvD
> On May 1, 2018, at 2:04 PM, Dewayne Richardson wrote:
>
> I'm beginning to evaluate the Perl cleanup effort and noticed that the
> *job_agent*, *job_status*, and *job_result* are minimally used (except for
> the "job" table which
I'm beginning to evaluate the Perl cleanup effort and noticed that the
*job_agent*, *job_status*, and *job_result* are minimally used (except for
the "job" table which has the list of Purge Jobs"). I wanted to get a feel
for the usage outside of Comcast and what the sentiment is to those tables
@Dew - we did not touch job_result table. Thanks, -Hongfei
On 5/1/18, 5:03 PM, "Dewayne Richardson" wrote:
@Hongfei
What about the "job_result" table? It doesn't seem to be used at all.
- Dew
On Tue, May 1, 2018 at 2:47 PM, Hongfei Zhang
@Hongfei
What about the "job_result" table? It doesn't seem to be used at all.
- Dew
On Tue, May 1, 2018 at 2:47 PM, Hongfei Zhang (hongfezh) wrote:
> Hi Dew/Jan,
>
> We made some minor changes in content invalidation which were using
> Job/Status - specifically we:
> 1.
I am +1 on moving it to our website. We can have GitHub link to it from
there.
On Mon, Apr 30, 2018 at 13:07 Hank Beatty wrote:
> I was considering adding a News page that would have a link in the top
> menu (HOME INFO DOCS ISSUES NEWS ...) when I was
> release manager.
>
>