Release Candidate Testing

[Randall Leeds <ra...@apache.org>]

I've pushed an v0.1.0-rc.2 to npm@dev from the contents of master@aabae90
for testing.

  > npm install --save @annotator/selector@dev

Apologies for the churn on the branches and the commits. I made a few
errors getting the hang of the lerna publishing.

Re: Release Candidate Testing

[Randall Leeds <ra...@apache.org>]

I've been doing some more reading through the release procedures of other
projects and the ASF documentation.

I believe that what I've done here was atypical. What seems to be called a
release candidate by ASF projects should be something that is ready to be
released, tagged, uploaded to the staging artifact host, and then voted on.
It should have the final version number everywhere but the filenames.

Publishing release candidates will be a little tricky to manage with lerna
and npm, since lerna wants to commit the prelease identifier into source
while the ASF process would not have me do so.

What may end up happening is that we publish other prerelease versions for
developer feedback. We would reserve the -rc.X suffix for sanity checking
releases and voting, but would not publish these to the registry.

I am preparing the release process now:

- Add rules to the makefile for creating a proper release with signatures
and checksums.

- Determine how to interact with git and lerna as release manager;
determine when and how to create and publish tags, branches, artifacts, and
votes.

I should have this ready to go tomorrow and will post an official vote
thread, consistent with ASF practices for voting on release candidates.

On Thu, Jan 30, 2020, 21:42 Randall Leeds <ra...@apache.org> wrote:

> I've updated master with a Makefile. The dist target builds the release
> tarball artifact.
> I've also published this to v0.1.0-rc.3.
>
> The archive checks out with Apache Rat. The npm packages look right to me.
>
> I think the release process might be in in good shape at this point.
>
> On Thu, Jan 30, 2020 at 8:08 PM Randall Leeds <ra...@apache.org> wrote:
>
>> I've pushed an v0.1.0-rc.2 to npm@dev from the contents of master@aabae90
>> for testing.
>>
>>   > npm install --save @annotator/selector@dev
>>
>> Apologies for the churn on the branches and the commits. I made a few
>> errors getting the hang of the lerna publishing.
>>
>

Re: Release Candidate Testing

[Randall Leeds <ra...@apache.org>]

I've updated master with a Makefile. The dist target builds the release
tarball artifact.
I've also published this to v0.1.0-rc.3.

The archive checks out with Apache Rat. The npm packages look right to me.

I think the release process might be in in good shape at this point.

On Thu, Jan 30, 2020 at 8:08 PM Randall Leeds <ra...@apache.org> wrote:

> I've pushed an v0.1.0-rc.2 to npm@dev from the contents of master@aabae90
> for testing.
>
>   > npm install --save @annotator/selector@dev
>
> Apologies for the churn on the branches and the commits. I made a few
> errors getting the hang of the lerna publishing.
>