Development mailing list

Syndicate content
Archive of posts for haiku-development at FreeLists
Updated: 1 hour 45 min ago

[haiku-development] Re: Beta1 and R1 release plan (Julian Harnath)

Mon, 2014-11-10 09:45
Hey, Axel Dörfler axeld@xxxxxxxxxxxxxxxx schrieb: About the release, the keys to the solution are in Ingo's reply, and are: - We need stable internal protocols/interfaces. Ie. if we do incompatible changes in the future, we need to version the communication. - This allows us to keep old repositories around. Incompatible versions ...
Categories: Development

[haiku-development] Re: Beta1 and R1 release plan (Donn Cave)

Mon, 2014-11-10 07:45
quoth Axel Dörfler, That allows a user to run new versions of Haiku as wished, and still be able to run software that requires an older version. I thought I'd pop in here in case my situation sheds any interesting light on the problem. I'm not sure what this proposal really means - probably I'm weak on the terminology, because for example this isn't clear to me: ...
Categories: Development

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

Mon, 2014-11-10 05:45
Am 04/11/2014 15:06, schrieb Ingo Weinhold: I don't think a rolling release model is realistic ATM. We neither have the means (infrastructure, automated tests) nor the manpower and would likely produce one broken state after the other. I just talked with Ingo on the phone to discuss this further, and while we did not really find a common ground on the topic of rolling releases, ...
Categories: Development

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

Sun, 2014-11-09 23:45
Am 04.11.2014 um 11:26 schrieb Adrien Destugues pulkomandy@xxxxxxxxx: Well, yes, we could go back to ffmpeg 0.8.something, which worked, but then we lose support for h264 and probably some other really common video and audio formats (also for decoding). I don’t know why you say that. I can assure you that h264 worked when I worked on the ffmpeg media add-on. Maybe it got broken by an in-between update of ffmpeg, I don’t know. At least I was not aware that it was broken ...
Categories: Development

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

Sun, 2014-11-09 21:45
On 11/03/2014 10:57 AM, Axel Dörfler wrote: Am 02.11.2014 18:54, schrieb Jérôme Duval: +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. Agreed. Furthermore, while the plan is very developer friendly, it's ...
Categories: Development

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

Sun, 2014-11-09 21:45
On Tue, Nov 04, 2014 at 03:53:40AM -0800, Niels Sascha Reedijk wrote: Hi, On general I agree with the statements in the discussion. In this email I argue that we might have to tweak our view on our target audience, and at the bottom I will outline my view on the future release discussion. Hi, It seems your email client does not properly quote what you reply to (at least in the text version of what it sends). Could you see if it's ...
Categories: Development

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

Sun, 2014-11-09 21:45
Hi, On general I agree with the statements in the discussion. In this email I argue that we might have to tweak our view on our target audience, and at the bottom I will outline my view on the future release discussion. ...
Categories: Development

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

Sun, 2014-11-09 19:45
On Tue, Nov 04, 2014 at 11:38:20AM +0100, Axel Dörfler wrote: Am 04.11.2014 11:26, schrieb Adrien Destugues: Well, yes, we could go back to ffmpeg 0.8.something, which worked, but then we lose support for h264 and probably some other really common video and audio formats (also for decoding). I don’t know why you say that. I can assure you that h264 worked when I worked on the ffmpeg media add-on. Maybe it got broken by an in-between update of ffmpeg, I don’t know. At least I was not aware that it was broken at some point, and I watched h264 encoded videos on Haiku from time to time. ...
Categories: Development

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

Sun, 2014-11-09 19:45
Am 04.11.2014 11:26, schrieb Adrien Destugues: Well, yes, we could go back to ffmpeg 0.8.something, which worked, but then we lose support for h264 and probably some other really common video and audio formats (also for decoding). I don’t know why you say that. I can assure you that h264 worked when I worked on the ffmpeg media add-on. Maybe it got broken by an in-between update of ffmpeg, I don’t know. At least I was not aware that it was ...
Categories: Development

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

Sun, 2014-11-09 19:45
Well, yes, we could go back to ffmpeg 0.8.something, which worked, but then we lose support for h264 and probably some other really common video and audio formats (also for decoding). I don’t know why you say that. I can assure you that h264 worked when I worked on the ffmpeg media add-on. Maybe it got broken by an in-between update of ffmpeg, I don’t know. At least I was not aware that it was broken at some point, and I watched h264 encoded videos on Haiku from time to time. Well then, why don't we revert to that perfectly working ffmpeg version, ...
Categories: Development

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

Sun, 2014-11-09 19:45
Am 04.11.2014 um 10:35 schrieb Adrien Destugues pulkomandy@xxxxxxxxx: On Tue, Nov 04, 2014 at 09:39:23AM +0100, Axel Dörfler wrote: It is currently not possible to encode audio and video in Haiku (MediaConverter will crash). I don't really see the connection. ffmpeg definitely could do that years ago, the problem must be on our side, anyway. Well, yes, we could go back to ffmpeg 0.8.something, which worked, but ...
Categories: Development

[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