2006/10/16, Tim Ellison <[EMAIL PROTECTED]>:
Mikhail Loenko wrote:
> When we bring new platforms how will we make sure that a patch for some
> rare platform would not break another one?
Beyond sniffing the patch to ensure it looks reasonable, the best a
committer can do is to test it on the platforms he or she has available.
After that we rely on the diversity of the community building and
testing the code to catch any problems; i.e. the change doesn't
necessarily end with the commit, it may still have to be backed out.
How will we define which changes should be backed out?
Do you mean that we first define list of "supported" platforms
and then we will roll back all the changes that reportedly break
build on one of that platform?
What would be the procedure to add a new platform to the list of
supported ones? (Well I assume it's a vote, but what are the criteria
to be used in that vote?)
Thanks,
Mikhail
There is no guarantee of the stability of HEAD, we only get that by
taking a snapshot and everyone testing it with all platforms (c.f. say
Eclipse that does have a centralized build system).
Regards,
Tim
--
Tim Ellison ([EMAIL PROTECTED])
IBM Java technology centre, UK.
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
