@jhamman & @shoyer - I think Xarray has a release frequency problem.

• 1782 has been merged, but I still can't plot timeseries with an all-nan step

• 1796, #1819, and #1893 have been merged - but I still can't plot RGB images

• 1840 has been merged - but loading CF-int-encoded data still uses double the memory it needs.

• All of these daily tasks for myself and my colleagues are harder than they should be.

It's been more than three months now without a patch release. This is really, really frustrating as an Xarray contributor, user, and advocate - getting my work merged upstream literally isn't worth anything until it's released, my colleagues have trouble using it (and go back to Matlab or IDL!), and it's harder to ask for anything in meetings with eg @opendatacube.

Moving to weekly patch releases would fix all of these problems.

Maintainer availability doesn't need to be a limiting factor, either - for example, @HypothesisWorks has a deployment pipeline where the only human involvement is to click 'merge', and I'd be happy to help out if you'd like to set up a similar system.