Makes sense.

Setting up nexus takes a while, so I suggest that you log a JIRA task to work 
on it in the background. I’ve forgotten the precise steps, but an INFRA ticket 
is probably required.

Regarding the process, if you’re interested in what we do in Calcite, go to 
https://calcite.apache.org/docs/howto.html#making-a-release-for-calcite-committers
 
<https://calcite.apache.org/docs/howto.html#making-a-release-for-calcite-committers>
 and search for "Verify the staged artifacts”.

A lot of the functionality comes from using the Apache parent POM. See the 
following lines in Calcite’s pom.xml:

  <parent>
    <groupId>org.apache</groupId>
    <artifactId>apache</artifactId>
    <version>19</version>
  </parent>

So, you should consider using that parent POM in Crail. Again, not a trivial 
task.

Julian

 

> On May 7, 2018, at 7:41 AM, Jonas Pfefferle <[email protected]> wrote:
> 
> Ok, thanks. Let's skip maven central for now.
> I will call for an IPMC vote then.
> 
> Jonas
> 
> On Mon, 7 May 2018 07:33:14 -0700
> Julian Hyde <[email protected]> wrote:
>> Yes, if you want binary artifacts to be available from maven central, you 
>> need to stage the artifacts in nexus. They are reviewed during the vote. 
>> After the vote succeeds, you press a button and they appear on maven central.
>> If you do this, it will take a few days. Setting up a nexus account is a bit 
>> of hassle the first time. And I think you should re-run the vote on the PPMC 
>> list to include the artifacts, before you start the IPMC vote.
>> One option is to skip maven artifacts this release, and proceed immediately 
>> to an IPMC vote. Then you can make another release in a few weeks. I 
>> slightly favor this option. Releases should be easy and reproducible rather 
>> than perfect. Source-only releases are the easiest option at this point.
>> In any case, you may not get a choice. If the IPMC vote fails (and there’s a 
>> non-zero chance of that), you will find yourselves needing to roll a new RC 
>> and carry out a new vote anyway.
>> Julian
>>> On May 7, 2018, at 02:00, Patrick Stuedi <[email protected]> wrote:
>>> Luciano, Julian,
>>> Is the idea that we put the artifacts into a staging directory (for
>>> maven central?) prior to starting the IPMC vote?
>>> If not required, can we make the call the IPMC vote? Source release is
>>> prepared, PPMC vote has passed, so from our side everything is ready.
>>> Thanks,
>>> Patrick
>>>> On Mon, Apr 30, 2018 at 2:58 PM, Jonas Pfefferle <[email protected]> wrote:
>>>> I looked at the example of Toree. How can I stage artifacts at
>>>> https://repository.apache.org/content/repositories ?
>>>> I assume this is for maven central?
>>>> Thanks,
>>>> Jonas
>>>> On Fri, 27 Apr 2018 12:03:49 -0700
>>>> Luciano Resende <[email protected]> wrote:
>>>>> For the IPMC vote, it's very similar to this one, but you would add the
>>>>> link to this thread and another link to the result. You can see some
>>>>> examples at:
>>>>> https://lists.apache.org/[email protected]
>>>>> Also, you should have your result e-mail with a subject [RESULT].
>>>>> Thanks
>>>>> -- Luciano
>>>>>> On Fri, Apr 27, 2018 at 3:57 AM, Jonas Pfefferle <[email protected]> 
>>>>>> wrote:
>>>>>> I'm closing the PPMC vote now:
>>>>>> 5 + votes
>>>>>> 0 - votes
>>>>>> @Julian, Luciano How do we kick of the IPMC vote?
>>>>>> Thanks
>>>>>> Jonas
>>>>>> On Thu, 26 Apr 2018 17:19:03 +0200
>>>>>> "Jonas Pfefferle" <[email protected]> wrote:
>>>>>>> Thanks for the clarification. Let's wait until tomorrow to close the
>>>>>>> voting for the PPMC.
>>>>>>> Jonas
>>>>>>> On Thu, 26 Apr 2018 07:57:44 -0700
>>>>>>> Julian Hyde <[email protected]> wrote:
>>>>>>>> The “binding” thing is a bit confusing. Let me attempt to clarify.
>>>>>>>> The first vote is in the PPMC (podling PMC) and members of the PPMC
>>>>>>>> have
>>>>>>>> binding votes. That’s mentors plus initial committers - i.e. most folks
>>>>>>>> on
>>>>>>>> this list.
>>>>>>>> The second vote is by the incubator PMC. It starts only when the first
>>>>>>>> vote has passed. Only members of the IPMC have binding votes. That’s
>>>>>>>> your
>>>>>>>> mentors plus anyone else on the IPMC who takes an interest in voting.
>>>>>>>> Mentors’ votes cast during the first vote are generally carried forward
>>>>>>>> to
>>>>>>>> the second vote.
>>>>>>>> So, we already have enough PPMC votes for the first vote to pass. We
>>>>>>>> need to make sure the 72 hour minimum duration has passed (to give
>>>>>>>> everyone
>>>>>>>> opportunity to vote) before we close the vote. Then we should start the
>>>>>>>> vote in IPMC.
>>>>>>>> Julian
>>>>>>>>> On Apr 26, 2018, at 3:27 AM, bernard metzler <[email protected]> wrote:
>>>>>>>>> +1 (non-binding)
>>>>>>>>> Jonas,
>>>>>>>>> Many thanks for driving this release forward. Let's cross fingers
>>>>>>>>> we get all the binding votes needed ;)
>>>>>>>>> Luciano, Raphael - did you by any chance found the time to have
>>>>>>>>> Crail RC2 evaluated..? Thanks very much for your support!
>>>>>>>>> Cheers,
>>>>>>>>> Bernard.
>>>>>>>>>> On 4/26/2018 9:47, Jonas Pfefferle wrote:
>>>>>>>>>> Hi Julian,
>>>>>>>>>> Thanks for the vote.
>>>>>>>>>> I will link the key into the web of trust thing and I just fixed the
>>>>>>>>>> KEYS file (The "HOWTO" part is a shameless copy of gearpump's KEYS
>>>>>>>>>> file).
>>>>>>>>>> So current vote status is:
>>>>>>>>>> + 1 Binding vote by Julian Hyde
>>>>>>>>>> - 0
>>>>>>>>>> (+ 3 not binding)
>>>>>>>>>> Since we need another PMC meber to vote besides Julian and Luciano.
>>>>>>>>>> Has anyone heard from Raphael?
>>>>>>>>>> @Julian, Luciano is there any other PMC member you know we can ask to
>>>>>>>>>> vote for this release?
>>>>>>>>>> Thanks,
>>>>>>>>>> Jonas
>>>>>>>>>> On Wed, 25 Apr 2018 11:02:14 -0700
>>>>>>>>>> Julian Hyde <[email protected]> wrote:
>>>>>>>>>>> +1 (binding)
>>>>>>>>>>> Downloaded, checked signatures and checksums. Checked LICENSE,
>>>>>>>>>>> NOTICE, README.md, KEYS, headers, ran RAT. Built using JDK 8 on
>>>>>>>>>>> MacOS.
>>>>>>>>>>> One thing: The key is not linked into a web of trust[1]. It doesn’t
>>>>>>>>>>> have to happen before the release, and won’t alter the artifacts for
>>>>>>>>>>> this
>>>>>>>>>>> release, but let’s do it soon.
>>>>>>>>>>> Another minor thing: KEYS[2] mentions Gearpump at one point. I think
>>>>>>>>>>> you meant Crail! (The gpg “HOWTO” at the top of KEYS is most
>>>>>>>>>>> welcome.
>>>>>>>>>>> Thanks for that!)
>>>>>>>>>>> Julian
>>>>>>>>>>> [1] https://www.apache.org/dev/release-signing.html#link-into-wot <
>>>>>>>>>>> https://www.apache.org/dev/release-signing.html#link-into-wot>
>>>>>>>>>>> [2] https://dist.apache.org/repos/dist/release/incubator/crail/KEYS
>>>>>>>>>>> <
>>>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/crail/KEYS>
>>>>>>>>>>> On Apr 23, 2018, at 4:40 AM, Jonas Pfefferle <[email protected]>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>> I fixed all the comments from rc1 and created rc2:
>>>>>>>>>>>> * Add all three source download options in README (@Julian
>>>>>>>>>>>> requirements were already there)
>>>>>>>>>>>> * Fix NOTICE file to include actual year for Apache Software
>>>>>>>>>>>> Foundation
>>>>>>>>>>>> * Fix signatures
>>>>>>>>>>>> * Created KEYS file https://dist.apache.org/repos/
>>>>>>>>>>>> dist/release/incubator/crail/KEYS
>>>>>>>>>>>> Thanks to everyone who has contributed to this release.
>>>>>>>>>>>> You can read the release notes here:
>>>>>>>>>>>> https://github.com/apache/incubator-crail/blob/master/HISTORY.md
>>>>>>>>>>>> The commit to be voted upon:
>>>>>>>>>>>> https://git1-us-west.apache.org/repos/asf?p=incubator-crail.
>>>>>>>>>>>> git;a=commit;h=749f44206943fcaef0841ed89411013c2dc11d64
>>>>>>>>>>>> Its hash is 749f44206943fcaef0841ed89411013c2dc11d64.
>>>>>>>>>>>> The artifacts to be voted on are located here:
>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc2/
>>>>>>>>>>>> The hashes of the artifacts are as follows:
>>>>>>>>>>>> source.tar.gz.sha256 6900341d8d8347be71107fe8c76635
>>>>>>>>>>>> 8b587d96a3e505cd501f6d0d8690a3f3c7
>>>>>>>>>>>> source.zip.sha256 51c2b11658e70ef0b7a80c427d88ee
>>>>>>>>>>>> 1a928fae8499f3910fe9bcc89a6fcfa5e3
>>>>>>>>>>>> Release artifacts are signed with the following key:
>>>>>>>>>>>> https://people.apache.org/keys/committer/pepperjo.asc
>>>>>>>>>>>> Please vote on releasing this package as Apache Crail 1.0
>>>>>>>>>>>> incubating.
>>>>>>>>>>>> The vote is open for the next 72 hours and passes if a majority of
>>>>>>>>>>>> at least three +1 PMC votes are cast.
>>>>>>>>>>>> [ ] +1 Release this package as Apache Crail 1.0 incubating
>>>>>>>>>>>> [ ] 0 I don't feel strongly about it, but I'm okay with the release
>>>>>>>>>>>> [ ] -1 Do not release this package because...
>>>>>>>>>>>> Here is my vote:
>>>>>>>>>>>> +1
>>>>>>>>>>>> Jonas
>>>>> --
>>>>> Luciano Resende
>>>>> http://twitter.com/lresende1975
>>>>> http://lresende.blogspot.com/
> 

Reply via email to