I look into that breakout (see other mail) so we can do that before 1.0.0

- Sebastian

On 2026/07/27 12:54:37 Christofer Dutz wrote:
> Hi Sebastian,
> 
> How about we address that after the release of 1.0.0?
> Or you do the heavy lifting of implementing that in the next week or so?
> 
> This is the last step of the NLNet funded research work I’m doing.
> I’m not planning to re-implement the code generation for all of our other 
> language modules if this work is not funded by anyone.
> 
> Chris
> 
> 
> Von: Sebastian Rühl <[email protected]>
> Datum: Montag, 27. Juli 2026 um 13:12
> An: [email protected] <[email protected]>
> Betreff: Re: Preparing to start the release-train...
> 
> I would like to have the repo split per language in it. Currently tags are 
> unusable for Golang for example. Maybe we can do that before the 1.0.0 
> otherwise the v1 release will stay unusable and that would be sad.
> 
> - Sebastian
> 
> On 2026/07/27 10:07:17 Christofer Dutz wrote:
> > Hi all,
> >
> > After coming back from lunch, I’m planning to cut a release for the 
> > build-tools … I don’t expect anyone to be working on that.
> >
> > However once that release is out the door, the next repo on the schedule 
> > will be the 1.0.0 of PLC4X … so please raise your hand if you need 
> > something in there and need some more time than let’s say a week?
> >
> > Chris
> >
> 

Reply via email to