Hi
A previous discussion on this said that ICLAs were required for 3 people [1]
Kind Regards,
Justin
1. https://lists.apache.org/thread/f3zj445thvm4btrf4jxdho0ojh1zm4wb
Hi,
> Sorry - the contractor thing is my speculation. Laurent simply stated
> "[...]the individuals mentioned in the ip review at
> https://incubator.apache.org/ip-clearance/arrow-flight-sql-odbc.html do not
> hold rights over the code as they were employed by Dremio at that time". They
> used
Hi,
I can also see that the Apache license was added later, so the code wasn’t
initially under the Apache license. But I’ve not seen which contributors might
be impacted by that.
The license was added 3 years ago (June 2022), and the copyright in the headers
is " Copyright (C) 2020-2022 Dremi
Hi,
> Yes, Laurent Goujon stated to me they were all employed by Dremio at the time
> (*possibly as contractors, from what I understand).
Contractors may retain IP rights, it is for instance, the default under
Australian law. Do we have anything more than that to go on?
Kind Regards,
Justin
--
HI,
> - Dremio has informed me (in a private email exchange) that they hold all
> rights to the code to be donated and they believe contributor ICLAs are
> unnecessary.
Did Dremio say why they hold all rights to the code? Being on an open-source
project on GitHub doesn't guarantee that. I can
Hi,
> Good catch for DISCLAIMER, I forgot to include it, I will do it. Does
> it mean that all jar files should include DISCLAIMER (not sure
> podlings are doing that) ?
I don't think it needs to be included in all jar files, but there no harm if
you do that.
> For LICENSE and NOTICE, it's a mi
Hi,
> A few files you mention are not pure code copied, it's probably inspired but
> not full copy.
Other files were "inspired by” or changed significantly or were simple, so I
didn't list them. For those files, it was between 60% and 95% copied.
Kind Regards,
Justin
--
Hi,
It looks like a few more third-party files not mentioned in the LICENSE may
also have incorrect headers.
Looks like these files are from Nessie:
./build-logic/src/main/kotlin/copiedcode/CopiedCodeCheckerPlugin.kt
./build-logic/src/main/kotlin/copiedcode/CopiedCodeCheckerExtension.kt
./build-
Hi,
> Do you think what's provided in
> https://issues.apache.org/jira/browse/LEGAL-684 is accurate/complete ?
Yes, and it follows the advice in [1]
> Specifically, as the how-to states: "Do not add anything to NOTICE
> which is not legally required." So, if those dependencies have
> third-party
Hi,
> 1. about Iceberg and Nessie NOTICE, during the 0.9.0 vote, you asked
> to remove it explicitly.
I’d suggested that unneeded parts of the NOTICE file be removed, not the entire
contents. See [1]
> Are you now asking to add it (as I did
> initially) ? And Iceberg NOTICE is not required as i
Hi,
> The NOTICE contains the Picocli NOTICE, mentioning:
>
> | This project includes one or more documentation files from OpenJDK,
> licensed under GPL v2 with Classpath Exception.
> |
> | These files are included in the source distributions, not in the
> binary distributions of this project.
>
Hi,
-1 (binding) form me.
I checked:
- incubating in name
- signatures and hashes are file
- LICENSE is missing one file, but give the header issue, other 3rd party files
may not be listed.
- NOTICE is misisng information from Iceberg NOTICE file and Project Nessie
NOTICE file.
- Non-ASF 3rd pa
Hi,
The vote passes with 19 +1 IPMC votes and no -1 votes.
+1 IPMC votes:
Justin Mclean
Paul King
Calvin Kirs
Nicholas Jiang
Furkan Kamaci
Charles Zhang
Yonik Seeley
Shao Feng Shi
Kent Yao
Xun Liu
Jerry Shao
PJ Fanning
Ayush Saxena
Jean-Baptiste Onofré
Junping Du
Xin Wang
Wei-Chiu Chuang
Yu Xiao
Hi,
> I’m on vacation this week and pouchdb is still in the project-setup phase,
> so not much to report yet. Would it be okay to submit our first report
> next month?
New projects are expected to report every month for the first three months. Can
someone else fill in the report for you?
It wou
HI,
Podling reports are due today, and we are still missing:
- annotator
- cloudberry
- devlake
- fury
- hamilton
- horaedb
- iggy
- ponymail
- pouchdb
- resilientdb
- seata
- texera
- training
Kind Regards,
Justin
-
To unsubscr
Hi,
While there hasn't been much feedback on the discussion thread, there have been
no objections and a week has passed, so I’m starting a vote for Apache
Gravitino.
There is a discussion thread at:
https://lists.apache.org/thread/ohnpz35wmc5xkgc3fyz6zs0vvtgm9gqk
Our self-assessment/maturity m
Hi,
I’ve created a draft proposal here [1] to graduate at the next board meeting,
and if there are no other comments, I’ll start a vote in the next couple of
days.
Kind Regards,
Justin
1. https://whimsy.apache.org/board/agenda/2025-05-21/Establish-Gravitino
Hi,
The votes passes with 3 +1 binding IPMC votes and no -1 votes.
Binding +1 votes include:
- Justin Mclean
- Shaofeng Shi
- Jerry Shao
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
Hi,
>> The KEYS file to verify the release can be found here:
>> https://dist.apache.org/repos/dist/release/incubator/gravitino/KEYS
>
> The KEYS link should point to downloads.a.o.
The KEYS file can be found at
https://downloads.apache.org/incubator/gravitino/KEYS and is identical to the
abov
Hi,
Apache Gravitino entered the Incubator in June 2024 and has since then has made
steady progress toward operating in the Apache Way. Given the project was
started by people with experience in other ASF projects and who are ASF
members, that’s not much of a surprise.
The project has:
- Addi
Hi,
This is a vote for Apache Gravitino 0.8.1 incubating release. The PPMC vote
can be found here [1][2]/
The commit hash is 949237c, and is tagged v0.8.1-incubating-rc5.
The release artifacts can be found in the official ASF release area:
https://dist.apache.org/repos/dist/dev/incubator/gravi
Hi,
We generally go on the starting month, and it normally roughly evens out. We’ve
rebalanced what podlings report in what months, but that’s not a hard thing to
do, and it's only happened once that I can recall.
Choosing a random month causes odd reporting patterns, which in the past
podling
Hi,
>> In summary, I think podlings SHOULD perform a ASF name search before
>> entering incubation, but that's not a MUST.
That was my concern as well, and the wording has been changed to reflect that.
i.e. Podlings are encouraged to do this before entering teh Incubator, but they
don’t have to
HI,
> I, on behalf of the contributors, confirmed that we agree to the license
> change.
We need a bit more than that. Can we see where all of the contribitors have
agreed to this?
As a first step, can you supply a list of all contributors and whether they
were employed by OpenClovis? As PJ
Hi,
-1 (binding), as issues mentioned in the last release vote were not fixed. The
NOTICE file contains unnecessary duplicated lines [1], and there are files
mentioned in LICENSE that do not exist in the source release.
The NOTICE files don't need to contain the full NOTICE for other ASF produc
Hi,
If contacted via email, I usually include the cookbook link and links to other
policies or pages depending on what I think the project may have an issue with;
for some, that branding; for others, that’s releases; for others, community
building.
But it has often started as a face-to-face co
Hi,
The distribution page [1] exists because it was approved by a previous board,
and projects needed more guidance than was in the current distribution policy.
[2]
I woudl be fine with teh content at [1] being moved to [2].
Kind Regards,
Justin
1. https://incubator.apache.org/guides/distribu
Hi,
> The Incubator should not have parallel policies that may lag behind the
> official policies.
>
>>> * https://incubator.apache.org/guides/releasemanagement.html
>>>
>>> Somehow we have too many pages tell different part of truth. Before I
>>> knew there is something about KEYS, closer.lua,
Hi,
The incubator isn’t creating any new policy here. We need to follow what M&P
comes up with and ensure podlings know about it. The current policy is here
[1], if you want to discuss the changes, bring that up in the draft document or
board list [2], M&P are unlikely to see the conversation h
Hi,
There’s a discussion on the board list about using "creator of Apache Foo”. [1]
Also, see the current policy on it. [2] (i.e “original creator” can be used,
not “creator” but even that is discouraged.)
We could possibly add an extra item to the maturity model [3] along the lines
of “TB50.
Hi,
Teaclave have confirmed they are working toward graduation.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
Given they have missing reports, I'll take a role call and see where that puts
us.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incuba
Hi,
Given they have missing reports, I'll take a role call and see where that puts
us.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incuba
Hi,
So far, I've had no repose from:
- Toree
- Annotator
- Livy
- NLPCraft
Can the mentors of these projects please prompt them to respond.
Considering retirement:
- Nemo
Moving forward towards graduation:
- Training
- Pegasus
- Wayang
I'm unsure about Teaclave.
Kind Regards,
Justin
Hi,
Yesterday, I went over the projects that have been in the incubator for too
long to see where they were. I’ve sent them an email to focus on graduation or
retirement.
Here’s the list:
Toree 2015
Annotator 2016 - last report suggests they will retire
Livy 2017
Nemo 2018 - discussing possibl
Hi,
The Pony Mail project has been incubating since 2016 and lately has failed to
submit its reports. The PPMC is struggling to attract people and only has two
or three active people on it. We have discussed this project before but haven't
concluded what to do with it. It is a mature project th
Hi,
I also note that a couple of incubating projects have done this because they
thought the name might not be accepted. [1][2] In short, nothing is stopping
new incubating projects from already doing this.
Kind Regards,
Justin
1. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-228
2.
Hi,
While I have nothing against this idea, podlings rarely get security reports,
and most never get them. Even if it occurred a few times a year, do we want to
task all podlings this?
Kind Regards,
Justin
> On 19 Mar 2025, at 2:07 AM, Shane Curcuru wrote:
>
> PJ Fanning wrote on 3/6/25 10:0
Hi,
One thing, well two, actually. I didn’t see in the document if the name is a
registered trademark, and will OpenClovis keep using SAFplus to refer to other
products?
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-un
Hi,
One thing, well two, actually. I didn’t see in the document if the name is a
registered trademark, and will OpenClovis keep using SAFplus to refer to other
products?
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-un
Hi,
Looking at the first propopal, I was surprised to discover https://www.kie.org/
- having a domain name like this is not in line with ASF trademark policy, nor
is having a domain name like https://kogito.kie.org/. There are other trademark
issues with those site(s), I trust the PPMC is aware
Hi,
>> Both Baremaps and Uniffle are in group 3, so they need to report yes.
No need to report to the Incubator but you'll need to report to the board. New
TLP report monthly for 3 months to the board.
Thanks,
Justin
-
To unsub
Hi,
Both Baremaps and Uniffle are in group 3, so they need to report yes.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
HI,
StormCrawler is in group 1, which usually reports January, April, July and
October. I’m not sure why it was listed here as it’s not listed as monthly in
podlings.xml, The email script takes info from the generated
shepherd_assignments.json file which has that project listed, so perhaps ther
HI Dave,
This email was generated by a script. I assume that some data the script relies
on has not been updated.
Justin
> On 3 Mar 2025, at 2:22 PM, jmcl...@apache.org wrote:
>
> Dates for next board report:
> Wed March 05 - Podling reports due by end of day
> Sun March 09 - Shepherd reviews
Hi,
>> 2. The license will need to change after you become an ASF project but you
>> also won't be able to use any GPL licensed libraries in the project either.
>> Have you done an audit of how hard these changes will be?
>>
> [Hung] Yes, we agree that the license needs to change after we become
Hi,
Three people is quite a low number for the initial committer list - are there
not more people you can invite?
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e
Hi,
The Fury project uses a standard disclaimer, not a work-in-progress disclaimer.
The Gravitino project uses a WIP disclaimer and includes a reason for using it.
The text for the two disclaimers is different and can be found here. [1] The
disclaimer in Polaris is called “DISCLAIMER-WIP” but d
Hi,
+1 (binding) jmclean (IPMC)
I checked:
- incubating in name
- signatures and hashes are fine
- DISCLAIMER exists
- LICENSE is good (but lists non-existent v8-fast-api-calls.h)
- NOTICE is OK, but the multiple "This product includes software developed at
The Apache Software Foundation (http:/
Hi,
-1 (binding) jmclean (IPMC) as the DISCLAIMER text is incorrect
I checked:
- incubating in name
- signature and hashes are correct
- DISCLAIMER_WIP exists but doesn't contain the correct WIP text. It is unclear
why the WIP disclaimer is used here, which is its main purpose.
- LICENSE is OK
-
Hi,
> Could you share a link to one of the previous report?
Here’s one:
https://svn.apache.org/repos/private/foundation/board/archived_agendas/board_agenda_2024_06_19.txt
See Attachment AG.
> I checked that folder but didn't see a dedicated IPMC report. Or do
> you mean directly updating the bo
HI,
> Could you share a link to one of the previous report?
>
> I checked that folder but didn't see a dedicated IPMC report. Or do
> you mean directly updating the board Meeting Agenda [2]?
I usually submit the report via Whimsy (in the board agenda tool), which checks
it into SVN. When that h
Hi,
> I'm starting this thread to discuss whether it is a good idea to migrate the
> incubator report workflow to a GitHub-based system. Our current workflow is
> Confluence-based and involves many manual tasks. I also find Confluence
> difficult to use, and several other IPMC members seem to s
Hi,
> It could be that the stubs are generated by the python scripts in
> incubator svn but that the reports are not now committed to svn and
> just appear in cwiki.
The final report, which may differ slightly from the one in the wiki, is
submitted to the board and stored in SVN. [1]
Kind Regar
Hi,
Thanks for doing that PJ, I’ve updated the formatting and corrected the podling
list that need to report this month and sent out the notification emails.
You can access the step needed by running “report_runbook.py”.
Kind Regards,
Justin
Hi,
> OK, thanks for the prompt reminder, I will avoid including jar files with
> license type X in my distributions.
You need to do more than that, you can’t have them as a dependency.
Kind Regards,
Justin
-
To unsubscribe, e-
Hi,
Please don't use ChatGPT or similar to respond to emails.
Re your points:
1. Doesn’t answer the question I asked.
2. Please talk to Infra about the size of the file, they may be able to help.
4. This doesn’t solve the issue, and it is still an issue.
Kind Regards,
Justin
Hi,
> By the way, I will deal with the LGPL license issue next. If I only rely on
> the jar based on the LGPL license in the pom file of the project, and do not
> directly embed its class files in the project, such as MariaDB dependency is
> only used as a database driver reference, I understan
Hi,
-1 binding jmclean (IPMC) due to issues with the binary release, the source
release looks fine.
In the source release, I checked:
- incubating in names
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- signatures and hashes are fine
- all ASF files have headers
- no unexpected binary files
Hi,
There is no requirement for including “Apache" in an artifact release name
(see, for example [1]). Including it might be a good idea as it might provide
some legal protection.
Kind Regards,
Justin
1. https://incubator.apache.org/guides/distribution.html
Hi,
+1 (binding) jmclean carried over from dev list.
There were a couple of very minor issues that GitHub issues have been opened.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For addi
Hi,
> This is a reminder that the VOTE for the release of Apache OzHera
> (incubating) version 2.2.5-incubating-rc4 is still open. The vote
> was initiated on 2025/01/14, but we have not received sufficient feedback yet.
Have you asked your mentors to vote, or did any vote on your list?
Kind
Hi,
> Don’t you mean SGA (and not CCLA)?
We would also require an SGA. DAGWorks may want to submit a CCLA, but you are
correct in that we don’t require one.
Kind Regards,
Justin
Hi,
> 2. Question, does the whole repository need the same license? e.g.
> including documentation and examples?
It would be preferable to re-license as many files as possible to the Apache
license, but ASF projects can include 3rd party code under a compatible license
like BSD.
> 4. Segmentin
Hi,
> 1. Are there any requirements for the documentation directory structure
> under the website?
No, that is up to the project to decide.
> 2. Are there any requirements for the document generation tool?
Not really, unless the output is under a license not compatible with the Apache
license
HI,
> Maybe the members could put them somewhere readily accessible and links in
> the Incubator intro docs.
I’m unaware of any scripts besides Apache Rat, but if anyone else has one,
please speak up. The presentation “\How to Get Your Release Through the
Incubator” is linked to from the front
HI,
> Recent posts [1] have accused Apache of being rigid, dogmatic. These
> criticisms are, in my opinion, totally valid. And they matter, because we are
> losing projects to other foundations. We are no longer the only bar in town
> [2].
We don't actively seek out projects, projects that wan
Hi,
If you don't have active mentors, perhaps you should replace the inactive ones?
Asking here on the list might attract some more mentors.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
Hi,
> I will add the left licenses in the licenses-binary. Some licenses are the
> same so I don't add it before.
Licenses like the MIT license include a copyright line, and in general, they
are different from each other, so the full text needs to be included.
Kind Regards,
Justin
-
Hi,
+1 (binding) jmclean (IPMC)
I checked in the source release:
- incubating in the artifact name
- signature and hashes are fine
- LICENSE is fine
- NOTICE should not have "Copyright 2022 and onwards”
- DISCLAIMER exits
- All ASF file have ASF headers
- No unexpected binary files
The binary f
HI,
Sorry, but it is still -1 (binding) jmclean (IPMC).
The release contains a Blogger Template Style called Thisaway (Blue) designed
by Dan Rubin. [1] How is this licensed? Should this file have an ASF header? It
is also unclear how this file is licensed [2]. Should it have an ASF header?
(Th
Hi,
The PPMC needs to vote on this release candidate before having the IPMC vote on
it.
Note that "The vote is open for 72 hours. It passes if a majority of at least
three +1 IPMC votes are cast.” is not entirely correct. Votes are generally
open for at least 72 hours but can be open longer if
HI,
There seem to be some issues here:
1. 72 hours have not passed
2. You have no IPMC votes, and you need 3 binding votes from the IPMC to make a
release.
Kind Regards,
Justin
> On 26 Nov 2024, at 11:25 PM, zhengchenyu wrote:
>
> Hello Apache Uniffle PPMC and Community,
>
>The vote clos
HI,
+1 (binding) jmclean (IPMC)
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
> Ok, I simply removed this content as it is not required:
> https://github.com/apache/incubator-baremaps/pull/905/commits/af6e40a9860c0b0ce3ea1f670cd180f5bd4f8ca7
Thanks, that looks good to me.
Kind Regards,
Justin
-
To uns
Hi,
In the NOTICE file, there is no need for the "product includes / copied files /
derived files” sections. If you want to keep this content, put it in the README
or similar.
Kind Regards,
Justin
-
To unsubscribe, e-mail: gene
Hi,
Thanks for the improvements, but the NOTICE file still contains license
information, as this can impact downstream projects. Please remove what is not
needed from it, [1] should help.
Moving the image to GitHub may not solve the issue. An ASF project can’t
include or depend on something yo
Hi,
> The CopyWriter.java file is part of the Apache Baremaps project and does not
> require a mention in the LICENSE and NOTICE file.
Yes, it does, as it contains this:
* This code has been adapted from
* https://github.com/PgBulkInsert/PgBulkInsert";>PgBulkInsert
licensed under the MIT
HI,
> According to the documentation [1], what’s currently missing in our LICENSE
> file are pointers (“For details, see deps/flatgeobuf”). I suggest to modify
> the third party section as follow, so we have pointers for everything.
>
> THIRD PARTY LICENSES:
>
> Code and data produced outs
Hi,
Thanks for finding that legal issue.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Hi,
-1 (binding) from jmclean (IPMC)
in the main source release I checked:
- incubating in artifact names
- signatures and hashes are fine
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- ASF files have headers
- Didn’t compile from source
And everything is fine t
Hi,
>> - LICENSE is misisng info on [3][4]?
>
> I’m not sure to understand this point. I checked both file and they have a
> license information in their header.
They need to be mentioned in LICENSE, as that is where licencing info goes.
>> - NOTICE contains information on MIT/BSD license code
HI Bertil,
Apologies, that was indeed intended for another project. However you be clear
license information belongs in LICENSE, not NOTICE, see [1].
Justin
1. https://infra.apache.org/licensing-howto.html
Hi,
-1 (binding) form jmclean (IPMC)
I checked:
- incubating in name
- DISCLAIMER exists
- LICENSE is missing license information
- LICENSE is misisng info on [3][4]?
- NOTICE contains information on MIT/BSD license code when it should not
- How is this file is misisng a header [1]
- How is this
Hi,
Sorry but it -1 (binding) from me jmclean (IPMC)
I checked:
- incubating in name
- signature and hashes are fine
- DISCLAIMEr exists
- LICENSE is missing 3rd party content, some of which we may not be able to use.
- NOTICE is fine
- No unexpected binary files
- I was unable to complete but pr
Hi,
> Could you give an example of what exactly you mean for re-located
> copyright statements?
Generally, these are files donated in a software grant whose copyright
statement has been removed from their file headers, and the copyright line has
been relocated to the NOTICE file. The NOTICE fil
Hi,
> Thanks Justin for the detailed analysis.
> Checking LEGAL-469 [1], the only issue that seems to force an RC4, is
> the CDDL/GPL licensed source file.
Currently, there are several Category X/Category B codes in the release
artifact, I did not list them all. Also those licenses should also b
Hi,
+1 (binding) jmclean (IPMC)
I checked:
- incubating ion name
- signatures and hashes are correct
- DISCLAIMER exists
- LICENSE and NOTICE are OK (see below)
- all files have ASF headers
- no unexpected binary files
- can compile from source
In NOTICE it is unclear why Apache Iceberg, Apache
Hi,
> I was under the impression that N&L files are needed for all published
> code, including public repos.
> So the N&L files in each repo are required.
I woudl put a LICENSE and NOTICE in each repo, but as per [1] "The LICENSE and
NOTICE files must exactly represent the contents of the distri
Hi,
+1 (binding) jmclean (IPMC)
I checked teh source release:
- incubating in name
- signature and hashes are good
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- all ASF files have ASF headers
- no unexpected binaries
- can compile from source
Kind Regards,
Justin
-
HI,
> The current multiple NOTICES files are related to how the codebase is
> structured - we have several repositories that host the codebase - so
> each repository has its own set of legal files.
You should not do this, the LICENSE and NOTICE reflect what is in the release
artifacts, not what
Hi,
> The Hibernate LGPL stuff in the DISCLAIMER-WIP is possibly an issue.
>
> https://github.com/apache/incubator-kie-drools/blob/main/DISCLAIMER-WIP
>
> Using a DISCLAIMER-WIP allows you some leeway with Apache License
> compatible licenses. It does not give you leeway with ones that are
> not
Hi,
While recent vote threads did not directly link to any binary artifacts, the
binary artifacts were listed in the release area and could be easily checked.
That is generally best practice.
Kind Regards,
Justin
-
To unsubscri
Hi,
+1 (binding) jmclean (IPMC)
I checked in the source release:
- incubating in name
- signatures and hashes are fine
- LICENSE and NOTICE are fine
- DISCLAIMER exists
- Files have ASF headers
- No unexpected binary files
- unable to build
The README might need updating on how to build running
Hi,
+1 (binding) but only due to the disclaimer WIP.
Some more work is needed here as per the WIP disclaimer [1], some of which I’d
expect before the next release. There is also the outstanding license issue [2]
I checked:
- incubating release names
- signatures and hashes are correct
- LICENSE
Hi,
It is different as (from the last release) it contains teh following jars:
./incubator-kie-kogito-runtimes/quarkus/integration-tests/integration-tests-quarkus-gradle/integration-tests-quarkus-gradle-project/gradle/wrapper/gradle-wrapper.jar
./incubator-kie-kogito-runtimes/.mvn/wrapper/maven
HI,
> The Apache KIE podling requires several binary files (e.g., .jar and
> .zip files) solely for testing purposes.
Compiled code is not allowed in a source release. If it is required for tests,
then compiling the source for that test is generally an option.
Kind Regards,
Justin
Hi,
> I was trying to find the proper location to write the October report for
> Toree but could only locate this one:
> https://cwiki.apache.org/confluence/display/INCUBATOR/September2024
The report, while submitted in October, covers what happens in September and is
named after that month.
K
Hi,
Also the URL should be:
https://cwiki.apache.org/confluence/display/INCUBATOR/September2024
Thanks,
Justin
> On 8 Oct 2024, at 5:08 AM, jmcl...@apache.org wrote:
>
> Dates for next board report:
> Wed October 02 - Podling reports due by end of day
> Sun October 06 - Shepherd reviews due by
Hi,
Apologies for the late notification, but you should still have time to get the
reports in by the end of the week.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional comma
1 - 100 of 2516 matches
Mail list logo
