[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Future release schedules
From: |
Eli Zaretskii |
Subject: |
Re: Future release schedules |
Date: |
Sat, 21 Nov 2015 13:14:33 +0200 |
> From: John Wiegley <address@hidden>
> Cc: address@hidden, address@hidden, address@hidden, address@hidden,
> address@hidden, address@hidden, address@hidden
> Date: Fri, 20 Nov 2015 13:33:20 -0800
>
> Ok, how about a tick-tock schedule then, while we lack such manpower? Release
> focus year 1, next release feature focus year 2, etc. Perhaps this is even
> what you meant.
We could try that. It all depends on how long it takes to develop and
integrate a few significant features. Based on recent experience, a
year might not be enough, but we could set that as a goal and see
where it takes us.
- Future release schedules (was: make change-history on non-master branches), (continued)
- Future release schedules (was: make change-history on non-master branches), John Wiegley, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Eli Zaretskii, 2015/11/20
- Re: Future release schedules, John Wiegley, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Artur Malabarba, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Artur Malabarba, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Eli Zaretskii, 2015/11/20
- Re: Future release schedules (was: make change-history on non-master branches), Eli Zaretskii, 2015/11/20
- Re: Future release schedules, John Wiegley, 2015/11/20
- Re: Future release schedules, Eli Zaretskii, 2015/11/20
- Re: Future release schedules, John Wiegley, 2015/11/20
- Re: Future release schedules,
Eli Zaretskii <=
- Re: make change-history on non-master branches, Eli Zaretskii, 2015/11/18
- Re: make change-history on non-master branches, Glenn Morris, 2015/11/18