Sorry, I meant 0.9.24. A typo.
Which fpc version it's gonna use? fpc stable or fpc fixes? I hope
Lazarus fixes will use fpc fixes, as I suggested. This way, we'll have
fixes from both tool (fpc and lazarus). I personally would prefer to use
this fixes branch for development.
-Bee-
has
Bee wrote:
Sorry, I meant 0.9.24. A typo.
Which fpc version it's gonna use? fpc stable or fpc fixes? I hope
Lazarus fixes will use fpc fixes, as I suggested. This way, we'll have
fixes from both tool (fpc and lazarus). I personally would prefer to use
this fixes branch for development.
You are about snapshots or sources?
Both, as I suggested before:
- Lazarus 9.24.0 using FPC 2.2.0 (latest stable)
- Lazarus 9.24.1 using FPC 2.2.1 (latest fixes)
- Lazarus 9.25 using FPC 2.3.1 (latest development)
-Bee-
has Bee.ography at:
http://beeography.wordpress.com
Bee пишет:
You are about snapshots or sources?
Both, as I suggested before:
- Lazarus 9.24.0 using FPC 2.2.0 (latest stable)
- Lazarus 9.24.1 using FPC 2.2.1 (latest fixes)
- Lazarus 9.25 using FPC 2.3.1 (latest development)
Then lets think of how to release lazarus 0.9.26 before fpc 2.4?
Then lets think of how to release lazarus 0.9.26 before fpc 2.4?
Wouldn't laz 9.26 is based on 9.25 and fpc 2.4 is based on 2.3? This way
laz release will be always synchronized with fpc release. If we stick
to this scheme then we shouldn't release laz 9.26 before fpc 2.4 is
released.
Bee пишет:
Then lets think of how to release lazarus 0.9.26 before fpc 2.4?
Wouldn't laz 9.26 is based on 9.25 and fpc 2.4 is based on 2.3? This way
laz release will be always synchronized with fpc release. If we stick
to this scheme then we shouldn't release laz 9.26 before fpc 2.4 is
Yes, but we have plans to release more often than fpc team - at least
twice per year, or better once per quarter.
Using above versioning scheme, we don't need to release often, IMO.
Because we have fixes branch. People who don't wait too long for
official stable release should use fixes
Hi all,
I found FPC's versioning scheme is neat. It has 3 versioning scheme:
stable, fixes, and development. But I found Lazarus only got 2
versioning scheme: stable and development.
So, I think it's good if Lazarus also follows FPC's versioning scheme.
Each scheme uses appropriate FPC
Bee ha scritto:
Hi all,
I found FPC's versioning scheme is neat. It has 3 versioning scheme:
stable, fixes, and development. But I found Lazarus only got 2
versioning scheme: stable and development.
So, I think it's good if Lazarus also follows FPC's versioning scheme.
Each scheme uses
Lazarus fixes branch is on its way, starting from 9.0.24. It will just
contain bugfixes for 9.0.24 which popped up after the official release.
Did you mean 9.24.0? Next Laz stable version is 9.24, isn't?
Just warming up the motors.
That's really a good news! :)
I'm in charge of it, but
Bee ha scritto:
Lazarus fixes branch is on its way, starting from 9.0.24. It will just
contain bugfixes for 9.0.24 which popped up after the official release.
Did you mean 9.24.0? Next Laz stable version is 9.24, isn't?
Sorry, I meant 0.9.24. A typo.
Giuliano
--
Giuliano Colla
Whenever
11 matches
Mail list logo