To hammer home my point: the fact that the production of release artifacts (at least everything except for GPG signing them and uploading to SVN) is something you are not confident that you can do is a symptom of the mess that we are in. We need to make the PMC-requiring aspects of the release process as trivial and unobtrusive to the PMC members as possible. Otherwise you are competing for an extraordinarily scarce resource.
The appropriate step at this stage is to fix the broken process — if we accede to your request and cut a release a month ahead of schedule, what is to stop the status quo from continuing indefinitely? On Mon, Nov 23, 2020 at 6:23 PM Charlene Solonynka <csolony...@dremio.com> wrote: > Hi Wes. I haven’t tried running through the full release process, I > believe there are some steps that I am not allowed to do; but I can spend > today and tomorrow looking at them and see if there is anything that I have > particular difficulties with. > -- > Charlene Solonynka > M: 778-903-3124 • E: csolony...@dremio.com > <https://hello.dremio.com/email-signature-url> > <https://hello.dremio.com/email-signature-url> > > On Nov 23, 2020, at 10:06 AM, Wes McKinney <wesmck...@gmail.com> wrote: > > hi Charlene, > > I think if you can resolve the issues we have raised with the Java > release process and better automate the production of all the release > artifacts (so that there is less time commitment required for the RM), > then we may be able to release in December. Otherwise, I am not sure > it's possible (that is, if you're expecting someone from Ursa Labs or > Kou to be the RM). Have you tried running through the full release > process with the RM hat on to better understand why we don't want to > cut more frequent releases? > > Thanks > > Wes > > On Mon, Nov 23, 2020 at 11:43 AM Charlene Solonynka > <charle...@bitquilltech.com> wrote: > > > Hi Wes and Neal. > > We would really like to get a release of Arrow Flight for December and not > wait until January. We have a release of our Endpoint on December 16th > which requires the merged authentication and cookie changes below. There > are a couple of additional tickets which are still in progress for > c++/python as well;. We are willing to do whatever is needed to get an > earlier release. > https://github.com/apache/arrow/pull/8554 < > https://github.com/apache/arrow/pull/8554> > https://github.com/apache/arrow/pull/7994 < > https://github.com/apache/arrow/pull/7994> > We are also currently developing the above changes in c++/python. > > As mentioned below, there are 3 tickets open. If we resolve these issues; > can we get a release sooner? Are there any other tasks that need to be done? > https://issues.apache.org/jira/browse/ARROW-6103 < > https://issues.apache.org/jira/browse/ARROW-6103> I am not sure what > needs to be done here as this seems to be a question rather than an action > https://issues.apache.org/jira/browse/ARROW-1234 > https://issues.apache.org/jira/browse/ARROW-10648 > Would it be possible to meet to discuss this? I am free in the following > time blocks, but if another time works for you, I will make myself > available. > > November 23, 3:00-4:00 PM PST > November 24, 10:00-11:00 AM PST > November 24, 4:00-5:00 PM PST > November 25, any time after 1:00 PM PST. > > I will also be at the Apache Arrow Sync on Wednesday. > > Regards, Charlene Solonynka > > -- > Charlene Solonynka > Development Manager > Bit Quill Technologies Inc. > Office: +1.778.331.3355 | Direct: +1.778.903.3124 | > charle...@bitquilltech.com <mailto:charle...@bitquilltech.com> > https://www.bitquilltech.com <https://bitquilltech.com/> > > This email message is for the sole use of the intended recipient(s) and > may contain confidential and privileged information. Any unauthorized > review, use, disclosure, or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy > all copies of the original message. Thank you. > > >
