|
3 | 3 | This release brings new equipment support, bug fixes/code cleanups, and some |
4 | 4 | changes to ease transition to 5.0 |
5 | 5 |
|
6 | | -**Support term changes go here** |
| 6 | +As many changes are planned for Hamlib in the future leading to 5.0.0 |
| 7 | +(no planned release date at this time), the 4.7.x series is planned to |
| 8 | +be a sort of long term support release and will receive updates in the |
| 9 | +form of new models and backends as they are developed. If all goes well |
| 10 | +such updates will be in parallel with 5.0.0 development. |
| 11 | + |
| 12 | +This will place a burden on contributors who are asked to submit such |
| 13 | +code to both the master and Hamlib-4.7 branches. Hopefully this period |
| 14 | +will not last overly long and development can concentrate solely on the |
| 15 | +Hamlib 5 series at some point in the future. |
7 | 16 |
|
8 | 17 | ## New equipment support |
9 | 18 | - Icom IC-7300MK2 |
@@ -31,8 +40,8 @@ changes to ease transition to 5.0 |
31 | 40 | ## Changes for 5.0 |
32 | 41 | HAMLIB 5.0 will make some major changes to the Application Binary Interface(ABI) that will |
33 | 42 | require changes to some applications, and at least recompilation/linking for all |
34 | | -apps. Most(all, I hope) of these source changes can be made/tested/debugged incrementally |
35 | | -with 4.7, making the transition much easier. The Application Programming Interface(API) |
| 43 | +apps. These source changes can be made/tested/debugged incrementally with 4.7, |
| 44 | +making the transition much easier. The Application Programming Interface(API) |
36 | 45 | does not change. |
37 | 46 |
|
38 | 47 | ### Storage restructuring |
|
0 commit comments