Phase milestone for all the beta bugfixes needed before the final 1…(more)
Phase milestone for all the beta bugfixes needed before the final 1.2 release. Only bugfixes are accepted during the beta phase, ideally: that means no new features or string changes without a very good reason, please! This is the phase where we start asking translators to work on their bit, so the strings need to be as static as possible at this point. This milestone will generate formal prereleases on github.
Remaining tasks for MyPaint 1.2.0. Now just arranging for builds to be made.
Milestone for easy new features which need to be implemented before…(more)
Milestone for easy new features which need to be implemented before the beta release cycle for 1.2 starts. The beta cycle begins with a feature and string freeze, so anything involving mass string changes should go here. Also covers important bugs which should be fixed ASAP. However bugs can be deferred to the beta cycle... I've bumped the version number to indicate the transition from the current 1.1.1-alpha to 1.2.0-beta. It's a milestone, a waypoint, so let's name it for what it'll become.
Milestone marking tasks that need to be done before we bump the ver…(more)
Milestone marking tasks that need to be done before we bump the version number from 1.1.1-alpha to 1.2.0-alpha. Right now, I'm closing down this milestone, and moving its issues to later milestones: 1.2.0-alpha for all work which needs to be done before the beta cycle can start this means string changes and new features, plus any important bugs 1.2.0-beta.<1st> first beta milestone (of possibly many) formal beta release once this is complete, no date yet bugfixes only, ideally trivial ones; no string changes without good reason, and no new features 1.2.0 project management project stuff that needs to be done before the release actual software issues (bugs, enhancements) should go in one of the other milestones