Development mailing list

Syndicate content
Archive of posts for haiku-development at FreeLists
Updated: 1 hour 33 min 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

[haiku-development] Re: Beta1 and R1 release plan (Rene Gollent)

Fri, 2014-11-07 20:45
On Mon, Nov 3, 2014 at 9:14 AM, Stephan Aßmus superstippi@xxxxxx wrote: 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. Agreed, I like this suggestion. Regards, ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Stephan Aßmus)

Fri, 2014-11-07 20:45
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 ...
Categories: Development

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

Fri, 2014-11-07 20:45
Am 03.11.2014 12:00, schrieb Adrien Destugues: The R2 side of things was left open to discussion on purpose. I know there isn't much agreement (or even much discussion) on what R2 should be. I would prefer R2 to happen in less than 13 years, as maintaining the R1 branch for so long is not something very enjoyable. The best way to achieve this, though, is to actually fledge out a plan :-) ...
Categories: Development

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

Fri, 2014-11-07 18:45
On Mon, Nov 03, 2014 at 10:57:32AM +0100, Axel Dörfler wrote: Am 02.11.2014 18:54, schrieb Jérôme Duval: 2014-11-02 10:22 GMT+01:00 Adrien Destugues pulkomandy@xxxxxxxxx: During the BeGeistert coding sprint we had a long discussion with Ingo, Oliver and Ithamar about the future of Haiku and the problems we have with getting releases out. We have reached an agreement on this and we would like to propose a plan to finally get R1 out and move on to the next steps of development. +1 except I think the R1 branch could also see new features. I don't see any reason why R1.1 should only be a fixes-only release. ...
Categories: Development

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

Fri, 2014-11-07 18:45
Am 02.11.2014 18:54, schrieb Jérôme Duval: 2014-11-02 10:22 GMT+01:00 Adrien Destugues pulkomandy@xxxxxxxxx: During the BeGeistert coding sprint we had a long discussion with Ingo, Oliver and Ithamar about the future of Haiku and the problems we have with getting releases out. We have reached an agreement on this and we would like to propose a plan to finally get R1 out and move on to the next steps of development. ...
Categories: Development

[haiku-development] Re: Google Code-In 2014 (Jorma Karvonen)

Fri, 2014-11-07 18:45
OK, br, Karvjorm 2014-11-03 11:00 GMT+02:00 Adrien Destugues pulkomandy@xxxxxxxxx: On Mon, Nov 03, 2014 at 10:58:10AM +0200, Jorma Karvonen wrote: Please, DO NOT include Finnish language related trac tickets in Google ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Stephan Aßmus)

Fri, 2014-11-07 18:45
Hi all, Am 02.11.2014 um 10:22 schrieb Adrien Destugues pulkomandy@xxxxxxxxx: We have drafted a plan to allow for a smooth transition to the future Haiku. +1 for the overall plan. Best regards, -Stephan ...
Categories: Development

[haiku-development] Re: Google Code-In 2014 (Adrien Destugues)

Fri, 2014-11-07 18:45
On Mon, Nov 03, 2014 at 10:58:10AM +0200, Jorma Karvonen wrote: Please, DO NOT include Finnish language related trac tickets in Google Code-In 2014. Last time there were several students who did not know Finnish at all. They tried to execute tasks using Google Translate and all got wrong. Generally, using Google Translate into Finnish language is considered as a joke, because translation is hardly never correct. We were not the only project victim of this, and Google removed the whole localization part of GCI from the program since it is not easily possible to check the translations - or at least it is easy enough for ...
Categories: Development

[haiku-development] Re: Google Code-In 2014 (Jorma Karvonen)

Fri, 2014-11-07 18:45
Please, DO NOT include Finnish language related trac tickets in Google Code-In 2014. Last time there were several students who did not know Finnish at all. They tried to execute tasks using Google Translate and all got wrong. Generally, using Google Translate into Finnish language is considered as a joke, because translation is hardly never correct. br, Karvjorm ...
Categories: Development

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

Fri, 2014-11-07 18:45
On Mon, Oct 27, 2014 at 11:16 PM, scottmc scottmc2@xxxxxxxxx wrote: I have signed Haiku up as a possible mentoring org for Google Code-In 2014. If you would like to be a mentor for Haiku this year contact me off-list. Our brain storming ideas wiki page it here: ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Jessica Hamilton)

Fri, 2014-11-07 18:45
On Monday, 3 November 2014, Adrien Destugues pulkomandy@xxxxxxxxx wrote: On Sun, Nov 02, 2014 at 12:04:19PM -0800, Niels Sascha Reedijk wrote: The goals here are multiple: * Finally provide a stable release which third-party developers can use * Setup a better release cycle so we can put out releases more frequently * Let the developers work on more exciting things without making them feel guilty for not working on the important R1 stuff ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Ingo Weinhold)

Fri, 2014-11-07 18:45
On 11/02/2014 06:54 PM, Jérôme Duval wrote: 2014-11-02 10:22 GMT+01:00 Adrien Destugues pulkomandy@xxxxxxxxx: During the BeGeistert coding sprint we had a long discussion with Ingo, Oliver and Ithamar about the future of Haiku and the problems we have with getting releases out. We have reached an agreement on this and we would like to propose a plan to finally get R1 out and move on to the next steps of development. ...
Categories: Development

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

Fri, 2014-11-07 16:45
On Sun, Nov 02, 2014 at 12:04:19PM -0800, Niels Sascha Reedijk wrote: The goals here are multiple: * Finally provide a stable release which third-party developers can use * Setup a better release cycle so we can put out releases more frequently * Let the developers work on more exciting things without making them feel guilty for not working on the important R1 stuff Overall I concur with the goals. What is missing here is the end-goal, meaning why are we still working on Haiku? Quoting the mission statement from our homepage: Haiku is a new open-source operating system that ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Niels Sascha Reedijk)

Fri, 2014-11-07 16:45
Hello devs, On Sunday, Nov 2, 2014 at 10:25 am, Adrien Destugues pulkomandy@xxxxxxxxx, wrote: Hello devs, ...
Categories: Development