flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flink Jira Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-22069) Check Log Pollution for 1.14 release
Date Sun, 27 Jun 2021 22:39:02 GMT

     [ https://issues.apache.org/jira/browse/FLINK-22069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Flink Jira Bot updated FLINK-22069:
    Labels: auto-deprioritized-critical pull-request-available stale-major  (was: auto-deprioritized-critical

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community
manage its development. I see this issues has been marked as Major but is unassigned and neither
itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major"
to the issue". If this ticket is a Major, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be deprioritized.

> Check Log Pollution for 1.14 release
> ------------------------------------
>                 Key: FLINK-22069
>                 URL: https://issues.apache.org/jira/browse/FLINK-22069
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>            Reporter: Stephan Ewen
>            Priority: Major
>              Labels: auto-deprioritized-critical, pull-request-available, stale-major
>             Fix For: 1.14.0
> We should check for log pollution and confusing log lines before the release.

This message was sent by Atlassian Jira

View raw message