I suggest we create a jira for specific change so we can track the changes.
You can request access to jira and create a ticket yourself to be used for
your pr.
https://issues.apache.org/jira/projects/GEODE/issues/GEODE-7254?filter=allopenissues
Sai
On Mon, Oct 21, 2024, 10:35 PM Sanjay Yadav wr
Thank you Sai Boorlagadda for guidance, links were super helpful.
I will run all the tests and raise PR if it is small fix, should I use any
jira as such from my git branch?
Thank You,
Sanjay Yadav
On Tue, Oct 22, 2024 at 9:00 AM Sai Boorlagadda
wrote:
> Hi Sanjay,
>
> I would like to underst
Hi Sanjay,
I would like to understand where you are in setup? Are you able to checkout
the code and build?
I would say 'Geode in 5 minutes' is a great start and from there Testing.md
shows how to run each tests, while building.md shows how to setup project
and build in ide such as intellij.
>Fro
Hi Kirk/Team,
I am new to the ecosystem and would like to help with the above items but
not sure where to start ?
Please discount my naive question ? How can I mirror the
environment before raising PR's addressing above ?
Thank You,
Sanjay Yadav
On Tue, Oct 22, 2024 at 4:32 AM Kirk Lund wrote
Hi,
In my opinion the minimum needed to get Geode PRs flowing so that CVEs can
be addressed for a new release:
- automated build for PRs that has multiple pipelines
1. compile with unit tests
2. integration tests per module that depends on compile with unit tests
3. distributed tests per module t
> On Oct 20, 2024, at 3:28 AM, Sai Boorlagadda
> wrote:
>
> I pushed a commit to asf-site and the website is deployed now. Verified new
> links are working.
>
> There was a Dockerfile to build using nanoc and then the contents have to
> be copied from build folder to the asf-site branch.
Gre
