GitHub release model.

[Mario Torre]

What's the model used by OpenJDK?

I think it makes sense to use the same so we have a consistent process.

Personally, I do prefer multiple separate explicit repositories, but
that's just me. There's not much difference between having in tree
branches and explicit forks really anyway. I agree on the tagging in
either case.

Cheers,
Mario

On Tue, Oct 6, 2020 at 2:49 PM Marcus Hirt <marcus.hirt at datadoghq.com> wrote:
>
> Hi all,
>
> It's time we start considering how we want to manage the source across
> releases. One model that looks attractive is what is done in the JavaFX
> project. We'll branch for major releases and tag commits in those branches
> for our actual releases.
>
> If this is not enough, and we ever feel the need to work on several minor
> releases in parallel for a specific major release, we could create branches
> as needed from the major release branches.
>
> We could name the branches jmc7, jmc8 etc. And yep, we could fold in the
> jmc7 repo being ported to GitHub into a jmc7 branch in the jmc repo and
> retire the jmc7 repo.
>
> What do you think?
>
> Kind regards,
> Marcus
>


-- 
Mario Torre
Associate Manager, Software Engineering
Red Hat GmbH <https://www.redhat.com>
9704 A60C B4BE A8B8 0F30  9205 5D7E 4952 3F65 7898