----- Original Message -----
From: "Heiko W.Rupp" <hrupp(a)redhat.com>
To: rhq-devel(a)lists.fedorahosted.org
Sent: Tuesday, March 5, 2013 10:25:22 AM
Subject: Re: GitHub migration again -- The Plan
Am 04.03.2013 um 17:30 schrieb Stefan Negrea:
> I am not sure how this would work from the perspective of getting a
> build out for testing purposes. The fix for core might break
> something else in the plugins space but there is no way to get
> feedback for the change in core until post-release of core itself.
> Since the test driver in this case would be a change or new
> functionality in a
Isn't that perfect?
If we make a change in core that breaks (our) plugins, it is likely
to break plugins of third parties as well, which is one thing
we are seeking to prevent.
For a release branch that is good. However, for the master branch it means we purposefully
introduce delays in getting important feedback. Instead of reducing the time necessary to
receive feedback, will get increase it, make things unpredictable, and wrap everything in
a complicated process.
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel