Jump to page: 1 2 3
Thread overview
Master is now at frontend level 2.069.2
Feb 23, 2016
Kai Nacke
Feb 23, 2016
Dan Olson
Feb 23, 2016
kink
Feb 23, 2016
Kai Nacke
Feb 23, 2016
Kai Nacke
Feb 23, 2016
Johan Engelen
Feb 24, 2016
Kai Nacke
Feb 24, 2016
rsw0x
Feb 24, 2016
Kai Nacke
Feb 24, 2016
Russel Winder
Feb 24, 2016
Kai Nacke
Feb 24, 2016
Suliman
Feb 24, 2016
Kai Nacke
Feb 24, 2016
Russel Winder
Feb 24, 2016
Kai Nacke
Feb 24, 2016
Johan Engelen
Feb 24, 2016
Johan Engelen
Feb 24, 2016
Johan Engelen
Feb 25, 2016
Jacob Carlborg
Feb 25, 2016
Andrea Fontana
Feb 25, 2016
David Nadlinger
Feb 26, 2016
Andrea Fontana
Feb 25, 2016
Joakim
Feb 25, 2016
David Nadlinger
Feb 25, 2016
Joakim
Feb 25, 2016
Joakim
February 23, 2016
Hi everyone!

I merged the merge-2.069 branch into master right now. We are approaching the next release very fast!

Because the frontend is now written in D we Need a D Compiler to bootstrap. I moved the previous master to branch ltsmaster. This is the branch where we continue to maintain the C++ based version of LDC (release 0.17.x).

Have fun!

Regards,
Kai
February 23, 2016
Kai Nacke <kai@redstar.de> writes:

> Hi everyone!
>
> I merged the merge-2.069 branch into master right now. We are approaching the next release very fast!
>
> Because the frontend is now written in D we Need a D Compiler to bootstrap. I moved the previous master to branch ltsmaster. This is the branch where we continue to maintain the C++ based version of LDC (release 0.17.x).
>
> Have fun!
>
> Regards,
> Kai

Nice and thanks.  I assume best practice for changes intended for both ltsmaster and master, do pull-request to ltsmaster first, then later merge into master?  I am thinking of my latest arm-linux changes.

And "ltsmaster" - what does "lts" stand for?
--
Dan
February 23, 2016
On Tuesday, 23 February 2016 at 16:59:25 UTC, Dan Olson wrote:
> And "ltsmaster" - what does "lts" stand for?

Long-term support I'd guess (known from Ubuntu).
February 23, 2016
On Tuesday, 23 February 2016 at 17:02:45 UTC, kink wrote:
> On Tuesday, 23 February 2016 at 16:59:25 UTC, Dan Olson wrote:
>> And "ltsmaster" - what does "lts" stand for?
>
> Long-term support I'd guess (known from Ubuntu).

Right, I copied the Ubuntu term. I did not want to include a version number and chose this generic term.

Regards,
Kai
February 23, 2016
On Tuesday, 23 February 2016 at 16:59:25 UTC, Dan Olson wrote:
> Kai Nacke <kai@redstar.de> writes:
>
>> Hi everyone!
>>
>> I merged the merge-2.069 branch into master right now. We are approaching the next release very fast!
>>
>> Because the frontend is now written in D we Need a D Compiler to bootstrap. I moved the previous master to branch ltsmaster. This is the branch where we continue to maintain the C++ based version of LDC (release 0.17.x).
>>
>
> Nice and thanks.  I assume best practice for changes intended for both ltsmaster and master, do pull-request to ltsmaster first, then later merge into master?  I am thinking of my latest arm-linux changes.

Hi Dan!

This is the process we need to follow. All target architecture relevant changes (ARM, AArch64, etc.), LLVM updates and maybe bug fixes (#1224, #1292) should be developed first for ltsmaster.

Regards,
Kai


February 23, 2016
On Tuesday, 23 February 2016 at 20:11:42 UTC, Kai Nacke wrote:
> On Tuesday, 23 February 2016 at 16:59:25 UTC, Dan Olson wrote:
>> Nice and thanks.  I assume best practice for changes intended for both ltsmaster and master, do pull-request to ltsmaster first, then later merge into master?  I am thinking of my latest arm-linux changes.
>
> Hi Dan!
>
> This is the process we need to follow. All target architecture relevant changes (ARM, AArch64, etc.), LLVM updates and maybe bug fixes (#1224, #1292) should be developed first for ltsmaster.

Isn't the opposite usually done? Develop something for master, and backport to LTS ?
(perhaps less chance of introducing something bad in LTS?)
February 24, 2016
On Tuesday, 23 February 2016 at 05:51:01 UTC, Kai Nacke wrote:
> Hi everyone!
>
> I merged the merge-2.069 branch into master right now. We are approaching the next release very fast!
>
> Because the frontend is now written in D we Need a D Compiler to bootstrap. I moved the previous master to branch ltsmaster. This is the branch where we continue to maintain the C++ based version of LDC (release 0.17.x).
>
> Have fun!
>
> Regards,
> Kai

The speed of development of LDC is impressive, thank you Kai/LDC team.
February 24, 2016
On Tuesday, 23 February 2016 at 05:51:01 UTC, Kai Nacke wrote:
> Hi everyone!
>
> I merged the merge-2.069 branch into master right now. We are approaching the next release very fast!
>
> Because the frontend is now written in D we Need a D Compiler to bootstrap. I moved the previous master to branch ltsmaster. This is the branch where we continue to maintain the C++ based version of LDC (release 0.17.x).
>
> Have fun!
>
> Regards,
> Kai

Next version will be 1.0?
February 24, 2016
On Wednesday, 24 February 2016 at 05:25:33 UTC, rsw0x wrote:
> On Tuesday, 23 February 2016 at 05:51:01 UTC, Kai Nacke wrote:
>> Hi everyone!
>>
>> I merged the merge-2.069 branch into master right now. We are approaching the next release very fast!
>>
>> Because the frontend is now written in D we Need a D Compiler to bootstrap. I moved the previous master to branch ltsmaster. This is the branch where we continue to maintain the C++ based version of LDC (release 0.17.x).
>>
>> Have fun!
>>
>> Regards,
>> Kai
>
> The speed of development of LDC is impressive, thank you Kai/LDC team.

Thanks. It is the team which is doing the work behind the scenes.
I currently only create the releases and write the announcements...

Regards,
Kai
February 24, 2016
On Wednesday, 24 February 2016 at 06:24:58 UTC, Suliman wrote:
> On Tuesday, 23 February 2016 at 05:51:01 UTC, Kai Nacke wrote:
>> Hi everyone!
>>
>> I merged the merge-2.069 branch into master right now. We are approaching the next release very fast!
>>
>> Because the frontend is now written in D we Need a D Compiler to bootstrap. I moved the previous master to branch ltsmaster. This is the branch where we continue to maintain the C++ based version of LDC (release 0.17.x).
>>
>> Have fun!
>>
>> Regards,
>> Kai
>
> Next version will be 1.0?

Hi Suliman!

Yes, next version will be 1.0. This was discussed earlier in this forum.
The move to the D based frontend is a major milestone for this project.
Given the current shape of the project and the development activity right now, we are really ready for a 1.0 version. :-)

Regards,
Kai
« First   ‹ Prev
1 2 3