Community
Participate
Working Groups
We’ll use this Bugzilla record to track the onboarding process for the project. This channel will be the primary means of communication for the project team, your mentors, and the Eclipse Foundation during this process. To get started on your new project, we need to do the following: -Identify a mentor for the project -Transfer ownership of the project name trademark to the Eclipse Foundation We will open separate Bugzilla records to track this. Once we have all of the requirements above and the proposal has been open for community review for a minimum of two weeks, we will schedule the project for creation. If you have any questions for us, please feel free to reach out anytime! As well, if you’d like an overview of the project creation process, check out our Project Handbook [1]. We look forward to working with you and your team to make this project a success! [1] https://www.eclipse.org/projects/handbook/#starting
The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management: ssh://committer_id@git.eclipse.org:29418/glassfish-tools/glassfish-tools.git Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=glassfish-tools Outbound Communication: Mailing list: https://dev.eclipse.org/mailman/listinfo/glassfish-tools-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/glassfish-tools.git Commits will be published to www.eclipse.org/glassfish-tools within 5 minutes Downloads: http://download.eclipse.org/glassfish-tools Archives: http://archive.eclipse.org/glassfish-tools Builds: You can upload releases to ~committer_id/downloads/glassfish-tools via SFTP or SCP (to build.eclipse.org) or from a CI instance at Eclipse.org Older builds should be moved to the archives area when they are no longer required.
Your next step is to submit an initial contribution [1] for review by the IP Team. Please do not commit any code to an Eclipse Foundation Git repository until after you receive the IP Team's approval. IP requests are referred to as Contribution Questionnaires (CQs). When the initial CQ receives “check in” and/or “full approval” you are now ready to check the initial project code contribution into your project’s repository. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution
Created Contribution Questionnaires (CQs): https://dev.eclipse.org/ipzilla/show_bug.cgi?id=15355
Hi Kasandra, I uploaded the source code in CQs for review and didn't realize have to update the workflow. Could you check if the CQs is now in correct status? https://dev.eclipse.org/ipzilla/show_bug.cgi?id=15355 Thanks, Danny Ju
(In reply to Danny Ju from comment #4) > Hi Kasandra, I uploaded the source code in CQs for review and didn't realize > have to update the workflow. Could you check if the CQs is now in correct > status? I've approved the CQ on behalf of the EE4J PMC. This will push it along the workflow and put it into the hands of the Eclipse IP Team. Stay tuned.
Where can I find the status IP review? I haven't seen any update in the IPZilla bug: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=15355 Here is the initial project code contribution so far: * The project web site created at: https://projects.eclipse.org/projects/webtools.glassfish-tools * Source code checked in to git repo https://git.eclipse.org/c/gerrit/glassfish-tools/glssfish-tools.git/ * Jenkin build server has been setup for building and signing the JARs https://ci.eclipse.org/glassfish-tools/
(In reply to Danny Ju from comment #6) > Where can I find the status IP review? I haven't seen any update in the > IPZilla bug: > https://dev.eclipse.org/ipzilla/show_bug.cgi?id=15355 > > > Here is the initial project code contribution so far: > * The project web site created at: > https://projects.eclipse.org/projects/webtools.glassfish-tools > * Source code checked in to git repo > https://git.eclipse.org/c/gerrit/glassfish-tools/glssfish-tools.git/ > * Jenkin build server has been setup for building and signing the JARs > https://ci.eclipse.org/glassfish-tools/ The IP Team has it in their queue. Are you waiting for final approval for anything in particular? e.g. do you have a particular date in mind for a release? Does the project use any third party content (other than GlassFish itself)?
>> Are you waiting for final approval for anything in particular? >> e.g. do you have a particular date in mind for a release? We have done testing on the build from source code checked-in, and are hoping to have a release shortly after the coming Eclipse Photon release. >> Does the project use any third party content? No. It doesn't.
(In reply to Danny Ju from comment #8) > >> Does the project use any third party content? > No. It doesn't. Is GlassFish itself a prerequisite?
AFAICT, the project team has checked in the initial contribution and has a build. But it looks like progress stopped about six months ago. What is the status of the project?
>>> Is GlassFish itself a prerequisite? A client library is shipped as part of the plugin but GlassFish itself is NOT a prerequisite. There is no activity from dev team since there has been no new features or bug fixes so far. We are waiting for Eclipse IP Team's final approval.
Your initial contribution has been approved and there is code in your source code repository; It is now time to plan your first release! If you haven't already done so, it is time to create a release record. If you have already created your release record, you may revise your date to most accurately reflect project progression. Once your release record is created, confirm the date and engage in the process. For more information about the release process, check out our handbook [1]! [1] https://www.eclipse.org/projects/handbook/#release
My apologies, this comment was posted in error! Please disregard. Thanks, Cydnie (In reply to Cydnie Smith from comment #12) > Your initial contribution has been approved and there is code in your source > code repository; It is now time to plan your first release! > > If you haven't already done so, it is time to create a release record. > > If you have already created your release record, you may revise your date to > most accurately reflect project progression. > > Once your release record is created, confirm the date and engage in the > process. > > For more information about the release process, check out our handbook [1]! > > [1] https://www.eclipse.org/projects/handbook/#release
AFAICT, your initial contribution was approved on 04-03-2019; but, no releases have been planned. What is the status of your first release? Is there anything we can assist with? For more information about the release process, check out our handbook [1]! [1] https://www.eclipse.org/projects/handbook/#release
Hi, I have update the project with an new release record at: https://projects.eclipse.org/projects/webtools.glassfish-tools/releases/1.0.1 (Source code has been checked and build produced while IP Team going through the review and approval.) Thanks.
(In reply to Danny Ju from comment #15) > Hi, > I have update the project with an new release record at: > https://projects.eclipse.org/projects/webtools.glassfish-tools/releases/1.0.1 > > (Source code has been checked and build produced while IP Team going through > the review and approval.) > > Thanks. We will use this bug to track the release: https://bugs.eclipse.org/bugs/show_bug.cgi?id=549822. If you haven't already, please request PMC approval.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
The project was successfully provisioned some time ago.
