* Set version in build/VERSION file
* Add release blog post
* Update versions and automatic blog post content
* Update blog post author
* Fix blog post content
---------
Co-authored-by: rm3l <rm3l@users.noreply.github.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update blog post
---------
Co-authored-by: feloy <feloy@users.noreply.github.com>
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update release blog content
---------
Co-authored-by: rm3l <rm3l@users.noreply.github.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update release doc
---------
Co-authored-by: feloy <feloy@users.noreply.github.com>
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Fix order of "Using Helm with odo" blog post when there is no Git history
This was the case when running developing on the website with `odo dev`
* Update release blog post content
* Apply suggestions from code review
Co-authored-by: Philippe Martin <phmartin@redhat.com>
---------
Co-authored-by: rm3l <rm3l@users.noreply.github.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update
* Apply suggestions from code review
Co-authored-by: Armel Soro <asoro@redhat.com>
---------
Co-authored-by: feloy <feloy@users.noreply.github.com>
Co-authored-by: Philippe Martin <phmartin@redhat.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update release announcement blog post
---------
Co-authored-by: rm3l <rm3l@users.noreply.github.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update blog post
---------
Co-authored-by: feloy <feloy@users.noreply.github.com>
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update blog post for v3.7.0
---------
Co-authored-by: rm3l <rm3l@users.noreply.github.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update the release blog
Signed-off-by: Parthvi Vala <pvala@redhat.com>
* Update docs/website/blog/2023-01-24-odo-v3.6.0.md
Co-authored-by: Armel Soro <asoro@redhat.com>
* Add note about attributes defined at both the levels
Signed-off-by: Parthvi Vala <pvala@redhat.com>
---------
Signed-off-by: Parthvi Vala <pvala@redhat.com>
Co-authored-by: valaparthvi <valaparthvi@users.noreply.github.com>
Co-authored-by: Parthvi Vala <pvala@redhat.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update blog post
* Update docs/website/blog/2023-01-04-odo-v3.5.0.md
Co-authored-by: Armel Soro <asoro@redhat.com>
* Update docs/website/blog/2023-01-04-odo-v3.5.0.md
Co-authored-by: Armel Soro <asoro@redhat.com>
* Apply suggestions from code review
Co-authored-by: Parthvi Vala <pvala@redhat.com>
Co-authored-by: feloy <feloy@users.noreply.github.com>
Co-authored-by: Philippe Martin <phmartin@redhat.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
Co-authored-by: Parthvi Vala <pvala@redhat.com>
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update blog post
* Reorganize items from generated changelog output
This sheds light on items that are relevant for end-users
Co-authored-by: Philippe Martin <phmartin@redhat.com>
Co-authored-by: rm3l <rm3l@users.noreply.github.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Use latest 2.5.1 as label for v2 docs
* Update version to 3.0.0 in installation docs
* Mark 3.0.0 as stable in Docusaurus config
* Update build/VERSION to latest stable: 3.0.0
This allows odo users to get notified of a newer release available
**What type of PR is this?**
> Uncomment only one ` /kind` line, and delete the rest.
> For example, `> /kind bug` would simply become: `/kind bug`
/kind code-refactoring
**What does does this PR do / why we need it**:
Updates the build version to 2.0.1 to coincide with the release
**Which issue(s) this PR fixes**:
N/A
**PR acceptance criteria**:
- [ ] Unit test
- [ ] Integration test
- [ ] Documentation
- [ ] I have read the [test guidelines](https://github.com/openshift/odo/blob/master/docs/dev/test-architecture.adoc)
**How to test changes / Special notes to the reviewer**:
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
**What type of PR is this?**
> Uncomment only one ` /kind` line, and delete the rest.
> For example, `> /kind bug` would simply become: `/kind bug`
/kind feature
**What does does this PR do / why we need it**:
2.0.0 has gone out. This updates the build version to 2.0.0
**Which issue(s) this PR fixes**:
N/A
**PR acceptance criteria**:
N/A
**How to test changes / Special notes to the reviewer**:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
**What type of PR is this?**
> Uncomment only one ` /kind` line, and delete the rest.
> For example, `> /kind bug` would simply become: `/kind bug`
/kind feature
**What does does this PR do / why we need it**:
Updates the build version to 1.2.4
**Which issue(s) this PR fixes**:
N/A
**PR acceptance criteria**:
N/A
**How to test changes / Special notes to the reviewer**:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
**What type of PR is this?**
> Uncomment only one ` /kind` line, and delete the rest.
> For example, `> /kind bug` would simply become: `/kind bug`
/kind feature
**What does does this PR do / why we need it**:
Updates the build version to 1.2.2
**Which issue(s) this PR fixes**:
N/A
**How to test changes / Special notes to the reviewer**:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
**What type of PR is this?**
> Uncomment only one ` /kind` line, and delete the rest.
> For example, `> /kind bug` would simply become: `/kind bug`
/kind feature
**What does does this PR do / why we need it**:
Updates the build version to 1.2.0
**Which issue(s) this PR fixes**:
N/A
**How to test changes / Special notes to the reviewer**:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
**What type of PR is this?**
> Uncomment only one ` /kind` line, and delete the rest.
> For example, `> /kind bug` would simply become: `/kind bug`
/kind feature
**What does does this PR do / why we need it**:
Updates the build number to 1.1.2
**Which issue(s) this PR fixes**:
N/A
**How to test changes / Special notes to the reviewer**:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
**What type of PR is this?**
> Uncomment only one ` /kind <>` line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind feature
**What does does this PR do / why we need it**:
Updates the build to 1.1.1 for the release
**Which issue(s) this PR fixes**:
N/A
**How to test changes / Special notes to the reviewer**:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
**What kind of PR is this?**
<!--
DELETE the kind(s) which are not applicable before opening the PR.
-->
/kind enhancement
**What does does this PR do / why we need it**:
Updates the build version to 1.0.2
**Which issue(s) this PR fixes**:
N/A
**How to test changes / Special notes to the reviewer**:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
**What kind of PR is this?**
<!--
DELETE the kind(s) which are not applicable before opening the PR.
-->
/kind feature
**What does does this PR do / why we need it**:
Updates the build version to 1.0.1
**Which issue(s) this PR fixes**:
N/A
**How to test changes / Special notes to the reviewer**:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
