[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[eclipse.org-architecture-council] Eclipse Development Process
- From: David Carver <d_a_carver@xxxxxxxxx>
- Date: Mon, 17 Nov 2008 09:56:13 -0500
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=uuChginV6CbS6s5UuhRD5AQjl1V5+ySIajYSwTeOrKV/FNRhIcx0GWuC+l+wwJzY7y2SzERJbah13wLJ2EIFNFUb6NCugBqBxh7uIxmDOl6o+1D9LRlmApeJSl6bsOTNomHxk5o45DwN5buyzKkAPodKdc/jXy20U+AS0fazPng= ;
- User-agent: Thunderbird 18.104.22.168 (X11/20080925)
Recently, I blogged about if the the Eclipse Development Process was
still considered an agile one. Mike suggested that I bring this up as
an Architecture Council topic.
As Mike has pointed out the Eclipse Development Process isn't really
considered with the actual coding and software development, but more in
how to move a project through the Eclipse release and deployment
cycle. I don't think that the AC should dictate to projects how to
develope their particular plugins, but I do think that we need to try to
help install and make sure that that 10 principles of Agile Development
are being followed.
Anyways, is this something that the Architecture Council should try to
address over the next several months, and if so how?
Personally, I think a recommendation of which Agile methodologies a
project can use wouldn't hurt. As I said, I'm fond of XP and Scrum
used together, but that's my opinion. Any other combinations, or