Worklist for 20.2

• Publish first version of NGNext as NG7.
  • Adapt buildscript where needed
  • Disable Configuration-Cache, it is not supported by TC
  • Add toolchains to tests
• Create tasks that build both the installer and the userdev
  • Create a decently useable DSL
  • Create a default setup within DynamicProjects
• Prepare for initial release
  • Update current 20.2 work to use NG7 (Need to ask schurli for source of the fork branch)
  • Fix NeoForge testmods
  • Squash all commits (Technici4n)
    • Fix datagen difference
  • Fix NG Runs when running with IDEs
    • Fix eclipse run directories
    • Fix Run with IDEA run directories
    • Shorten Command Line somehow?
      • IDEA
      • Eclipse
    • Fix handling of the assets and natives directories
  • Fix cache busting on Execute tasks, Decompile does not run when changing ATs
  • Fix licenser not being config cache capable and add it as a task
  • Update libraries to neoforged variants (and create if not exists)
    • accesstransformers
    • eventbus -> bus
    • forgespi
    • coremods
    • unsafe (won't be updated)
    • mergetool
    • JarJarSelector
    • JarJarMetadata
    • Test that the updated libraries still work (Technici4n)
  • NeoForge changes
    • Repackage FML
    • Repackage NeoForge
    • Change modid and built files to neoforge
    • Test that the game is still runnable
      • Forgedev
      • Prod client
      • Prod server
      • Userdev client
      • Userdev server
      • Userdev datagen
      • Userdev gametest
    • Change IForgeXXX to IXXXExtension
    • Rename other classes with Forge in their name
    • Update all resources except tags to the neoforge: namespace
      • Decide on a general policy for backwards compatibility
      • Add aliases for the old forge: entries?
    • Misc fixes
      • Fix mods screen (can't find forge)
      • Loading error screen is missing textures
  • Make GradleUtils ready for publishing
    • Fix and publish licenser fork
    • Fix GU configuration cache
    • Add NeoForge versioning support to GU
  • Make TC build and publish the NG_7.0 branch
  • Prepare renaming script
  • Prepare a blog post
    • General info
    • List of package and Forge changes
    • Event bus changes post
  • Make NeoForge ready to accept contributions
    • Licensing
    • Formatting
    • CI Checks
      • Do we need checkAt, checkExc, etc… back?: Orion: For now no. We will see what we need.
  • NG Mixin PR
  • Publish NG with non-snapshot versioning
  • Update MDK
  • Update NG in Kits and remove includeBuild
  • Tag the latest Kits commit as 20.2 (tag -a 20.2 -m "20.2 Release" for example)
  • Publish Kits to NeoForge public repo (remember the tag: git push --follow-tags)
  • Final touches to the blog post (see TODOs in the source)
• Post release changes
  • Consider what to do with networking
    • Registries need to go into the config phase for sure
    • Implement Protocol changes? Technically not needed, but do we want to be nice and implement modmusses proposal regardless?
  • Port the capabilities changes (Technici4n)
  • Port the registry changes (Shadows)
• Work on the installer
  • Prepare Den
  • Define Installer Modules RFC
    • There are different streams within the community that are pushing for different things. To prevent another version fiasco we should make up our minds as maintainers and then publish some RFC on Den
  • Create new Installer
• Extend NG7 Platform system with manageable DSL for platform projects
  • Create the PR validation framework