Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jaxrs-dev] "Sandbox" branches created for 2.1.1-SNAPSHOT, 2.2-SNAPSHOT, 3-SNAPSHOT / Tagged Oracle's initial contribution

+1 for sandbox banch protection.

 

-Markus

 

 

From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth
Sent: Sonntag, 18. Februar 2018 14:53
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] "Sandbox" branches created for 2.1.1-SNAPSHOT, 2.2-SNAPSHOT, 3-SNAPSHOT / Tagged Oracle's initial contribution

 

Hi Markus,

 

thanks a lot for preparing the sandbox branches.

 

One thing I would like to note: What do you think about enabling branch protection also for the "sandbox" branches? I absolutely agree with you that direct commits to these branches must not happen and that all changes should be integrated via pull requests. I just wonder if we shouldn't enforce this pattern by marking the branches as "protected" on GitHub.

 

Christian

 

2018-02-18 14:16 GMT+01:00 Markus KARG <markus@xxxxxxxxxxxxxxx>:

Contributors and Fellow Committers,

 

in compliance with the EE4J PMC's recent PMC statement about initial EE4J project contributions  (https://www.eclipse.org/ee4j/news/?date=2018-02-16) I just created the needed "Sandbox" branches as announced earlier this week:

 

·        Branch 2.1.1-SNAPSHOT - Bug fixes and clarifications only. No feature changes. Must stay JAX-RS 2.1 compatible.

 

·        Branch 2.2-SNAPSHOT - New features ontop of JAX-RS 2.1 / Java EE 8. Must stay backwards compatible to JAX-RS 2.1, hence only adds features but does not drop or change old ones. Deprecation of old features has to happen here.

 

·        Branch 3-SNAPSHOT - Incompatible changes / feature removals only here.

 

·        Tag initial-contribution - Oracle's initial contribution in case someone needs to look it up one day.

 

Please always discuss first in a Github issue.

 

Please do not directly commit to any branch, but always open a PR and let at least one other committer review your changes.

 

Please do not open a PR against branch master, but always open a PR against one of the above branches.

 

Looking forward to review your PRs! :-)

 

-Markus

 


_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev



 

--


Back to the top