12 Matching Annotations
  1. Last 7 days
    1. wph-acronis-agent-maintenance --install-latest

      [Upgrade-2] Inappropriate procedure?(Upgrading Acronis agent)

      Background: There are two ways to update Acronis agent.?a)wph-acronis-agent-maintenance --install-latest (Upgrade to the latest agent released by Acronis)?b)wph-acronis-agent-maintenance --install-release (Upgrade to the latest agent supported by WPH) Issue : The IG has instructions to upgrade the agent using method a after upgrading the WPH. ?As a result, the agent is updated to an agent that does not support WPH. Request : Replace with the instruction to upgrade the agent by the method b.

    2. The default backup plans are created with a default schedule and frequency, default backup data retention, and available backup data storage location and encryption.

      [Upgrade-1] misdescription (Default Backup plan)

      Background: The Default Backup plan created by Backup Recovery Assistant is unencrypted. Issue: In the description below, it is incorrect to say that it is encrypted with the Default Backup plan. Action: Delete the relevant part

    1. In the next major, we'll start copying the ref onto both the props and the element.ref. React will now use the props.ref as the source of truth for forwardRef and classes and it will still create a shallow copy of props that excludes the ref in these cases. At the same time, we'll add a getter for element.ref in DEV that warns if you access it. The upgrade path is now to just access it off props if you need it from the element.
    2. The backwards compatible implementation of jsx(...), we would still support key passed as props. We'd just pull it off props and issue a warning that this pattern is deprecated. The upgrade path is to just pass it to JSX separately if you need it.
    3. This would be a breaking change, but we could always clone in the call in a minor and then make the breaking change later in a major.
    4. It's much easier to iterate on new versions by deploying npm packages than updates to the compiler toolchain. Therefore, it might be best if the actual implementation still lives in the react package.
    5. the actual upgrade path should be very simple for most people since the deprecated things are mostly edge cases and any common ones can be codemodded
  2. Sep 2020
  3. Jul 2020
  4. Jul 2018
  5. Feb 2017
    1. select proprietary or out-of-tree modules (ex. vitualbox, nvidia, fglrx, bcmwl, etc.)

      If anyone is wondering what other modules they refer to, or how to discover any on your own system, this StackExchange thread on how to identify out-of-tree modules might help.

  6. Aug 2016
    1. From my car passing under the stars,

      There is definitely progress: the speaker describes 'out of bus ride' on the 2nd stanza but in the 5th last stanza he is cruising, chillin' under the stars in his own car.