[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Eclipse Development Process

Again, I don't want to dictate which methodology they use, but I do think that it is a good idea to document the principles that should be implemented. We should also encourage the projects we are mentoring to follow some standard practices that can help make meeting milestone releases, and consistent stable builds possible.

I know that there isn't a magic formula or a silver bullet, but is there a reason that somebody can come up with why Unit Testing, continuous code integration, and other pragmatic development techniques should not be encouraged for all eclipse projects?

Dave

Gunnar Wagenknecht wrote:
David Carver schrieb:
John I agree, but from my understanding is that Eclipse originally was founded on Agile techniques...

I don't think that this is the case. You are probably mixing up the Eclipse project with the Eclipse Foundation. But I don't know either.

IMHO we should *not* define or instruct projects how they *do* software
development. I see our role more as someone who is looking at *what* the
projects produce and *help* projects to understand what others are doing
and *help* projects in adopting it *if* they want.

Of course we encourage projects to release often and to use the mailing
lists and Bugzilla, etc. But I see this more as part of our mentoring
task to help projects get started and develop their communities.

-Gunnar

------------------------------------------------------------------------

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.