Hi Dominic, I'll drop all the +1 I have on this ... I remember the things you need to do to be quite a few.
And keep in mind ... if you don't use the real disclaimer it's almost impossible to have your initiation irte: Justin voting -1 on your release ;-) But don't worry ... I know one other podling that made it without initiation and the way you are currently doing things, I could even imagine you do it too ;-) I intentionally verified the release as if you had the normal disclaimer but voted as you had the WIP ... I think I read other reviews too and you should have all the things listed that need addressing. Chris Am 02.06.20, 23:49 schrieb "Dominik Riemer" <[email protected]>: Hi again, a question related to our next release: For the last release, we used the Work-in-progress/WIP-Disclaimer [1] from the Apache Incubator, which makes releasing a bit easier as releases do not need to be fully compliant with ASF requirements. In the release vote, we got some comments on things that do not fully comply with the ASF release policy and most of them are already fixed (see Jira issues in [2,3]). We can switch to the standard disclaimer at any time, which potentially increases the risk for getting -1 release votes, but helps to learn about ASF policy requirements on releases. Before graduation, we need to show that we're able to make fully-ASF-compliant releases anyways. What do you think? Should we replace the WIP disclaimer [4] with the standard disclaimer in our Github repos? Dominik [1] https://incubator.apache.org/policy/incubation.html#work_in_progress_disclai mer [2] https://issues.apache.org/jira/browse/STREAMPIPES-137 [3] https://issues.apache.org/jira/browse/STREAMPIPES-138 [4] https://github.com/apache/incubator-streampipes/blob/dev/DISCLAIMER-WIP
