GitHub release model.

[Marcus Hirt]

Yep. Personally I'd prefer a single repo and branches too. Anyone else
wanna weigh in? Are we missing anything?

Kind regards,
Marcus

On Tue, Oct 6, 2020 at 4:14 PM Guru <guru.hb at oracle.com> wrote:

> Hi Marcus and Mario,
>
> "OpenJDK creating a new repo for each release” : This is due to the LTS
> and Non-LTS model, where LTS Model will have
> https://github.com/openjdk/jdk11u and Non LTS model :
> https://github.com/openjdk/jdk13u , https://github.com/openjdk/jdk15u and
> https://github.com/openjdk/jdk14u , etc.
>
> Where as for JMC we could have Single Repository "
> https://github.com/openjdk/jmc” with
> a. Main release — Separate branch as and when we release (i.e JMC8, JMC9,
> …)
> b. Minor release — Tags (i.e JMC-8.0.0, JMC-8.0.1,...)
>
> This will make easier to manage compared to multiple repo and This is the
> model which is used in https://github.com/openjdk/jfx (OpenJFX).
>
> Thanks,
> Guru
>
> On 06-Oct-2020, at 6:52 PM, Marcus Hirt <marcus.hirt at datadoghq.com> wrote:
>
> Hi Mario,
>
> OpenJDK is creating a new repo for each release. That's a bit clunky, and a
> decision that seems to be mostly based on "not changing too much at the
> same time". With branches we can create new ones on our own. With new repos
> we can't.
>
> Kind regards,
> Marcus
>
> On Tue, Oct 6, 2020 at 2:54 PM Mario Torre <neugens at redhat.com> wrote:
>
> 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
>
>
>
>