dpol1 opened a new pull request, #2318:
URL: https://github.com/apache/stormcrawler/pull/2318

   Hi folks, with 4.0 around the corner, I thought it was worth spending some 
time on the migration guide. While I was at it, I also fixed dead links, 
outdated examples and inconsistencies in the docs.
   
   I'd appreciate a read through the migration guide in particular. Please let 
me know if anything is missing or unclear, especially for configurations or 
custom components I may have overlooked.
   
   The CloudSearch entries cover the removal proposed in #2317.
   
   We'll update the Storm requirements and related instructions once #2316 
lands.
   
   cc @jnioche @rzo1 @mvolikas @sebastian-nagel 
   
   ### For all changes
   
   - [ ] Is there a issue associated with this PR? Is it referenced in the 
commit message?
   
   - [ ] Does your PR title start with `#XXXX` where `XXXX` is the issue number 
you are trying to resolve?
   
   - [x] Has your PR been rebased against the latest commit within the target 
branch (typically main)?
   
   - [ ] Is your initial contribution a single, squashed commit?
   
   - [x] Is the code properly formatted with `mvn git-code-format:format-code 
-Dgcf.globPattern="**/*" -Dskip.format.code=false`?
   
   ### For code changes
   
   - [ ] Have you ensured that the full suite of tests is executed via `mvn 
clean verify`?
   - [ ] Have you written or updated unit tests to verify your changes?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file?
   - [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to