Re: [ide-dev] Development Process was Re: Why we dropped Eclipse in favour of IntelliJ | Java Code Geeks
Sorry Wayne, I think I just added to confusion by dropping "EDP" in here -- and no, I don't mean review in the EDP sense. Actually I was (mis)using EDP as a label for all of the formal and informal understandings about how code makes it from someone's head into a release. So I'm not really talking about the high-level process. I'm referring to bug triage process, branch management, knowledge of specific (but often arbitrary) conventions, etc.. not all of which can or should be avoided.
But there is some overlap. For example, where we are in a release train has an enormous impact on how likely it is that someone's contribution will get in or not. A niave outside contributor would have a hard time understanding why a solid but novel contribution that they made in say March of 2014 wouldn't have a chance of getting into an actual Eclipse release until June 2015.
On 2013-09-25, at 6:17 AM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
> Can you be specific? What aspects of the EDP are a big issue?
> I don't believe that you're using the term "review" in the same sense as the EDP. AFAICT, nothing in your post is a limitation imposed by the EDP.
> I'm in the process of wrapping up a new draft of the EDP. If there's something that we can change to reduce friction, I'd like to explore it.
> On 09/24/2013 04:25 PM, Miles Parker wrote:
>> length of time for reviews and overall EDP friction is a _big_ issue.
> Wayne Beaton
> Director of Open Source Projects, The Eclipse Foundation
> Learn about Eclipse Projects
> <eclipsecon logo 480px x 60px.jpg>
> ide-dev mailing list