Skip to content
Snippets Groups Projects
Vicente Bolea's avatar
commented on issue #837 "Release 2.3.0" at VTK / VTK-m

user guide published at: https://vtk-m.readthedocs.io/en/v2.3.0

Vicente Bolea's avatar
closed issue #836 "Release 2.3.0-rc1" at VTK / VTK-m
Vicente Bolea's avatar
pushed new tag v2.3.0 at VTK / VTK-m
Kitware Robot's avatar
accepted merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m
Kitware Robot's avatar
pushed to branch release at VTK / VTK-m
Kitware Robot's avatar
pushed to branch master at VTK / VTK-m
Vicente Bolea's avatar
commented on merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m

There are two stuck test jobs due to a runner failure, the tip of release have already passed these builds and we do not modify source code here....

Kenneth Moreland's avatar
approved merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m
Kenneth Moreland's avatar
commented on merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m

+1

Vicente Bolea's avatar
commented on merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m

@kmorel Ascent is green with the latest release branch :) #836 (comment 1646804)

Vicente Bolea's avatar
commented on issue #836 "Release 2.3.0-rc1" at VTK / VTK-m

Sounds good, thanks! Normally would be the tag, but this time was special since we are ready for another release and by checking the release branch...

Nicole Marsaglia's avatar
commented on issue #836 "Release 2.3.0-rc1" at VTK / VTK-m

@vbolea I did both and both worked. for future reference, which should I have done?

Vicente Bolea's avatar
commented on merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m

As for VTK yes, as for Ascent Nicole reported it today in here #836 (closed), she previously spoke (!3302 (comment 1644877)) that she will test the release ...

Vicente Bolea's avatar
commented on issue #836 "Release 2.3.0-rc1" at VTK / VTK-m

@nicolemarsaglia have you tested against the tag v2.3.0-rc1 or the latest release branch? Thanks!

Kenneth Moreland's avatar
commented on merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m

Are you sure !3305 (merged) was tested? It is not included in the v2.3.0-rc1 tag.

Vicente Bolea's avatar
commented on merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m

My bad, I was referring to !3307 (merged) and !3306 (merged). !3305 (merged) has been tested in both Ascent (!3302 (comment 1644874)) and VTK. !3307 (merged) in VTK only.

Kenneth Moreland's avatar
commented on merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m

Yes, that is our normal procedure but release branch is green in VTK and in Ascent (up the commit before !3305 (merged)). To avoid further stalling the rel...

Vicente Bolea's avatar
commented on merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m

Yes, !3305 (merged) was merged to release since we forgot to add the backport at the original MR !3302 (merged)....

Kenneth Moreland's avatar
commented on merge request !3308 "Branch for the vupdate-to-2.3.0 release" at VTK / VTK-m

Actually, what happened with !3305 (merged)? As I recall, that was merged into master after the cut of 2.3.0-RC1. I was expecting an RC2. Was RC1 just moved...