Converting to v2.1

[Banaanae]

With v2.1 being released into alpha I've been brainstorming ideas on how to implement this

• New branch, develop concurrently until v2.1 is released fully (May cause many merge conflicts)
• Option in settings to convert to v2.1? (Lot of work)
• Start converting scripts straight to v2.1 now (Probably not as most people would still want v1.1 to v2)
• New repo (would require people downloading both to go from v1.1 to v2.1)

Personally thinking about option 1, but want to get others ideas on it, and any other ideas people might have

[mmikeww]

Are there going to be many breaking changes? Option 1 is probably best I think

…

On Mon, Mar 25, 2024, 6:31 AM Banaanae ***@***.***> wrote: With v2.1 being released into alpha I've been brainstorming ideas on how to implement this - New branch, develop concurrently until v2.1 is released fully (May cause many merge conflicts) - Option in settings to convert to v2.1? (Lot of work) - Start converting scripts straight to v2.1 now (Probably not as most people would still want v1.1 to v2) - New repo (would require people downloading both to go from v1.1 to v2.1) Personally thinking about option 1, but want to get others ideas on it, and any other ideas people might have — Reply to this email directly, view it on GitHub <#154>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOQBDB6XEIPEIYYHQAUCB3YZ74GPAVCNFSM6AAAAABFGX2RV6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYDKNBQGUZDMOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>