Search results

...ss that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved (this fixes some segfaults seen on i686 (fixed in 0.4), along with numerous other improvements).

...ss that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved ...unding ecosystem, most notably with the addition of the npm (Node-packaged modules) package manager and developing packaging guidelines around it.

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG = Modules for Everyone <!-- The name of your change proposal --> =

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG = Kubernetes modules <!-- The name of your change proposal --> =

<!--{{:Docs/Drafts/AdministrationGuide/Servers/Firewall}} ...owever, to configure more advanced options using this utility, familiarity with the <code>iptables</code> rules syntax is necessary.")]

** It was unclear to me that you're proposing that all package maintainers with programs or libraries in / will need to update their packages to carry the ...when I misunderstood it to only be needing to replace the "/" directories with symlinks into "/usr". Also, your list of 257 packages is incomplete. For

...t we'll probably want to look at the template and try writing a few HOWTOs with it before anyone will have input.. ...t-snmp update.. I have no clue how to set up an snmp server, or what to do with it

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)

...and what has changed. Depending on the beat, it might be helpful to begin with a 'short' synopsis of what is in the beat, but the main thrust should be to ...es a simple note mentioning a new version of a particular package, perhaps with a short description of new features is adequate. For a completely new pack

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...n renamed from '''System Python''' to '''Platform Python''' not to collide with upstream [https://www.python.org/dev/peps/pep-0432/#a-system-python-executa

0:05 < thl> | scop, I'm working on getting fedora-maintainers up2date 0:07 < cweyl> | warren: gotcha. so maintainers-announce, with automated subscription of everyone in the owners list?

| kernel || The Linux kernel || <ul> <li>sctp cookie used when opening a connection uses a HMAC, kernel is configured to use a MD5 HMAC (#485933).

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG = OpenShift modules <!-- The name of your change proposal --> =

* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> ASSIGNED -> accepted by FESCo with on going development

• Add instructions to ensure the future signing of files (kernel postinstall and maybe rpm postinstall (if next point doesn't cover it alrea * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG ...ss that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved.

* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG See same process with JDK8, current main JDK, and JDK7 before.