1.0 Roadmap

[bw4sz]

@ethanwhite and @henrykironde

We need to create a roadmap that we agree on for how to bring together

DeepForest-pytorch and DeepForest

Let's start by agreeing on the end goal. We want a single repo that holds a main branch that points to pytorch and a tensorflow branch that will have deprecation notice. I'm agnostic to the git history, i'm not sure its worth the time to do a massive effort for bringing the two files under version control. I vote for keeping the pytorch git history and have a clean git history that holds the deprecated tensorflow code.

Specific objectives

• a single readthedocs that points the pytorch instructions at https://deepforest.readthedocs.io/
• a document outline transitioning code from tensorflow to pytorch
• a new release model in this repo holding the current release model here: https://github.com/weecology/DeepForest-pytorch/releases/tag/v0.1.17
• a pypi workflow on azure that pushes the pytorch version under the name deepforest https://pypi.org/project/deepforest/#history

anything else?

[ethanwhite]

I agree with the overall goal.

I vote for keeping the pytorch git history and have a clean git history that holds the deprecated tensorflow code.

We can easily have separate histories for the two branches, which reflects the reality of how they were developed. I'm happy to take care of this as soon as we're ready.

I think little clean up/management things to add include:

• Issue in deepforest repo to notify folks of the change
• Issue in the deepforest-pytorch repo to notify folks of the change
• Issues in repos with deepforest tensorflow dependencies notifying them of the change
• Update README in deepforest-pytorch to point users back to deepforest
• Redirect pip installs of deepforest-pytorch to deepforest: https://github.com/simonw/pypi-rename

[henrykironde]

• Update the release
• Update the conda package

[bw4sz]

#195

[bw4sz]

There is now a main branch that holds the pytorch versus, which is default, and a tensorflow version that holds the original.

[henrykironde]

@bw4sz there are a few changes required after the change to main. These are some of the files that we may have to change
https://github.com/weecology/DeepForest/search?q=master

let me know if you want me to make those changes, In case you have not started.

[bw4sz]

i'm done for the night, I can pick up monday, if you have time this weekend, that's great, if not let me know.

…

On Fri, Jun 4, 2021 at 9:11 PM henry senyondo ***@***.***> wrote: @bw4sz <https://github.com/bw4sz> there are a few changes required after the change to main. These are some of the files that we may have to change https://github.com/weecology/DeepForest/search?q=master let me know if you want me to make those changes, In case you have not started. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#193 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJHBLEIHIFVMSC75EIWETLTRGPWJANCNFSM46BPJF2A> .

-- Ben Weinstein, Ph.D. Postdoctoral Fellow University of Florida http://benweinstein.weebly.com/

[bw4sz]

https://deepforest.readthedocs.io/en/latest/ now builds pytorch docs.

[bw4sz]

New release that matches pytorch https://github.com/weecology/DeepForest/releases/tag/1.0.0

[bw4sz]

added note in deepforest-pytorch to point users here.

[bw4sz]

pypi deepforest release points to main branch at 1.0.0

https://pypi.org/manage/project/deepforest/release/1.0.0/

[bw4sz]

@henrykironde can I assign you ethan's request that

Redirect pip installs of deepforest-pytorch to deepforest: https://github.com/simonw/pypi-rename

[bw4sz]

cleaned up old issues.

[bw4sz]

Added note to the front of tensorflow branch on updating model.

https://github.com/weecology/DeepForest/blob/tensorflow/README.md

[bw4sz]

Added issues in active downstream repos.