I would like to propose that the next release remains 0.4, and that at that point that's when the clock starts for 1.0. So 1.0 will be a year after 0.4. The reason for suggesting this is that a few major infrastructure components are going to change after 0.3 (configuration, astropy_helpers, etc.) so I think it would be more realistic to plan 1.0 for in a year. We can still keep the release schedule above for 0.4, but the first LTS would be in a year. If people already decided against such an idea, then I'm happy to withdraw that suggestion.

Another idea is to plan to have 0.4 *sooner* than six months, as soon as the infrastructure changes are made (including whatever features are done by then), then start the clock then for 1.0.