2017-07-16 06:21:56 UTC
release of trunk, to help us build towards 0.93. Something a bit more
than just a nightly snapshot, but far less than even an alpha release.
Call it an "unrelease" or just a "blessed snapshot".
Here's my reasoning for why I think this would be worth doing:
a. Our alphas get decent testing, but there's not time for the
necessary bug fixing, since we're anxious to get the actual release
out. This interim release would stimulate testing and bug fixing
independent of any such pressure.
b. Moving to gitlab, cmake, and gtk3 has changed a LOT structurally.
Doing a "practice release" would help find remaining problems with
c. Despite all the great work done setting up CI's, automated builds,
and rolling packaging systems, many advanced users want a fully
usable, QA'd build before they'll look at our work. Lesson learned
from last release is that we really need these kinds of users' input
on our features before we finalize stuff.
d. For the rest of us Inkscapers, it will provide a focal point for our
near term development, testing, documentation, and refactoring work.
But one that won't need all the rigor that a regular release would
have - no about screen contests, overly long feature freeze periods,
string freezes, worrying over release-blocker bugs, or needing to
polish up release notes and other docs.
* A soft feature freeze for a week or two, max
* No more than one pre-release (if even that)
* Translations encouraged, but no string freeze
* Packaging needed for all platforms
* Packages available from website, but not linked prominently
* Lite marketing - basically just target to advanced users
* Is clearly marked UNSTABLE and UNSUPPORTED
Some other crazy ideas to consider, that might help prevent it from
becoming a support burden:
+ Annoying popup dialog declaring it so at run time?
+ No guarantee of file format compatibility?
+ Limited period for accepting bugs reports?
+ Expiring binary refuses to run after a certain date?
+ Advise distros to NOT distribute it?
So, your thoughts?