|
1 | 1 | <!-- |
2 | | -
|
3 | 2 | Licensed to the Apache Software Foundation (ASF) under one |
4 | 3 | or more contributor license agreements. See the NOTICE file |
5 | 4 | distributed with this work for additional information |
|
8 | 7 | "License"); you may not use this file except in compliance |
9 | 8 | with the License. You may obtain a copy of the License at |
10 | 9 |
|
11 | | - http://www.apache.org/licenses/LICENSE-2.0 |
| 10 | + http://www.apache.org/licenses/LICENSE-2.0 |
12 | 11 |
|
13 | 12 | Unless required by applicable law or agreed to in writing, |
14 | 13 | software distributed under the License is distributed on an |
15 | 14 | "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
16 | 15 | KIND, either express or implied. See the License for the |
17 | 16 | specific language governing permissions and limitations |
18 | 17 | under the License. |
19 | | -
|
20 | 18 | --> |
21 | 19 | # TinkerPop Upgrade Risk Assessment Guide |
22 | 20 |
|
23 | 21 | Upgrading to TinkerPop versions can sometimes be a challenging process depending on the scope of changes for a |
24 | 22 | particular version and the size and complexity of a particular codebase being upgraded. While TinkerPop provides Upgrade |
25 | 23 | Documentation which outlines all the changes introduced, that still leaves the reader with the heavy job of determining |
26 | 24 | where in their codebase the changes will need to be applied. TinkerPop provides a purpose-built prompt designed for use |
27 | | -with advanced coding agents, such as Claude, GitHub Copilot, or Amazon Q Developer, which can intelligently analyze your |
28 | | -project for areas that may break or behave unexpectedly after the upgrade. Leveraging AI, minimizes time spent on manual |
29 | | -review, reduces the likelihood of missing subtle incompatibilities, and provides actionable advice for adapting existing |
30 | | -code to the new version. This approach enables upgrades with greater confidence, efficiency, and accuracy, ensuring that |
31 | | -all significant compatibility issues are surfaced and addressed early in the migration process. |
| 25 | +with advanced coding agents, such as Claude, GitHub Copilot, or Kiro, which can intelligently analyze your project for |
| 26 | +areas that may break or behave unexpectedly after the upgrade. Leveraging AI minimizes time spent on manual review, |
| 27 | +reduces the likelihood of missing subtle incompatibilities, and provides actionable advice for adapting existing code to |
| 28 | +the new version. This approach enables upgrades with greater confidence, efficiency, and accuracy, ensuring that all |
| 29 | +significant compatibility issues are surfaced and addressed early in the migration process. |
32 | 30 |
|
33 | 31 | This directory contains tools and testing to help build this release version-specific prompt and has the following |
34 | 32 | structure: |
|
0 commit comments