[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] Example spec release schedules
|
The plan is independent of the ballot until the last stage. The start of a spec represents:
1. creating a staging release
2. Creating a PR indicating it is ready for staging (and possibly a ballot)
At the end of the period, the staging release api jar needs to be usable by downstream dependencies so that they can update their poms and do a staging release.
A 14 day ballot can start anytime during or after the staging release task.
> On Jul 22, 2019, at 4:32 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>
> I think I'm still missing something basic...
>
> What's supposed to be happening during the start/end time for a spec?
> Staging occurs? PR is submitted? Balloting starts and ends?
>
> Is this still assuming a 7 day ballot period?
>
>
> Scott Stark wrote on 7/22/19 4:10 PM:
>> The plan is a worst case staging plan that has the ultimate dependencies being the platform specs staged in time to just complete the two week ballot. The calendar in the program was not including weekends, so after changing that setting the plan has the platform specs being stage complete by Aug 26. If the ballot were started at the start of staging, that would easily give three weeks for ballot completion by Sep 10.
>>
>> The stages are what is required simply for dependencies. Both Stage0 and Stage(-1) can start anytime. The other are based on dependencies, but I am figuring that we will be reviewing sets of staged PRs twice a week until complete, so that Stages also provide a rough schedule of what should be reviewed for ability to be used by the following stages dependencies.
>>
>> Voting could be delayed until the final the start of the platform specs staging period starting on Aug 20, which would give 3 weeks until the Sep 10 target release date.
>>
>> Voting could also be kicked off as soon as the spec committee is confident a staging PR is ready. I would think that we would want to take this approach to to finalize as many specs and TCKs as quickly as possible.
>>
>>
>>
