Why do the MacJournal alphas/betas have an expiration date?
MacJournal 2.6 is the second time I’ve done public pre-releases. It worked fantastically for 2.5 and has been even better for 2.6. But one of the things I learned from the 2.5 process is that people won’t always update to the latest pre-release build even if they understand it is pre-release software. I can understand it from their perspective (as the user who wants things running smoothly and if it isn’t broken then don’t fix it), but from my perspective (the developer who can’t support pre-release builds forever) it’s less than optimal. I can’t support 2.5b4 18 months after 2.5b5 was released. I need people to stay as current as possible to ferret out any problems that they may have. If you tell me about it now, I can fix it for the final build. If you e-mail me a year later I can’t help you. So it works to everyone’s advantage to stay within a build or two of the most current release. I try to stage the 2.6 releases so at least 2 builds still work, so if the most recent one doesn’t
Related Questions
- How long are EAR licenses good for? I know DOD licenses are good for 10 years but would like to know for EAR licensing and if you go by approved date or expiration date?
- Is the EAA doing anything official to change the expiration date of E-LSA aircraft in January 2010? And is there something I can do as a WSC sport pilot and EAA member?
- Why do the MacJournal alphas/betas have an expiration date?
