Greetings,
I think that it is time to start to take a hard look at a release candidate. I do not expect the release candidate to succeed, however, there is a lot to be learned in the failure. There is a milestone [1] currently open. Let's take that and work toward the release candidate. I think we should start by determining if there are items that are not required for the release and items that are missing. I am opening two issues today that I will add to the milestone. They are the addition of the LICENSE and NOTICE files to the snapshots, under the assumption that doing so will also add them to the release. Let's clean the list and then concentrate on only those items that will get us to RC1. So let's hold a vote on the items in the current milestone and see if they all need to be in release 1.0 In this process we will need to ensure that everyone is communicating what they are doing. So, I think we should do the following: 1. do not work on a change without a ticket. 2. make sure the ticket is associated with the milestone. 3. when you are working on a ticket, assign it to yourself. If you can not assign it to yourself, post a note on the dev mailing list with a subject prefix of [ACCESS] noting the ticket that you do not have access to and then add a comment to the ticket indicating that you are working on it. 4. any change that is not a simple break/fix should be discussed in the dev mail list with the subject prefix of [DISUCSS]. We should also be looking on the dev list for offers of assistance and point them to the milestone first. We need to develop standard operating procedures that are welcoming to new contributors. [1] https://github.com/apache/incubator-pekko/milestone/1
