Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Release Schedule 1.5 #4744

Closed
Closed
@OceanWolf

Description

@OceanWolf

As my first time going through a point release, and with less than two weeks until 1.5, I wondered about the release schedule. As the mailing list has gone down, I started an issue to discuss this.

I presume it will go something like:

  1. a v1.5 branch gets created from master, i.e. we implement a code-freeze for 1.5
  2. we then start removing commits from the 1.5 branch that we don't consider stable, i.e. things in master that we discover aren't as stable as we thought when we first merged them and thus needs holding back until v2.1.
  3. once we feel confident about the 1.5 release, we release.

So question, when does step 1 occur, and how long between step 1. and step 3.?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp