Aha, ok i see my 'error' now...

So, i need to re-arrange my mind a little: (old) v0 is no more, and v0-on-trunk took its place -> now v0

All clear now, thanks for the explanation.

Let me explain this in a bit different way.

There are only two ABIs: ABIV0 and ABI"in progress" (also called V1). Which branch in repository each ABI is hosted on is a detail. ABIV0 is now hosted on branch called "ABIV0-on-trunk-20141231" and ABIV1 is hosted on branch called "trunk". Both of those branches are used to create nightly builds labelled ABIV0 and ABIV1 respectivelly.

That is why when discussing we should simply use ABIV0 vs ABIV1 terms to make it simple.

Thank you very much for the correction there deadwood.

Just to make things clear (and sorry if i perhaps phrase a bit incorrectly): does that mean that your improvements which were made in on-trunk to be able to make use of some v1 features/improvements has found its way back into 'regular' abi-v0 now ?

That things are not updated as planned was not meant as criticism, just attempting to make clear for those affected that it might take a while for further enhancements/improvements to find its way back.

BTW, I will start the next refresh in Januarry, but since it is a whole year of changes, I don't know how long it will take to finish it.

@magorium

The ABIV0-on-trunk was a transition name when this was in development to distinguish between old ABIV0 and the new developments. Now there is only one ABIV0 and it is the branch from which the nightly builds are beeing build. This branch get critical fixes and is refreshed with new features on (unfortunatelly) yearly basis.

Quote:
afaik, no.

ABIv0 development halted many moons ago (see trac).

ABIv0-on-trunk is an effort made by deadwood (also see trac), also with help from other developers, and is updated on a regular base (well that was the plan until the time-devil disturbed things).

That means that every improvement made to v1 that is to be incorporated in on trunk (backporting) needs to be done manually.

The 'old' system in where v1 fixes were (more or less) automatically (but also manually) backported to v0, seems to be no more.

I think you've been missing the piece "the v0 days are over things moved forward"

personally i failed to see the point, since neither v0 or v1 is in a 'finished' state.

Quote:

I'm starting missing pieces here... hadn't ABIV0-on-trunk become the de-facto current ABIV0 build, many months ago?

In any case, I would really love to see this issue fixed in Icaros some day. With no hurry to anyone, obviously.

Thanks ncafferkey! Excellent!

Thank you very much ncafferkey.

As most have already expressed, this [s]is[/s] was one of the most annoying visible bugs.

This is now fixed in ABIv1. I probably won't backport it to ABIv0, but it should eventually appear in the next global backport for ABIv0-on-trunk.