Giters

etcd-io / raft

Raft library for maintaining a replicated state machine

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Plan to release raft 3.6.0

ahrtr opened this issue · comments

commented

Plan to formally release raft 3.6.0 sometime in the following 1 ~ 2 months, so that users can depend on a tagged version instead of a commit.

Please advise what features should be included in raft 3.6.0.

We also need to cut a branch something like release-3.6 (raft 3.6.0 should be released based on this branch), and it only accepts bug fixes afterwards. Any new features should only go into the main branch after we release 3.6.0.

commented

Rough plan:

  • Release 3.6.0-alpha.0. Will not cut branch, and it will be released against the main branch.
    • Please advise what need to be resolved before we release 3.6.0-alpha.0.
  • Continuously testing raft 3.6.0-alpha.0 in etcd.
  • [Optional] Release 3.6.0-beta.X if there are any major issues.
  • Cut branch release-3.6 and release 3.6.0-rc.X or 3.6.0.
commented

Was asked in #110 (comment) to comment here:

In #110, we're removing the main use of Progress.PendingSnapshot, but we should keep the field and tracking in place until 4.0 for backwards compatibility reasons since Progress is a public API. We should also make some other, related cleanups to the snapshot logic and APIs while we're at it, I'll write up a placeholder issue shortly.

commented

I am planning to create tag 3.6.0-alpha.0 this week per plan above #89 (comment). Please let me know if anyone has any comment or concern.

commented

Tag v3.6.0-alpha.0 was just created.

commented

Is the release done, or we can still make small changes?

I'd like to add the check (2) from #138 (see Action Items), so that in future releases we can finish the fix. Not doing it now will postpone the end-goal fix by another release.

The change will be simple: #139.

commented

Is the release done, or we can still make small changes?

As mentioned in #89 (comment), we just created a tag 3.6.0-alpha.0, and haven't cut branch release-3.6 yet. It's still open for new changes in 3.6, but not for any breaking change, and try not add major changes in 3.6 either.