bsd-port repo organization
David Holmes
david.holmes at oracle.com
Fri Aug 29 05:29:47 UTC 2025
On 29/08/2025 3:41 am, Harald Eilertsen wrote:
> On Thu, Aug 28, 2025 at 10:59:25AM +1000, David Holmes wrote:
>> On 27/08/2025 8:01 pm, Harald Eilertsen wrote:
>>> The repo is set up so that the master branch automatically track the
>>> openjdk/jdk repo master branch, and from what I gather, the normal
>>> openjdk workflow for integrating merge requests into the master branch
>>> apply. I.e. merge requests in the bsd-repo will be integrated into the
>>> mainline jdk branch.
>>
>> That doesn't sound right to me. You merge your project master branch with
>> mainline jdk master but not the other way around. Any changes for JDK master
>> need to be done via PR on the mainline JDK repo.
>
> Thanks for clarifying, my misunderstadning.
>
>>> I'm not sure how important the JEP is if we add changes gradually, but
>>> I'm thinking it won't hurt.
>>
>> If there is a JEP for the port (as there should be) then you can't integrate
>> anything* until the JEP has been targeted to a particular release.
>
> That makes sense. Does that mean the entire change set will be merged at
> once, or do you still want smaller, self-contained changes?
The integration to mainline would take place all at once, but the
individual changes would be accumulated in the project repo.
David
More information about the bsd-port-dev
mailing list