I would suggest just using semver, treating a bump of the required Ledger version as a breaking change and noting the minimum required Ledger version in the release notes. I'm saying this with no knowledge of whether Ledger likes semver or has a problem with unsynchronized version numbers/large major versions :-).
On Tue, Aug 2, 2016 at 6:21 PM David Glasser <[email protected]> wrote: > Having a tight coupling between ledger and ledger-mode versions would have > been a problem even when they were in the same repo, since there's not much > to encourage users to make sure to carefully upgrade them simultaneously. > > On Tue, Aug 2, 2016 at 5:18 PM, Craig Earls <[email protected]> wrote: > >> I will use a separate version number. Up to this point there hasnt been >> one they are very loosely coupled. I am open to suggestions. Ledger mode >> is mostly getting bug fixes no features have been added in a few years now. >> >> On Tuesday, August 2, 2016, Ben Finney < >> [email protected]> wrote: >> >>> "John Wiegley" <[email protected]> writes: >>> >>> > >>>>> "BF" == Ben Finney <[email protected]> writes: >>> > >>> > BF> Are you de-coupling the release cycles, or will ‘ledger’ and >>> > BF> ‘ledger-mode’ still track the same version and release at the same >>> > BF> time? How will that be managed? >>> > >>> > They don't need to be exactly synced >>> >>> So, my question was based on the assumption that until now they are both >>> on a single release cycle, and both have an identical version at all >>> times. Is that assumption correct? >>> >>> > unless there is a change in the data protocol used between them, or in >>> > the reporting arguments. But all of that is very stable now. >>> >>> When the split occurs, will the versions mean what they do today by >>> remaining in lock-step at each release? Or will they diverge? >>> >>> -- >>> \ “Everyone is entitled to their own opinions, but they are not | >>> `\ entitled to their own facts.” —US Senator Pat Moynihan | >>> _o__) | >>> Ben Finney >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Ledger" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> -- >> Craig, Corona De Tucson, AZ >> enderw88.wordpress.com >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Ledger" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > [email protected] | langtonlabs.org | flickr.com/photos/glasser/ > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Ledger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
