+1 for Mike’s suggestion On Sat, 17 Aug 2019 at 13:45, mike smith <[email protected]> wrote:
> I'd wonder if it wouldn't be easier to have just one version, but with > extra features enabled or not, depending on customer. Having to maintain > fixes in multiple versions gets to be a lot of work, testing, etc. > > Mike > > On Sat, Aug 17, 2019, 13:15 Glen Harvy <[email protected]> wrote: > >> Hi, >> >> Up till now I have been releasing updates to my projects to all valid >> licence holders if they have a current 'support/upgrade' licence. What I >> want to do is keep maintaining the current version (for example version >> 15) but I also want to release a new version (for example version 16). I >> want to charge version 15 licence holders should they wish to upgrade to >> version 16 but at the same time I will maintain version 15 for bug fixes >> and minor improvements etc. >> >> A complication is that Version 16 will have updated third party libraries >> whilst version 15 will only have the current version of the third party >> library. Unfortunately, the different versions of the third party libraries >> cannot both be installed on the same machine. >> >> I believe the above scenario will mean that I will need to maintain >> separate projects for version 15 as well as version 16 plus (one day) >> version 17 etc. Unless I update version 15 third party libraries to the >> newer versions of their libraries (and that is an option) then the separate >> projects will also need to reside on separate machines. >> >> I assume that the above can and probably often is resolved by using Git >> and branches which I do currently use for tracking but I was wondering if >> anyone else can share their experience before I take any course. >> >> >> >> >> Glen Harvy, >> *Aquarius Communications* <http://www.aquacomm.com.au> >> >> >> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >> Virus-free. >> www.avg.com >> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >> <#m_-5550497165796426406_m_6029028682910055284_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >
