Preparing v1.1.0-incubating release #4080

Activity

1. bobbai00

   added the

   Task

   issue type on Nov 25, 2025
2. bobbai00

   added

   triage

   on Nov 25, 2025
3. bobbai00

   self-assigned this

   on Nov 25, 2025
4. github-actions

   removed

   triage

   on Nov 25, 2025
5. bobbai00

   added sub-issues on Nov 25, 2025

   • Create a CI to upload release candidates to dist.apache.org/repos/dist/dev/incubator/texera #4081
   • Bump versions in the sbt and image tags to v1.1.0-incubating #4082
   • bin/single-node is outdated, missing newly-introduced micro services #4083
   • Separate rpy2 dependency from releases due to GPL license incompatibility #4084
   • Load example datasets & workflows to dashboard #4085
6. Yicong-Huang commented on Nov 26, 2025

   

   Yicong-Huang

   on Nov 26, 2025

   Contributor

   More actions

   @bobbai00 I suggest also include #4079 on this target. any objections?
7. bobbai00

   added a sub-issue on Nov 28, 2025

   • Add support for Python 3.13 #4079
8. bobbai00 commented on Nov 28, 2025

   

   bobbai00

   on Nov 28, 2025

   ContributorAuthor

   More actions

   @bobbai00 I suggest also include #4079 on this target. any objections?

   Added
9. Yicong-Huang

   added a sub-issue on Dec 1, 2025

   • Re-package amber under texera #4003
10. bobbai00

    removed a sub-issue on Dec 5, 2025

    • Load example datasets & workflows to dashboard #4085
11. Yicong-Huang

    removed a sub-issue on Dec 8, 2025

    • Add support for Python 3.13 #4079
12. 6 remaining items

    Load more
13. pjfanning

    added a sub-issue on Apr 13, 2026

    • all docker images produced by Texera need to be have a license and notice that describes the contents of the image #4372
14. bobbai00 commented on Apr 16, 2026

    

    bobbai00

    on Apr 16, 2026

    Last edited by bobbai00

    ContributorAuthor

    More actions

    I would like to summarize the current roadmap of making the release compliance in terms of license.

    There are in total 3 steps. After these steps, Texera release should be fully compliant.

    Step 1 — Use compliant libraries in Texera itself

    Every direct dependency declared in Texera's build files must be Category A or Category B.

    The problematic package is mysql-connector-java, which is GPLv2 and
    is currently declared as a dependency of the MySQL source operator.

    This is tracked by #4393

    Step 2 — Ensure proper licensing for Texera's own jars

    Texera produces 12 jars. Each jar's META-INF/LICENSE must describe
    what is inside that specific jar, not what is in the full source tree.

    This is tracked by #4394.

    Step 3 — Make release artifacts compliant

    Texera releases Docker images as convenience binaries. A Docker image
    bundles roughly 450 third-party dependency jars alongside Texera's own
    jars, plus system packages from the base OS layer. Per ASF policy, the
    LICENSE file shipped inside each Docker image must describe everything
    it contains, not just Texera's own jars.

    This is tracked by #4396
15. bobbai00 commented on Apr 16, 2026

    

    bobbai00

    on Apr 16, 2026

    ContributorAuthor

    More actions

    Can @parshimers take a look at the above roadmap and see if my understanding is correct?
16. parshimers commented on Apr 16, 2026

    

    parshimers

    on Apr 16, 2026

    Member

    More actions

    I think that's generally right. I'm curious as to how #1 slipped by the release checks. I didn't see it in RAT either. For #2 I think we need the NOTICE and DISCLAIMER as well. For #3 I am unsure of how exactly to deal with it. Since other ASF projects ship containers, there must exist some base image that has compatible licenses for everything somehow.

    👍React with 👍1Reacted by Chen Li
17. bobbai00

    added sub-issues on Apr 22, 2026

    • Binary dist zips ship source-tree LICENSE / NOTICE instead of binary-specific files #4448
    • Build: per-module build.sbt files duplicate organization, version, and scalaVersion #4446
18. bobbai00

    removed a sub-issue on Apr 22, 2026

    • Binary dist zips ship source-tree LICENSE / NOTICE instead of binary-specific files #4448
19. bobbai00

    added sub-issues on May 3, 2026

    • Introduce a LLM Agent that helps users construct workflows #4034
    • HashJoin returns empty result via sync execution API #4576
    • Rename agent-service LOG_LEVEL to TEXERA_SERVICE_LOG_LEVEL for consistency #4574
    • Include LICENSE, NOTICE and DISCLAIMER in docker compose tarball #4847
    • Remove helm chart tarball from the releases artifacts #4848
20. bobbai00 commented on May 22, 2026

    

    bobbai00

    on May 22, 2026

    ContributorAuthor

    More actions

    v1.1.0-incubating is released officially ! Thanks everyone who participated in the release discussion and preparation!

    Here is the announcement email: https://lists.apache.org/thread/544qnl5wwtjgyk0vq7r7xw7fbngbpqvc

    🎉React with 🎉2Reacted by Yicong Huang and Chen Li
21. bobbai00

    closed this as completedon May 22, 2026
22. chenlica commented on May 23, 2026

    

    chenlica

    on May 23, 2026

    Contributor

    More actions

    Congratulations! Thanks for the great work!