>  I want to see the discussion on the dev mailing list.   I also want to
try
to clean the milestone 1 list as it stands now and add/remove things later
as needed.  We need one place where all the milestone 1 is managed and a
history of the management decisions are immutably preserved.

I believe the point is that the entire community is already discussing
these matters
on github issues/milestones/projects and so moving the discussion to the
mailing list is
going to cause duplication and confusion (and in my opinion, using github
for this
is far more productive/practical as a tool).

I don't have any problem with doing actual voting on the mailing list (for
obvious reasons).

On Wed, May 24, 2023 at 5:12 PM Claude Warren, Jr
<claude.war...@aiven.io.invalid> wrote:

> On Wed, May 24, 2023 at 3:53 PM PJ Fanning <fannin...@gmail.com> wrote:
>
> > Just a note but the issues in the 1.0.0 milestone are not the be all
> > and end all. We're still discovering new items that we need for a
> > 1.0.0 release. Have a look at the milestone [1] for the latest issues.
> >
> > I would really prefer if the relative merits of whether these are
> > blockers for 1.0.0 release are discussed on the individual issues in
> > GitHub instead of having one email thread that has many different
> > topics in it.
> >
> > [1]
> >
> https://github.com/apache/incubator-pekko/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0.0
> >
>
>  I want to see the discussion on the dev mailing list.   I also want to try
> to clean the milestone 1 list as it stands now and add/remove things later
> as needed.  We need one place where all the milestone 1 is managed and a
> history of the management decisions are immutably preserved.
>
> Please present a list of items that we need for a v1 release in an email so
> that we can all see what is missing.
>
> Claude
>


-- 

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:* matthew.dedetr...@aiven.io

Reply via email to