There is a place to discuss whether an issue should be in a milestone - the issue itself.
I also believe it is completely impractical to vote on every item before we work on it. It will take months or years to get the release done. There have been hundreds of changes made and reviewed across all our repos in the last few months. There are people waiting for us to get releases out. There are developers working long hours to get this done. If you think anything that was committed should not have been committed, raise an issue to get it reverted and it can be discussed. If you want to propose rules that we should abide by, go ahead. If they are accepted by the PPMC, then they will be followed. Usually in OSS, it is the active developers who make the decisions on the ways things are done. I have seen no Pekko PPMC members making suggestions that the current practices are incorrect. On Sun, 28 May 2023 at 09:41, Claude Warren, Jr <[email protected]> wrote: > > My discussion was not about how to develop or direction for each issue but > whether each issues belongs in the milestone. There is no other place to > discuss the milestone and what goes in it. Since there was not a lot of > discussion on the milestone contents I felt that taking a line item vote > would be good to surface any cases where there were issues with what should > be in the milestone. > > I also don't think that things should be added or removed from the > milestone without a discussion and vote. > > > On Sat, May 27, 2023 at 5:58 PM PJ Fanning <[email protected]> wrote: > > > I agree with Matthew. I believe the issues should be discussed > > individually in the comments on the issues themselves. > > > > My opinion is that where there are differences in opinions in these > > comments and that we need some mechanism to decide on which way to go, that > > a Vote thread is then useful. > > > > We have already closed off some issues and dropped others from the > > milestone. > > > > We are getting close to a release and we are discovering a lot of issues > > with the technicalities of making the release. Getting involved in voting > > on all of these issues will slow down the whole process. > > > > On 2023/05/24 15:40:01 Matthew Benedict de Detrich wrote: > > > If we are talking about the milestone generally and voting then it's > > clear > > > that this can be discussed on the mailing list. I was referring to > > > individual > > > discussion of issues in a milestone which is what I also believe PJ > > Fanning > > > was referring to. > > > > > > On Wed, May 24, 2023 at 5:28 PM Claude Warren, Jr > > > <[email protected]> wrote: > > > > > > > The milestone itself [1] does not have any way to discuss the > > milestone as > > > > a single entity. There is no place where all discussion about what > > should > > > > go into (or be taken out of) the milestone occurs. Each ticket in the > > > > milestone has its discussion space. But the milestone itself does not. > > > > Thus my desire to have discussions about what goes into or come out of > > the > > > > milestone to be held on the dev list. > > > > > > > > > > > > [1] https://github.com/apache/incubator-pekko/milestone/1 > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Matthew de Detrich > > > > > > *Aiven Deutschland GmbH* > > > > > > Immanuelkirchstraße 26, 10405 Berlin > > > > > > Amtsgericht Charlottenburg, HRB 209739 B > > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > > > > > *m:* +491603708037 > > > > > > *w:* aiven.io *e:* [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
