Development mailing list

Syndicate content
Archive of posts for haiku-development at FreeLists
Updated: 20 min 18 sec ago

[haiku-development] Re: Beta1 and R1 release plan (Adrien Destugues)

Sun, 2014-11-09 19:45
On Tue, Nov 04, 2014 at 09:39:23AM +0100, Axel Dörfler wrote: Waiting for years for a system update is not a problem. We are talking about just the system here, not the whole package repository as it happens in Linux distributions. Using an old system does not mean you are restricted to old applications. That certainly relieves the situation, yes, but that's still not any different from BeOS days. You can still use BeOS R5 with current applications. But since it's dead, almost no one develops for it anymore. It's a mostly a psychological thing. If you have that huge piece of software ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Axel Dörfler)

Sat, 2014-11-08 14:45
Am 03.11.2014 18:52, schrieb Adrien Destugues: On Mon, Nov 03, 2014 at 05:47:36PM +0100, Axel Dörfler wrote: As I already said, I would much like a stable branch, from which releases should be made. You think it should derive from the R1 branch and integrate features from master whenever possible. I think we should instead keep master stable so we can branch out future releases from it. I suggest doing that by using the Gerrit flow (where changes are reviewed before they can be merged to master) or something similar. ...
Categories: Development

[haiku-development] Re: Google Code-In 2014 (John Scipione)

Sat, 2014-11-08 14:45
We could maybe track more Finish language features ourselves, only, I don't know Finnish so I cannot help. On Monday, November 3, 2014, Jorma Karvonen karvonen.jorma@xxxxxxxxx wrote: OK, br, ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Adrien Destugues)

Sat, 2014-11-08 00:45
On Mon, Nov 03, 2014 at 05:47:36PM +0100, Axel Dörfler wrote: Yes, in the original plan, the R1 branch would be a dead-end. It is kept there for security updates and bugfixes to R1, until R2 is out. The idea being that we continue to support users running R1, and fixing bugs for them, while on the R2 branch we prepare and publish alphas and betas. The two branches thus live in parallel for some time (as short as possible), so there is an R1 release for users, which is bug-free, and an R2 pre-release for developers, which proably has some bugs but where they can experiment with the new R2 features. ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Axel Dörfler)

Fri, 2014-11-07 22:45
Am 03/11/2014 15:27, schrieb Adrien Destugues: On Mon, Nov 03, 2014 at 02:34:56PM +0100, Axel Dörfler wrote: Before making master a playground, I would prefer a Linux like approach, ie. a next (playground), and a stable repository, and establish a review process for the latter only (IIRC Oliver is still investigating this). Still, even playground should only receive mostly complete features. That other playground should stay the local/github repository of the developers. ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Adrien Destugues)

Fri, 2014-11-07 22:45
On Mon, Nov 03, 2014 at 02:34:56PM +0100, Axel Dörfler wrote: The way I see things, is that our master branch is a playground for developers. That doesn't mean R2 is. An R2 branch can be split out of the master and stable features merged there. We can then plan a release at any time knowing that we have a stable branch to work from. Starting the R2 work from the R1 branch instead would mean more work in catching up with trunk and I'm not sure what the gains are. Maybe I did not made myself clear enough: without keeping those branches connected, as a user, you won't have any functional update of Haiku for the ...
Categories: Development