On Fri, Jun 3, 2016 at 2:02 PM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:
> Le 31/05/2016 à 22:26, Georg Baum a écrit :
>>
>> We need to decide: Either have a fixed schedule, and an unknown feature
>> set
>> of the next release, or a fixed feature set, and an unknown schedule. We
>> do
>> not have enough man power for defining both a fixed feature set and a
>> fixed
>> release schedule.
>
>
> I prefer the fixed schedule. We never know exactly when starting a release
> cycle what features will happen or not. But we can enforce when the release
> will happen.
>
I too would favour a fixed schedule. Have a planned ~1 year release
cycle (instead of the 2-2.5 years we currently have, on average), and
start the release process and discussing tagging alpha some 6-8 months
into the cycle. This will help avoid burn out for devels and dragging
new features in trunk for longer than necessary, and avoid too much
uncertainty on when the release will actually happen. This will also
make it possible to make fileformat changes more often than we now do,
and bring about serious testing of trunk (with alpha and beta
releases) by end users less than a year since major features were
introduced on GIT.



>> - Have a build server that does automatic builds on a regular basis for
>> all
>> three platforms (Linux, OS X, windows) and makes binary packages and build
>> logs available.
>
>
> Do you have a particular service in mind? I agree that this would be nifty.
>
We already have nightly builds for Ubuntu Linux:
https://launchpad.net/~lyx-devel/+archive/ubuntu/daily

It's been running for couple of years (probably all through the 2.2
development cycle), though I'm not sure it's made much of an impact in
terms of testing and bug reports. (I still have to update the
packaging arrangements for 2.3dev, but it should be up and running
"soon".)


Liviu





-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Reply via email to