Skip to content

Commit

Permalink
Make release 3.2.35.
Browse files Browse the repository at this point in the history
Major changes:
* Fix Hessian eigenvalue calculation in FeatureStack.
* Fix bug from issue #63.
  • Loading branch information
iarganda committed Jun 30, 2021
1 parent b3cef13 commit 5c58f96
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@

<groupId>sc.fiji</groupId>
<artifactId>Trainable_Segmentation</artifactId>
<version>3.2.35-SNAPSHOT</version>
<version>3.2.35</version>

This comment has been minimized.

Copy link
@imagejan

imagejan Jun 30, 2021

Member

@iarganda please don't use "double-push to master" any more to release new versions. We have release-version.sh since a long time now, and it's perfectly maintained by @ctrueden and @hinerm.

(Note that due to travis-ci.org having stopped their service, there was no CI build and hence no deployment of the jar file to maven.scijava.org)

This comment has been minimized.

Copy link
@iarganda

iarganda Jun 30, 2021

Author Collaborator

Sorry about that, @imagejan. I knew about this but I have never done it so I went with the old-school way. What am I supposed to do? Do you have step-by-step instructions for an old-fashion guy like me?

This comment has been minimized.

Copy link
@ctrueden

ctrueden Jun 30, 2021

Member

This comment has been minimized.

Copy link
@ctrueden

ctrueden Jun 30, 2021

Member

Unfortunately, it won't work until we migrate the CI from travis-ci.org to GitHub Actions, due to travis-ci.org's recent discontinuation. @hinerm is actively working on mass migrating repositories in the core orgs (fiji, imagej, scijava, imglib2, scifio) starting today. (Neither will double-push-to-master work anymore, unless you manually deploy the release build yourself.)

This comment has been minimized.

Copy link
@iarganda

iarganda Jun 30, 2021

Author Collaborator

Thanks a lot @ctrueden and @imagejan, and sorry again for the inconvenience! What can I do now? Should I reverse the commits and do it again the proper way?

This comment has been minimized.

Copy link
@imagejan

imagejan Jul 1, 2021

Member

@iarganda no need to revert, let's wait until the migration to GitHub Actions is complete, then you can release a new version again using release-version.sh


<name>Trainable Segmentation</name>
<description>Trainable Segmentation plugin for Fiji.</description>
Expand Down

0 comments on commit 5c58f96

Please sign in to comment.