3.0 milestone?

[siennathesane]

There are two cards, #204 and #181, which reference the 3.0.0 milestone. There are a couple open issues with proposed API changes that we could also put into 3.0, that way we're making API changes on a major release.

Do we have an idea of what we want 3.0 to look like? Now there are enough open suggestions and cards, it might be good to finalize what we want 3.0 to look like so we can let those open issues start moving forward without a minor release.

// cc @cristaloleg @janisz

[cristaloleg]

I don't yet. Probably we can coop on something and try to figure out, what can we make.

[siennathesane]

I think it would be good to list out some issues we think are good candidates for v3 as a starting point, interface changes, new interfaces, etc.

For sure I want these *four:

• Persistence #204
• Go defaults to "0"" so in case we want to return #181
• FeatureRequest: provide PinnedSlice or something to avoid memmove #230
• FeatureRequest: provide a way to reuse byte slice allocated in readEntry #229

Are there any others you can think of @cristaloleg?