Feature #988
Review Tony branch and merge back to default?
| Status: | Resolved | Start date: | 2014-06-17 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Matthias Mauch | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
I am a little concerned by the thought that if a Tony user (especially likely on Linux) builds Tony and pYIN separately and installs them both from their default branches, they will end up with "the wrong" user experience because they aren't using the Tony branch of pYIN.
We should either make sure the default branch is properly compatible with Tony, or else make the two plugins have different identifiers so that they don't get mixed up. Or something. And we should also increase the version number!
Thoughts?
History
#1
Updated by Matthias Mauch about 9 years ago
- Status changed from New to Resolved
Chris Cannam wrote:
I am a little concerned by the thought that if a Tony user (especially likely on Linux) builds Tony and pYIN separately and installs them both from their default branches, they will end up with "the wrong" user experience because they aren't using the Tony branch of pYIN.
We should either make sure the default branch is properly compatible with Tony, or else make the two plugins have different identifiers so that they don't get mixed up. Or something. And we should also increase the version number!
Thoughts?
Sorry I didn't reply. But in the process of producing the new Tony release, this has been done, and the default branch has the "right" version.