[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [OctDev] control-2.3.50 released in package forum - please upload
From: |
Lukas Reichlin |
Subject: |
Re: [OctDev] control-2.3.50 released in package forum - please upload |
Date: |
Tue, 6 Mar 2012 21:33:41 +0100 |
On 06.03.2012, at 20:48, Carnë Draug wrote:
> On 6 March 2012 14:23, Lukas Reichlin <address@hidden> wrote:
>> Hi all,
>>
>> I've just posted control-2.3.50 (SVN Revision 9754) in the package forum
>> [1]. Please upload it to the server. The changes are listed in the NEWS file
>> [2]. The main features are frequency-weighted model and controller order
>> reduction tools as well as cleanup efforts under the hood.
>
> Done. Just uploaded it to the server and updated the documentation.
>
> Curious about one thing, why is the first release of the 2.3 version
> the number 50? This also happened for the 2.1 version but not for 2.2.
> Is this matching the octave core where odd numbers are development
> releases? In that case, should 2.3.X releases be considered
> development releases?
>
> Carnë
Well, I tried to use the octave core scheme. I use odd numbers (2.1.50-2.1.55)
to add new features / make important changes. When I reached my goals, I
release a package with an even number (2.2.0). It is followed by minor revision
(2.2.1 - 2.2.5) for bugfixes and small additions. I am going to release 2.3.5*
versions until my features for 2.4.0 are ready:
- model and controller reduction (done)
- clean up oct-files (done)
- "multiplot" feature
- system identification
There was a 2.1.5* release about every fortnight for people who wanted the
latest features as soon as they became ready. Those who didn't want to install
weekly updates could wait for 2.2.0. In general, there's no difference in
quality between even and odd versions.
Do you think it is confusing? Shall I do it differently?
Regards,
Lukas