Hi everyone,
Can you please review the Release notes attached?
I tried to aggregate everything together, but since I recently joined
the team, I may miss something :)
Thanks!
Em seg., 19 de jun. de 2023 às 14:48, Alexander Alten <[email protected]>
escreveu:
> Awesome, and merged!
>
> > On 19. Jun 2023, at 15:36, Gláucia Esppenchutz <[email protected]>
> wrote:
> >
> > Hi everyone,
> >
> > Update on this:
> > - Made some docs about the contribution and small changes on README.md
> > - I was investing some time reading the Apache release docs and found
> out I
> > was missing some steps.
> > - I was recommended to use the maven-release-plugin, and will try it
> later
> > today :)
> >
> > I give more updates about it soon!
> >
> > Em sex., 16 de jun. de 2023 às 17:21, Kaustubh Beedkar <
> [email protected]>
> > escreveu:
> >
> >> +1 on that.
> >>
> >> Best,
> >> Kaustubh
> >>
> >>
> >>
> >> On Fri, Jun 16, 2023, 21:10 Zoi Kaoudi <[email protected]>
> wrote:
> >>
> >>> No objections from me either. Please go ahead and thanks a lot for the
> >>> efforts :)
> >>>
> >>> Best
> >>> --
> >>> Zoi
> >>>
> >>> Στις Παρασκευή 16 Ιουνίου 2023 στις 12:44:18 μ.μ. CEST, ο χρήστης
> >>> Alexander Alten-Lorenz <[email protected]> έγραψε:
> >>>
> >>> Hey Glaucia,
> >>>
> >>> +1
> >>>
> >>> Thank you,
> >>> —Alex
> >>>
> >>> Sent from my iPhone
> >>>
> >>>> On 16. Jun 2023, at 11:27, Gláucia Esppenchutz <[email protected]
> >
> >>> wrote:
> >>>>
> >>>>
> >>>> Hi everyone,
> >>>>
> >>>> I was revisiting the good practices of releases and want to align with
> >>> you if it is the same thing Apache recommends because looking at the
> >> Apache
> >>> Release pages focuses on the artifacts uploaded on the Apache websites.
> >>>>
> >>>>
> >>>>
> >>>> The idea is the release/release-tag uses the development branch to
> >>> select the PRs or commits to create the release and merge it into the
> >> main.
> >>>> If we use this good practice, we need to avoid merging things on main
> >>> branch and only merge PRs into develop. (Sorry if it is a noob comment!
> >>> This is the first time I have done an RM, but I am enjoying it a lot
> :) )
> >>>> If everyone agrees on it, I can add this a note on the Contributing
> >> docs
> >>> or create a CONTRIBUTE.MD file with clear instructions.
> >>>>
> >>>> Let me know what you think, and if everyone approves, I will do it
> >>> immediately.
> >>>>
> >>>> Glaucia
> >>>
> >>> --
> >>> databloom AI, Inc.
> >>>
> >>> 3401 N. MIAMI AVE. STE 230
> >>> 33127 Miami, Florida
> >>> United States
> >>>
> >>>
> >>> -- Please consider the environment before printing this
> >>> email --
> >>>
> >>>
> >>>
> >>> Disclaimer:
> >>> The content of this message is confidential. If you
> >>> have received it by mistake, please inform us by an email reply and
> then
> >>> delete the message. It is forbidden to copy, forward, or in any way
> >> reveal
> >>> the contents of this message to anyone. The integrity and security of
> >> this
> >>> email cannot be guaranteed over the Internet. Therefore, the sender
> will
> >>> not be held liable for any damage caused by the message.
> >>>
> >>>
> >>
> >
> >
> > --
> > Gláucia Esppenchutz
> >
> > -----------------------------------------------------
> > Twitter: @lyuric19
> > Linkedin:
> https://www.google.com/url?q=https://br.linkedin.com/pub/gl%25C3%25A1ucia-esppenchutz/47/81a/312&source=gmail-imap&ust=1687786661000000&usg=AOvVaw39cpVv1IEfRTOo5BnDA01W
>
>
> --
> databloom AI, Inc.
>
> 3401 N. MIAMI AVE. STE 230
> 33127 Miami, Florida
> United States
>
>
> -- Please consider the environment before printing this
> email --
>
>
>
> Disclaimer:
> The content of this message is confidential. If you
> have received it by mistake, please inform us by an email reply and then
> delete the message. It is forbidden to copy, forward, or in any way reveal
> the contents of this message to anyone. The integrity and security of this
> email cannot be guaranteed over the Internet. Therefore, the sender will
> not be held liable for any damage caused by the message.
>
>
--
Gláucia Esppenchutz
-----------------------------------------------------
Twitter: @lyuric19
Linkedin: https://br.linkedin.com/pub/gláucia-esppenchutz/47/81a/312
==============================================================
Apache Wayang (incubating) 1.0.0
==============================================================
This is the first official major release of Apache Wayang (incubating).
This release supports the following frameworks:
TODO: Check the frameworks below
- Apache Flink v1.7.1
- Apache Giraph v1.2.0-hadoop2
- GraphChi v0.2.2 (only available with scala 11.x)
- Java Streams (version depends on the java version)
- JDBC-Template
- Postgres v9.4.1208 (Implementation JDBC-Template)
- Apache Spark v3.1.2 (scala 12.x) and v2.4.8 (scala 11.x)
- SQLite3 v3.8.11.2 (implementation JDBC-Template)
NOTE: depending on the scala version the list of the supported platforms
available
could be different.
New Features
------------
[WAYANG-34] Terasort
[WAYANG-IDE] Recognition of Scala code in IDE
[WAYANG-8] Inclusion of Python as platform of processing
[WAYANG-211] JVM-platform inside of Python-API
[WAYANG-273] - WebUI Draft
Grep Benchmark
Test classes and operators for Flink
Support for S3 files locations
Initial version of the SQL API and suppport for joins
Incompatible changes
--------------------
TODO: Check if something here is missing
Miscellaneous changes
---------------------
Updates in documentation files:
- README.md
- NOTICE
- DISCLAIMER.md
- Usage instructions
- Add EPL and PD license
CI updates:
- Protoc
- Skywalking-eyes check
- Deadlink check
- CodeQl Check
- UT check
- Auto Build And Install
- Create Issues from the TODO in the code
- Removed Travis, added Apache Calcite
Update maven-wrapper to 3.1.0, maven to 3.8.4 for performance improvements
Update .dlc.json
Updates for monitoring the runtime metrics of underlying platform (Spark)
[WAYANG-47] Properties Spark 2.11 updated with Spark version
Known Issues
------------
TODO: Check if something here is missing
Bug Fixes
---------
Delete paranamer-2.3 from dependecies (PR#76)
Code scanning alert (PR#80)
Correction in DistinctOperator for Apache Flink (PR#226)
Fix of broken links
Fix on WayangJoinVisitor
Concat strings vulnerability
[WAYANG-assembly] correction in the folder structure (PR#259)
[WAYANG-48] Fix errors when running WordCount
New Contributors
---------
* @chrisdutz made their first contribution in
https://github.com/apache/incubator-wayang/pull/1
* @2pk03 made their first contribution in
https://github.com/apache/incubator-wayang/pull/8
* @ggevay made their first contribution in
https://github.com/apache/incubator-wayang/pull/27
* @CalvinKirs made their first contribution in
https://github.com/apache/incubator-wayang/pull/44
* @hboutemy made their first contribution in
https://github.com/apache/incubator-wayang/pull/77
* @regaleo605 made their first contribution in
https://github.com/apache/incubator-wayang/pull/78
* @zkaoudi made their first contribution in
https://github.com/apache/incubator-wayang/pull/230
* @JorgeQuiane made their first contribution in
https://github.com/apache/incubator-wayang/pull/231
* @kbeedkar made their first contribution in
https://github.com/apache/incubator-wayang/pull/284
* @bgeng777 made their first contribution in
https://github.com/apache/incubator-wayang/pull/301
* @damik3 made their first contribution in
https://github.com/apache/incubator-wayang/pull/304
* @kmoltke made their first contribution in
https://github.com/apache/incubator-wayang/pull/309
* @michellesackmann made their first contribution in
https://github.com/apache/incubator-wayang/pull/310
* @AdeelAslamUnimore made their first contribution in
https://github.com/apache/incubator-wayang/pull/311
* @ichbinrich made their first contribution in
https://github.com/apache/incubator-wayang/pull/315