Re: [tools-pmc] Termination review for VE

[David M Williams <david_williams@xxxxxxxxxx>]

> Maybe we should take this opportunity to require that a projects
> (with the exception of permanent incubators) must do a *release* every year.
>
> Thoughts?

My thoughts are it might be a bit much to _require_ a release every year ... seems there'd be so many qualifications (e.g. initial release might take 15 months .. then to align with yearly release the next one might take 18 months, etc.).

But, perhaps the "intent" could be better codified with wording (around section 6.3) such as "... the expectation is that a Project will release once per year. If they do not, the projects PMC should ask for a formal continuation review to clarify what the plan is to get to a release". Or similar.

Thanks for asking,




Wayne Beaton ---04/27/2011 03:28:37 PM---"All Projects are required to participate in at least one Review per year." (section 6.3)

From: Wayne Beaton <wayne@xxxxxxxxxxx>
To: tools-pmc@xxxxxxxxxxx
Date: 04/27/2011 03:28 PM
Subject: Re: [tools-pmc] Termination review for VE
Sent by: tools-pmc-bounces@xxxxxxxxxxx

---

"All Projects are required to participate in at least one Review per year." (section 6.3)

A project needs to do either a release, restructuring, or continuation review every year. The only exception is that permanent incubator projects are not required to have reviews of any kind. We do a bad job of policing this. I have done a little work on some scripts that will help me identify those projects that need a review; I'll roll that out sometime soon...

Maybe we should take this opportunity to require that a projects (with the exception of permanent incubators) must do a *release* every year.

Thoughts?

Wayne

On 04/27/2011 03:12 PM, Schaefer, Doug wrote:

I’ll throw another thought into the mix, and maybe this should be input to the Eclipse Development Process. But I think the key criteria for a project at Eclipse to continue is that they promise to have official releases. If a project never releases, at least officially through the IP process, but still wants to keep the code alive, then maybe we should be encouraging to move it to somewhere a little less official, like Eclipse Labs. Would that be a better home for VE?

 

Doug.

 

From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Wednesday, April 27, 2011 3:07 PM
To: Tools PMC mailing list
Subject: [tools-pmc] Termination review for VE

 

+1 ...

... as long as we remain sensitive to any needs/rampdown the project wants to do. I suggest we start the formal termination review, and if a literal archive is not desired then Yves (or other interested party) can turn it into a 'continuation review' ... explaining what the concrete plans are, etc.


Any (other) PMC member want to volunteer to draft the termination review document? I think source (or examples) could be "snagged" from recent cases that I did, if that helps. Found these searching this list:

Attachment: HibachiTerminationReview.odt
Attachment: HibachiTerminationReview.pdf
And then Cobol was before that ..
http://www.eclipse.org/project-slides/CobolTerminationReview .pdf



I did check cvs activity of VE for the past year, and I can't say its "zero" ... the top line in following "dash table" actually appears to be for "JEM" bundles, which have moved to WTP project (years ago).
I suspect the last substantial activity in July and November of last year ... perhaps "build related"? Getting up on latest Eclipse?





Looking at bugzilla ... there are two that have been marked "fixed" in past year, both related to "build to the latest Eclipse", apparently.

https://bugs.eclipse.org/bugs/buglist.cgi?chfieldfrom=2010-06-15&chfieldto=Now&classification=Tools&product=VE&query_format=advanced&order=resolution%20DESC%2Cbug_id&query_based_on=


HTH



Jeff McAffer ---04/19/2011 09:43:50 AM---+1 On 2011-04-19, at 9:38 AM, Schaefer, Doug wrote:

From: Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>
To: Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
Date: 04/19/2011 09:43 AM
Subject: Re: [tools-pmc] FW: [ve-dev] Error installing VE-Update-1.5.0.zip
Sent by: tools-pmc-bounces@xxxxxxxxxxx




+1



On 2011-04-19, at 9:38 AM, Schaefer, Doug wrote:

Yes, John and I talked about that at EclipseCon. I think we’re ready. Let’s start the vote.

+1.

From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf OfMike Milinkovich
Sent: Tuesday, April 19, 2011 9:37 AM
To: 'Tools PMC mailing list'
Subject: [tools-pmc] FW: [ve-dev] Error installing VE-Update-1.5.0.zip

Esteemed Tools PMC,

Can we please please pretty please archive this project?

Especially now with WindowBuilder in full development, I see no reason to avoid end-of-lifing VE.


From: ve-dev-bounces@xxxxxxxxxxx [mailto:ve-dev-bounces@xxxxxxxxxxx] On Behalf Of Denny Vriesman
Sent: April-19-11 9:32 AM
To: ve-dev@xxxxxxxxxxx
Subject: [ve-dev] Error installing VE-Update-1.5.0.zip


Hello EveryOne,

I’ve Just downloaded “eclipse-rcp-helios-SR2-win32.zip” from eclipse website.
After that I’ve downloaded VE-Update-1.5.0.zip for Helios, in agreement with the site: “http://www.eclipse.org/vep/”, and I try to install it.

But, for my surprise, there is an error on the installation:

The artifact file for osgi.bundle,org.eclipse.ve.cde,1.5.0.R20101202-1328 was not found.
session context was:(profile="" phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.ve.cde 1.5.0.R20101202-1328, action="">
Please, have somebody the solution for this problem ? Is a VE a discontinuous or deprecated project ? Have anyone noted that problem until now ?

Thank you in Advance,
Denny Richard San Vriesman
Analista de Suporte
Softplan Planejamento de Sistemas Ltda
Sistema da Qualidade Certificado ISO 9001:2000
Fone: (48) 3027-8000
http://www.softplan.com.br

_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc

_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc



_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc