Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2019-07-31 from 10:00:00 to 11:00:00 US/Eastern
The meeting will be about:
Join members of the docs team in #fedora-docs for writing time. This is a great time to focus on writing and talk about challenges and blockers related to producing content.
There is no formal schedule for this meeting. Attendees should show up and use this as a way to block writing time into their week.
Source: https://apps.fedoraproject.org/calendar/meeting/9360/
https://bugzilla.redhat.com/show_bug.cgi?id=1674777
--- Comment #18 from Fedora Release Engineering <releng(a)fedoraproject.org> ---
Dear Maintainer,
your package has not been built successfully in 30. Action is required from
you.
If you can fix your package to build, perform a build in koji, and either
create
an update in bodhi, or close this bug without creating an update, if updating
is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your
package
can be orphaned if this bug remains in NEW state more than 8 weeks.
A week before the mass branching of Fedora 31 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 30 will be retired.
[1] https://fedoraproject.org/wiki/Updates_Policy
[2]
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails…
[3] https://fedoraproject.org/wiki/Releases/31/Schedule
--
You are receiving this mail because:
You are on the CC list for the bug.
Hi All,
Barring objection, I plan to work on removing the release notes
package from Fedora in August. The package has not been updated since
F28. Despite the fact that we have literally shipped a package
containing the F28 release notes in F29 and F30, there have been no
comments.
This leads me to believe we are safe to remove it.
Please reply on list if you have any questions or concerns.
regards,
bex
--
Brian "bex" Exelbierd (he/him/his)
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
bexelbie(a)redhat.com | bex(a)pobox.com
https://bugzilla.redhat.com/show_bug.cgi?id=1674777
--- Comment #17 from Fedora Release Engineering <releng(a)fedoraproject.org> ---
Dear Maintainer,
your package has not been built successfully in 30. Action is required from
you.
If you can fix your package to build, perform a build in koji, and either
create
an update in bodhi, or close this bug without creating an update, if updating
is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your
package
can be orphaned if this bug remains in NEW state more than 8 weeks.
A week before the mass branching of Fedora 31 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 30 will be retired.
[1] https://fedoraproject.org/wiki/Updates_Policy
[2]
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails…
[3] https://fedoraproject.org/wiki/Releases/31/Schedule
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1674777
Fedora Release Engineering <releng(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(jorton(a)redhat.com
| |)
--- Comment #16 from Fedora Release Engineering <releng(a)fedoraproject.org> ---
Dear Maintainer,
your package has not been built successfully in 30. Action is required from
you.
If you can fix your package to build, perform a build in koji, and either
create
an update in bodhi, or close this bug without creating an update, if updating
is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your
package
can be orphaned if this bug remains in NEW state more than 8 weeks.
A week before the mass branching of Fedora 31 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 30 will be retired.
[1] https://fedoraproject.org/wiki/Updates_Policy
[2]
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails…
[3] https://fedoraproject.org/wiki/Releases/31/Schedule
--
You are receiving this mail because:
You are on the CC list for the bug.
Dear all,
You are kindly invited to the meeting:
Docs Writing Hour on 2019-07-24 from 10:00:00 to 11:00:00 US/Eastern
The meeting will be about:
Join members of the docs team in #fedora-docs for writing time. This is a great time to focus on writing and talk about challenges and blockers related to producing content.
There is no formal schedule for this meeting. Attendees should show up and use this as a way to block writing time into their week.
Source: https://apps.fedoraproject.org/calendar/meeting/9360/
https://bugzilla.redhat.com/show_bug.cgi?id=1674777
Petr Bokoc <pbokoc(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pbokoc(a)redhat.com
--- Comment #15 from Petr Bokoc <pbokoc(a)redhat.com> ---
Adam, thanks for tagging us, we'll track the removal in the repo's issues:
https://pagure.io/fedora-docs/system-administrators-guide/issue/35
Joe, a docs update would be definitely appreciated. Let me know if you have any
questions about contributing to our docs; you can reach me by mail (on this
address or on docs(a)lists.fedoraproject.org) or in #fedora-docs on Freenode.
--
You are receiving this mail because:
You are on the CC list for the bug.