| Re: [birt-dev] [External] BIRT Q&A Meeting |
 |
Piggyback CQs are not longer required or supported. |
IP Team review or approval is not required for an Eclipse open source project to use released content from another Eclipse open source project as part of a release (a project may use unreleased content from another project in milestone builds). A release of one project should never include unreleased content from another project.
When an Eclipse projects makes direct use of third-party content inherited by consuming another Eclipse open source project, that content must be treated as a prerequisite dependency.
In general correct.
However, IIRC, for Orbit (non eclipse bundles served from download.eclipse.org) we have to file a Piggyback CQ
On Sat, Nov 13, 2021, 17:53 Alexander Fedorov <alexander.fedorov@xxxxxxxxxx> wrote:
> we must revisit all the dependencies in the target platform and make sure we have clearance to use them_______________________________________________
Wim, I believe we need to do that only for dependencies harvested outside of download.eclipse.org,
since all the bundles/features that are published at download.eclipse.org should be already approved by IP Team.
Do we have the same understanding here?
Regards,
AF
11/13/2021 4:58 PM, Wim Jongman пишет:
Alexander, we must revisit all the dependencies in the target platform and make sure we have clearance to use them.
We have upgraded most of the dependencies to the latest versions.
Maybe there is a tool to extract the dependencies that we use. If not then someone has to wade through all dependencies.
Cheers,
Wim
On Sat, Nov 13, 2021 at 9:24 AM Alexander Fedorov <alexander.fedorov@xxxxxxxxxx> wrote:
@Wim It is not clear for me what exactly do you mean by "We did not do our legal work"._______________________________________________
Do you think we can enumerate all such things in the form of issues to have clear picture "what else we must to do before the nearest release"?
There is a "RELEASE BLOCKER" label that I just added. Please mark the issues that blocks us. Once this list is empty we can schedule a release review, right?
@Wayne please advice how to proceed, perhaps we should submit the whole sources of BIRT to have them auto-checked and then create a number of IPZilla tickets for all the questionable entries?
Regards,
AF
11/13/2021 8:02 AM, Colin Sutton via birt-dev пишет:
Hi Wim,For me, there is another blocker: the run-time genreport.bat does not work. I can get no further with the issue I raised: https://github.com/eclipse/birt/issues/693, not understanding what is missing.I think the viewer is the more important issue though, can't develop without it!
Regards,Colin
On Fri, 12 Nov 2021 at 20:25, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
Hey Alexander,
There are two blockers:
1. Report viewer does not work2. We did not do our legal work
You have made a request for apache fop a couple of weeks ago but this is still pending. I am sure we have to revisit a lot of other dependencies.
We also need time to latch onto simrel. A release review would then be required much earlier?
Cheers,
Wim
_______________________________________________On Fri, Nov 12, 2021 at 6:58 AM Alexander Fedorov <alexander.fedorov@xxxxxxxxxx> wrote:
Hi Wim,_______________________________________________
Let's schedule a release review for 4.9 in the middle of December, somewhere near to SimRel 2021-12.
In case of success we can declare public release and then announce joining SimRel 2022-03.
In case of failure we will learn a lot.
So, we are winning in any case.
If you need my assistance with this matter we can schedule a short call.
Regards,
AF
11/10/2021 1:16 AM, Wayne Beaton пишет:
Before the project can push out anything called a "release", you'll have to undergo a release or progress review per the Eclipse Foundation Development Process.
I'll have the EMO initiate a progress review. They'll let you know if we need anything from the project team. After that has been successfully completed, the project team can engage in however many releases they need to for a calendar year.
Wayne
On Tue, Nov 9, 2021 at 6:49 AM Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
.. and we will support the latest Eclipse releases
_______________________________________________On Tue, Nov 9, 2021 at 12:41 PM Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
On Mon, Nov 8, 2021 at 5:56 PM Michael Greenman via birt-dev <birt-dev@xxxxxxxxxxx> wrote:
Questions for discussion:
1) When (approximately) will 4.9 or any new release (minor or major) actually be available for download and production use?
ASAP. You can speed up the process by helping the development.
Snapshot downloads are available from CI: https://ci.eclipse.org/birt/job/birt-master/lastSuccessfulBuild/artifact/build/birt-packages/birt-report-all-in-one/target/products/_______________________________________________
2) What version of Eclipse will be supported in that release? If it is the same from 2019 (like it is today) when can we expect a release with support for newer versions of Eclipse?
Thank you!
Michael
From: birt-dev <birt-dev-bounces@xxxxxxxxxxx> On Behalf Of Wim Jongman
Sent: Saturday, November 6, 2021 3:11 PM
To: Birt Dev project <birt-dev@xxxxxxxxxxx>
Subject: [External] [birt-dev] BIRT Q&A Meeting
Dear friends of the BIRT project,
I am hosting a Q&A session next Monday. Everyone with questions (and answers) can join. I certainly have a few questions myself, so I hope that all experts can join.
If you like to put some stuff on the agenda, then feel free to reply with your topics.
See you Monday.
Cheers,
Wim
Subject: BIRT Q&A Session
When: Monday, 8 November 2021 18:00-19:00 (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna.
Where: Microsoft Teams Meeting
________________________________________________________________________________
Microsoft Teams meeting
Join on your computer or mobile app
Click here to join the meeting
This e-mail and any attachments are intended only for the named recipient(s) and may contain information that is legally privileged, confidential, or exempt from disclosure under applicable law. This message may be logged for archival purposes, may be reviewed by parties at Deltek other than those named in the message header, and may not necessarily constitute an official representation of Deltek. If you have received this message in error, or are not the named recipient(s), you may not retain copy or use this e-mail or any attachment for any purpose or disclose all or any part of the contents to any other person. Any such dissemination, distribution or copying of this e-mail or its attachments is strictly prohibited. Please immediately notify the sender and permanently delete this e-mail and any attachment from your computer.
You are responsible for complying with all applicable data protection, import, re-import, export, and re-export control laws, including any applicable license requirements, and country-specific sanctions programs. Without limiting the foregoing, you are solely responsible for compliance related to the information you send, via email, to Deltek, its employees, or agents. Please contact legalcompliance@xxxxxxxxxx with any questions or concerns.
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation
_______________________________________________ birt-dev mailing list birt-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
_______________________________________________ birt-dev mailing list birt-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
_______________________________________________ birt-dev mailing list birt-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
birt-dev mailing list
birt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev
_______________________________________________ birt-dev mailing list birt-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/birt-dev