You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Feature request #1375: Synergy 4.0 final upgrade pathway

Kind feature request
Product Synergy
When
Status closed
Reporter Greg Hurrell
Tags no tags

Description

For a while now I've been trying to warn users that Synergy 3.5 would be the first non-free update in Synergy's history:

Basically, all such posts included text like the following:

Once the 3.5 series goes final it will be a free upgrade to all users who have purchased a license for Synergy 3.0 or higher (that is, if you purchased on or after 5 September 2006 then 3.5 will be a free upgrade for you).

In the end due to Apple's infamous NSAppleScript Garbage Collection bug (see ticket #640) 3.5 remained in "alpha" status for the entire Leopard product cycle and I never declared a release as "final".

Now Snow Leopard is out and I am preparing a 4.0 release. If Apple has finally fixed the bug then this release can be declared final and I'll be proceeding with the upgrades.

The following steps need to be implemented during the alpha/beta phase:

  1. In each release announcement must put a clear notice about the upgrade policy.
  2. Date checks on licenses: if a user is using an old license show a dialog once and once only that said license won't be valid for 4.0 final, and providing buttons to either purchase an upgrade or enter a new serial number.
  3. In the 4.0 final release, the once-only dialog becomes a once-per-run dialog.
  4. (Not decided for sure yet.) Possibly need to modify my payment handling scripts to offer discounted licenses to upgraders; the scripts are currently hard-coded to expect a 5€ payment, but most likely will be looking at a 10% discount, so they'll need to accept 4.50€ also.

At the same time I think I am going to take the opportunity to store the license separately in ~/Library/Application Support/ rather than embedding it in the preferences file, where it is too easily overwritten or lost.

Comments

  1. Greg Hurrell

    Ok, most of the code-side work on this is done. I've had a look at my PayPal fees and it doesn't look viable to offer discounted licenses, seeing as it would drop my per-license revenue prior to expenses below 4 euros, which isn't enough to offset server costs and other overheads.

    The move to Application Support isn't one I'll going to pursue right now, as I want to keep the complexity of code changes down to a minimum to minimize risk of breakage.

  2. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu