[jakartabatch-dev] Branch strategy for now

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

[jakartabatch-dev] Branch strategy for now

From: "Scott Kurz" <skurz@xxxxxxxxxx>
Date: Fri, 13 Mar 2020 08:47:05 -0500
Delivered-to: jakartabatch-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jakartabatch-dev>
List-help: <mailto:jakartabatch-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakartabatch-dev>, <mailto:jakartabatch-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jakartabatch-dev>, <mailto:jakartabatch-dev-request@eclipse.org?subject=unsubscribe>

Thanks Romain for the generics PR:
https://github.com/eclipse-ee4j/batch-api/pull/18

My first thought is to just leave it as a PR for now to review/discuss.

When the time comes that we want to build on top of it we can decide on a branching flow... e.g. maybe we'll be done with EE 9 and just merge into master, or, if we want to sooner we can propose another branching flow.

------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------

Follow-Ups:
- Re: [jakartabatch-dev] Branch strategy for now
  - From: Romain Manni-Bucau

Prev by Date: Re: [jakartabatch-dev] Generics need to move post-EE9
Next by Date: Re: [jakartabatch-dev] Branch strategy for now
Previous by thread: [jakartabatch-dev] Proposal: give more control over jobcontroller queue(s)
Next by thread: Re: [jakartabatch-dev] Branch strategy for now
Index(es):
- Date
- Thread

Breadcrumbs