[jakartaee-tck-dev] When should we rename the TCKRefactor branch for EE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jakartaee-tck-dev] When should we rename the TCKRefactor branch for EE 11?

From: Scott Marlow <smarlow@xxxxxxxxxx>
Date: Fri, 1 Mar 2024 11:59:29 -0500
Delivered-to: jakartaee-tck-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jakartaee-tck-dev/>
List-help: <mailto:jakartaee-tck-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev>, <mailto:jakartaee-tck-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jakartaee-tck-dev>, <mailto:jakartaee-tck-dev-request@eclipse.org?subject=unsubscribe>

Hi,

When should we rename the https://github.com/jakartaee/platform-tck/tree/tckrefactor branch? Since we are already starting to use the `tckrefactor` branch to stage TCKs for EE 11, I wonder if we should rename the `tckrefactor` to `main` now and make that the default branch.

There will be work involved to bring `master` branch changes over to `main` but I see no way around that.

Scott

Follow-Ups:
- Re: [jakartaee-tck-dev] [External] : When should we rename the TCKRefactor branch for EE 11?
  - From: Lukas Jungmann
- Re: [jakartaee-tck-dev] When should we rename the TCKRefactor branch for EE 11?
  - From: Emily Jiang

Prev by Date: Re: [jakartaee-tck-dev] Our Platform TCK groupId is currently using `jakartatck`, should we change to `jakarta.tck`?
Next by Date: Re: [jakartaee-tck-dev] When should we rename the TCKRefactor branch for EE 11?
Previous by thread: [jakartaee-tck-dev] Fwd: [eclipse.org-committers] Compute cluster instability
Next by thread: Re: [jakartaee-tck-dev] When should we rename the TCKRefactor branch for EE 11?
Index(es):
- Date
- Thread

Breadcrumbs