Reorganize Documents: Latest Entries First #26
Conversation
|
Hi @thesurenk, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user thesurenk" as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
|
❗ This change is not yet ready to be integrated. |
Completed this on 2/21/2025 |
|
@thesurenk Thanks for this PR. Can you follow the instructions above regarding signing the OCA? Then I can sponsor your PR. Thanks! |
|
/signed |
|
Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated! |
I signed the contract on 2/21/2025 but forgot to send the "/signed" comment. Sent that now. Hope that is good to move forward? |
Should be. Just need it to get processed...hopefully won't take too long. |
|
As a heads up, my OCA took a long time to get approved (well past a month). I would email them if a month goes by, and there is still no response from anyone. |
Thank you, sending them an email. |
|
@thesurenk This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
|
Status shows " OCA signatory status must be verified", not sure what are the next steps or who i can reach to? |
|
Another email is about all you can do, really. Again, it took months for
mine to go through, so unfortunately, this is not surprising.
…On Mon, Apr 14, 2025, 12:07 PM Suren K ***@***.***> wrote:
Status shows " OCA signatory status must be verified", not sure what are
the next steps or who i can reach to?
I sent another email to OCA team.
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJFR6SA7OBMQCTKAUGULJA32ZPMMTAVCNFSM6AAAAABXUAPKAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBSGIYDEOJQGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
*thesurenk* left a comment (openjdk/amber-docs#26)
<#26 (comment)>
Status shows " OCA signatory status must be verified", not sure what are
the next steps or who i can reach to?
I sent another email to OCA team.
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJFR6SA7OBMQCTKAUGULJA32ZPMMTAVCNFSM6AAAAABXUAPKAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBSGIYDEOJQGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
As of now on the home page https://openjdk.org/projects/amber/ , Documents section lists are mostly ordered as oldest-latest month-year.
It would be best to have them as Latest-On-Top.
Other OpenJDK projects like https://openjdk.org/projects/babylon/ also use the same approach.
Progress
Error
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/amber-docs.git pull/26/head:pull/26$ git checkout pull/26Update a local copy of the PR:
$ git checkout pull/26$ git pull https://git.openjdk.org/amber-docs.git pull/26/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26View PR using the GUI difftool:
$ git pr show -t 26Using diff file
Download this PR as a diff file:
https://git.openjdk.org/amber-docs/pull/26.diff