Thanks for the explanation -- that's super helpful!

On Fri, Feb 21, 2020 at 1:58 PM Trevor Grant <trevor.d.gr...@gmail.com> wrote:
>
> I agree- having tested builds as well as having been RM.
>
> tg
>
>
> On Fri, Feb 21, 2020 at 3:37 PM Steve Blackmon <sblack...@apache.org> wrote:
>>
>> Roman,
>>
>> Replying to your question from the Feb board minutes:
>>
>> >
>> > rs: It would be great to see more details on how the upcoming
>> > release is progressing and if there's anything that's blocking
>> > it.
>>
>> The last several times I’ve tried to perform a release, I’ve gotten bogged 
>> down in the sheer number of integration tests and how many prerequisites 
>> must be present to get them all to pass at once.  The development 
>> environment has to have many active account credentials, non expired, all in 
>> the right place in working copy, many docker containers running, enough 
>> system resources for 8 concurrent containers and the build, and still get a 
>> bit lucky.
>>
>> I think we’ve reached the point where its no longer reasonable to expect a 
>> release voter or the release manager to observe all the ITs under the 
>> contrib module tree passing in one execution.  As such I’m inclined to 
>> reconfigure our reactor and failsafe plugin and reactor such that 
>> integration tests under streams-contrib no longer run except by specific 
>> request, and only one module at a time - i.e. if you want to extend and 
>> integration test the Facebook module, set up your environment to do so and 
>> run those tests standalone rather than as part of a full build.
>>
>> dev@streams is cc’ed here.  Does anyone want to agree or not agree with this 
>> approach, and/or add your experience or ideas to the conversation?
>>
>> Steve
>>
>> P.S. With an adjustment like this made, I am confident we could cut a new 
>> release and complete a new release vote this quarter.
>>
>> On Feb 19, 2020, 2:15 PM -0600, Matt Sicker <mattsic...@apache.org>, wrote:
>> > Comments:
>> >
>> > rs: It would be great to see more details on how the upcoming
>> > release is progressing and if there's anything that's blocking
>> > it.
>>
>> > da: There has been a theme of low activity, you say "Mailing list
>> > and commit participation was low again. Adding committers and
>> > growing the PMC needs to be a focus". Do you have any specific
>> > ideas to tackle this?
>> >
>> > druggeri: Please include the date of the last committer addition as
>> > well. The reporter tool can help facilitate this.
>> >
>> > This feedback was generated automatically by the secretary from the
>> > comments made on your board report.
>> > Comments that do not ask specific questions should be noted by the PMC
>> > and taken into consideration as appropriate for future board reports.
>> > Where a comment asks a specific question, it should be answered in your
>> > next board report unless otherwise stated in the comment.
>> > If you have any queries or concerns regarding any of the comments they
>> > should be sent to the board@ mailing list.

Reply via email to