Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[technology-pmc] Fwd: Udig IP Status
Dear all,

Earlier this year we discussed the progress on this project. Since then not much has happened.
I am wondering if there is enough resource/bandwidth available within the project to move any further than where it has been the last couple of years.

My suggestion is either to come up shortly with a realistic roadmap and resource planning towards an EF project release or shelve it.

Looking forward to your decision. 

Kind regards,
Marc Vloemans


Begin doorgestuurd bericht:

Van: Sharon Corbett <sharon.corbett@xxxxxxxxxxxxxxxxxxxxxx>
Datum: 12 juli 2018 om 22:21:35 CEST
Aan: Marc Vloemans <marc.vloemans@xxxxxxxxxxxxxxxxxxxxxx>
Kopie: wayne beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
Onderwerp: Udig IP Status

Hi Marc:  
Please see the 2018 discussion from the IP Ticket for the udig Initial. It seems Frank wanted to try and then floundered....
Not sure if the Project Lead is engaged.  I guess the question remains is this project dead or not.  It would seem one guy won't be able to carry this. I know we tried to close down the project but Frank really wanted to keep it alive...
I believe its time for a go/no go conversation!

Thanks,
Sharon



------- Comment #38 From Frank Gasdorf CLA 2018-01-02 16:01:09 [reply] -------  
IMHO because codebase moved already this ticket is done. Anything we need to do
from project side? Not sure what is expected here.
------- Comment #39 From Sharon Corbett CLA 2018-01-02 20:07:38 [reply] -------  
Happy New Year Frank!

Unfortunately, the time from when we started the initial triage of the codebase
to now has been too long to only review the attachment from 2013 towards a full
review.

We had started email communication concerning how to move forward identifying
we would require a new attachment.  

It is our understanding, however, that PMC requested a termination as per bug
528769 [1].

As a result, this CQ is now dependent upon the termination process.  We are
monitoring that process as well.

Best Regards,
Sharon

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=528769
------- Comment #40 From Frank Gasdorf CLA 2018-01-04 00:32:29 [reply] -------  
Happy New Year Sharon!

Have I understood it correctly: We cannot move on this issue unless there is a
decission for termination bug 528769

If so, who is reposbible or in lead for termination bug? Anything I can do
right now?

However, my read of your comment is that we need a newer source attachment to
re-scan it by Genie Tools to continue here. Please let me know if we can
proceed ..
------- Comment #41 From Frank Gasdorf CLA 2018-03-08 15:37:45 [reply] -------  
Can we get support during codesprint in March, 21th-23rd were we prepare
another product zip for ip review? Do we have to create a release (candidate)
for this or is it enoght to create a tag in git repository?
------- Comment #42 From Wayne Beaton CLA 2018-03-12 14:16:00 [reply] -------  
(In reply to comment #41)
> Can we get support during codesprint in March, 21th-23rd were we prepare
> another product zip for ip review? 

I guess that it depends on what you mean by support. We cannot provide any sort
of realtime support for IP issues (we just don't have the bandwidth). What sort
of support are you looking for?

> Do we have to create a release (candidate)
> for this or is it enoght to create a tag in git repository?

It depends on what you're trying to achieve. If you're making a prerelease
build, then you can just tag it. If you're making anything that will be some
sort of formal release for broad dissemination, then we need to engage in a
release review.
------- Comment #43 From Frank Gasdorf CLA 2018-03-12 14:36:43 [reply] -------  
(In reply to comment #42)
> (In reply to comment #41)
> > Can we get support during codesprint in March, 21th-23rd were we prepare
> > another product zip for ip review? 
> 
> I guess that it depends on what you mean by support. We cannot provide any sort
> of realtime support for IP issues (we just don't have the bandwidth). What sort
> of support are you looking for?
> 
> > Do we have to create a release (candidate)
> > for this or is it enoght to create a tag in git repository?
> 
> It depends on what you're trying to achieve. If you're making a prerelease
> build, then you can just tag it. If you're making anything that will be some
> sort of formal release for broad dissemination, then we need to engage in a
> release review.
> 

Thats fine. I was just thinking of Autoscanning the uploaded zip file within
the two or three days to see if we addressed all the requested changes

Release candidate is fine for now. It dependes on  the output of the IP review
if we can/have to address some open issues. If everything is fine, we have a
good chance after testing the product to make an offical release out of it. 

Where do we have to request release review and is there a checklist we can use
for preperation. We know what we like to release but have not really have an
idea how to release software for/from Eclipse Foundation point of view. Any
suggestion where to start?

Many Thanks

Back to the top