Publish release 0.2.0

[chalin]

Hopefully, we'll be able to close a few more of the 22Q1 milestone items before the release.

• For items that need to be completed first, see Docsy as a Hugo module #849
  • Create extra tag dependencies/v0.2.0
• Add CHANGELOG to track when features were added, dependencies updated, etc. #831
• Update version in package.json - NPM package: change version to 0.2.0 #961
• Link to Getting-started page gives 404 #960

[chalin]

Done: https://github.com/google/docsy/releases/tag/v0.2.0

[chalin]

Also closing:

• https://github.com/google/docsy/milestone/2
• Use Go/Hugo-friendly git tags #954

[chalin]

@deining - I also created tag dependencies/v0.2.0

[chalin]

@LisaFC @emckean @geriom: FYI, for this first time, I decided to use GH's autogenerated release details.

[chalin]

@deining - I also created tag dependencies/v0.2.0

Oops, somehow I had the wrong commit. That is fixed now:

[deining]

@deining - I also created tag dependencies/v0.2.0

Duhh, the go.mod of the commit with tag 0.2.0 now still points to dependencies/v0.2.0-pre, which is a bit unfortunate:

docsy/go.mod

Lines 5 to 9 in f7b37a0

	require (
	github.com/FortAwesome/Font-Awesome v0.0.0-20210804190922-7d3d774145ac // indirect
	github.com/google/docsy/dependencies v0.2.0-pre // indirect
	github.com/twbs/bootstrap v4.6.1+incompatible // indirect
	)

We should have corrected this first in a new commit and then tagged this commit, I guess. This way, the tags for modules docsy and docsy/dependencies are in sync.

Anyway, our actions crossed and I just updated #849. This issue mentions a few items that need to be addressed IMHO.

[chalin]

@deining - Thanks for the updated notes. We're still learning. I've deleted the release and will start again tomorrow or Wednesday (I don't have time tonight). Could you make the updates you mention in the previous comment? Sorry to all for the fuss. I'm sure that it'll go better the next time around.

[deining]

@deining - Thanks for the updated notes. We're still learning.

That's very true!

I've deleted the release and will start again tomorrow or Wednesday (I don't have time tonight). Could you make the updates you mention in the previous comment?

Done with #958.

I will go through the whole documented installation process tomorrow to make sure everything works as expected.

I'm sure that it'll go better the next time around.

Yes, certainly!

[deining]

I double checked all module installation methods and made some minor improvements on the way, see #958. For me, everything ran smoothly and worked out as expected.
I also updated the checklist in #849, this tickets now lists everything that needs to be done to get v0.2.0 out eventually.

Looking forward to the release of version v0.2.0!

[spacefan]

Looking forward to the release of version v0.2.0 too!

[chalin]

@deining - wonderful! Thank you for #958 and for double checking the instructions. I've left some comments/questions in my review feedback.

[chalin]

Ok, I've merged #958 and other 0.2.0-release related PRs. Anything else to do before I create the release @deining?

[deining]

Anything else to do before I create the release

No, there's nothing that I'm aware of. I think we are now ready to assign tags v0.2.0 and dependencies/v0.2.0 to commit ID 18a7df2 (created when #958 was merged). Then you can create the release based on tag v0.2.0.

[chalin]

Tags created (from the current HEAD).

[chalin]

Released: https://github.com/google/docsy/releases/tag/v0.2.0 🤞