One good preparation would be for all to do full builds: with-cpp,with-python,with-dotnet,with-proxies,with-sandbox ... One person did report having problems. Would like to find out why.
Chris Outlook für Android<https://aka.ms/ghei36> herunterladen ________________________________ From: Tim Mitsch <[email protected]> Sent: Monday, May 6, 2019 12:31:43 AM To: [email protected] Subject: Re: [DISCUSSION] Release 0.4 Hey everybody, full ack ... a soon release shall be done, as we have enough stuff that could be released. I can do the release as i got a great introduction of how to do it with 0.3.1 by Julian, thanks for that btw. But i think Chris has the honor to decide if he wants to do the first Release of PLC4X matured to TLP - would love to support I think end of this or beginning of next week could be a good date for a 0.4.0-RC1 Best Tim Am 05.05.19, 21:04 schrieb "Christofer Dutz" <[email protected]>: Hi all, I also think we should do a release soon. Especially for making a first tlp release. Regarding the RM, I would like to actually perform the technical release this time. I'm quite sure I changed the graduation related stuff correctly, but with all this super special additional stuff (CPP, C#, Python, Thrift) I am sorry of expecting bumps on the road. I'm fine with Tim doing the paperwork, if he wants to ;-) Chris Outlook für Android<https://aka.ms/ghei36> herunterladen ________________________________ From: Julian Feinauer <[email protected]> Sent: Sunday, May 5, 2019 7:52:31 PM To: [email protected] Subject: [DISCUSSION] Release 0.4 Hi all, we also had a short discussion about the next release of PLC4X but I guess the best place is the list. So I think we should start very soon with the preparation of a new release. I also think we should include some of the very recent things (Python, CPP) but explicitly flag them as experimental feature. So we can give them out to others but with a clear disclaimer that this is more a “play around” thing. And we are free to target the next release “soon” to add some more things. I see that there are a lot of “small” improvements which we really should get out, and I would also love to start collecting feedback for the “experimental” stuff. Another question that came up was who will be RM. Tim already volunteered for that, and I absolutely support that to further diversify the RMs. But as the build recently changed it could be a bit complicated so Chris offered to do it this time. I cannot say what is the best solution but leave it up to everybody. Perhaps a solution would be to have Tim “manage” it and prepare everything and then do the maven related stuff with supervision from chris or by chris. By doing this he gets at least a good knowledge of the process around (branching strat, vote preparation and so). What are your opinions? I think we could target something like the end of next week for an RC. Julian
