Skip to content

Commit

Permalink
Merge pull request #167 from Teradata/sunilkmallam-patch-1
Browse files Browse the repository at this point in the history
Update teradata-vantage-editor-faq.mdx
  • Loading branch information
sunilkmallam authored Jan 9, 2025
2 parents 76969c2 + 3014044 commit b568f81
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/pages/teradata-vantage-editor-faq.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -214,9 +214,9 @@ title: Teradata Vantage Editor FAQ
<summary>Will Teradata Studio continue to be supported and enhanced?</summary>

<div>
<p>Teradata Studio is currently supported with no new feature development. As part of the General Availability of Vantage Editor in 2024, Teradata Studio is targeted to be end of life in 2025. An official communication and timelines for Teradata Studio end of life will be formally announced after release of Vantage Editor Desktop (31st May,2024)</p>
<p>Teradata Studio is currently in maintenance mode with no new feature development. As part of the General Availability of Vantage Editor in 2024, Teradata Studio is targeted for end-of-life, however, the sunset plan will give plenty of time for the users to migrate to either Vantage Editor or a 3rd party IDE. An official communication for Teradata Studio’s end-of-life will be formally announced once the timelines are finalized.</p>

<p>Customers and users are encouraged to start to plan transition to Vantage Editor, or a 3rd party tool offering . </p>
<p>Customers and users are encouraged to start planning transition to Vantage Editor or a 3rd party IDE.</p>
</div>
</details>

Expand Down Expand Up @@ -305,7 +305,7 @@ title: Teradata Vantage Editor FAQ
<div>
<p class="space">
<i>
Please contact &nbsp;[Seema Ray](mailto:[email protected]) for any further information.
Please contact &nbsp;[Seema Ray](mailto:[email protected]) or [Sunil Mallam](mailto:[email protected])for any further information.
</i>
</p>
</div>

0 comments on commit b568f81

Please sign in to comment.