On 4/27/2015 7:18 PM, Ryan Ollos wrote:
> The next releases (1.0.6 and 1.1.5) are scheduled for Monday May 4th (I
> modified the milestone due date over the weekend, previously it was May
> 1st). I'm going to try to create the releases early Monday morning of
> May 4th (GMT), which means we should wrap up changes by mid-day Sunday
> (GMT). The release steps are simplified quite a bit now and I'll be
> focusing on getting this release out on time.
Sounds good! Unfortunately I won't be able to assist, being away from my
workstation for a few weeks. But you seem to have everything under
control by now anyway.
>
> The milestones that follow are 1.0.7 and 1.1.6, scheduled for July 1st
> 2015. If things go well and we are in a good position for a 1.2 release
> following 1.1.6, then the 1.2 release could happen later in the month.
> That would give some time after 1.1.6 to pull in translations and ask
> for extensive beta testing of 1.1.6. That implies no enhancements, just
> fixes, between 1.1.6 and 1.2.
However I'll have time to catch-up reading my mail and contribute to the
previous discussions I missed on Trac-dev, notably the 1.2 roadmap and
what's beyond. Some of the ideas I'll try to develop would be to focus
on Python 2.7, find a way out of the Genshi trap and modernize the UI,
doing more stuff client-side and have the Python backend go back to
generate the data only (only, JSON instead of HDF this time ;-) ).
>
> We should think about how we'll support the 1.0.x line after 1.2 is
> released. I'd like to push only critical fixes to 1.0.x after 1.2 is
> released, but please let me know your thoughts.
>
Yes, once 1.2 is out, there will be no reason to continue adding
features or non-critical fixes to 1.0. We don't even need to label it as
"LTS", I think we could plan to have 1.2 as the next long term stable
basis after 0.12.
-- Christian