[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipselink-dev] Which branch for bugfixes?
- From: Alexander Lehmann <a.lehm@xxxxxx>
- Date: Wed, 13 Feb 2019 06:27:43 +0100
- Delivered-to: email@example.com
Thank your for your fast reply. This should suffice to make me able to submit the patch.
What's funny is: When I was trying to make the patch yesterday I already thought: "This would be much easier if eclipselink had a github repo". Could it be that there is no hint to github on the project website yet?
Woops, forgot to answer your specific questions!
I recommend you fix the issue in the `master` branch and then create a port for the same fix back to the `2.7` branch. If it gets code reviewed and merged, it'll get in the next 2.7 release (perhaps someone else can chime in on when that is expected to be).
For testing, I would recommend creating a simple test in the `eclipselink.jpa.test.jse` project. You should be able to take a look at similar tests in that project and create a new package (would these be PostgreSQL specific tests?) or find similar tests and add yours in.
Also, that wiki includes instructions on pulling down/setting up your fork and setting up a workspace so that you can more easily submit PRs! Hope this helps!
eclipselink-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit