[haiku-development] Re: Beta1 and R1 release plan
- From: Stephan Aßmus <superstippi@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 3 Nov 2014 15:14:39 +0100
Hi,
> Am 03.11.2014 um 14:34 schrieb Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:
>
> Following my suggestion, this would look like this:
> - After R1 is released, we switch master to move GCC2 support to a legacy
> folder. Once that is done, it will be merged into the R1 branch, too (IOW,
> this branch (or one based on it) would become our release branch also for
> future releases). This will also make merging changes a lot easier.
> - R2 would happen in the GCC4 part of our tree. All applications & servers
> that come with Haiku would be switched to GCC4 (again, this would affect the
> release branch, too).
> - This way, we could deliver frequent updates to Haiku without having to
> worry about binary compatibility too much for quite some time to come.
>
> That would also mean that we will break binary compatibility for
> Tracker/Deskbar add-ons, etc. - I think this is acceptable, but if someone
> finds the motivation, I'm sure this would be fixable, too.
>
> The actual R2 release would mark the date when we make our GCC4 (or clang,
> for that matter) API stable. At that point we could decide (or not) to
> officially drop support for the GCC2 compatibility layer (ie. make it a
> nice-to-have external package that would not hold up future releases).
> Also, our libraries will then get versioned like any other, and we may need
> to keep old ones around for binary compatibility.
I think this is a very good plan, also because it is very specific. I can
easily understand how this could work and don’t see any big potential problems
with it.
Best regards,
-Stephan
Other related posts:
