On 6/22/2016 5:45 AM, Paul Jakma wrote:
On Wed, 22 Jun 2016, Lou Berger wrote:
While the conclusion to work on ce may (or may not, I wasn't on the
call for this) be premature, why can't a branch just be added under
the existing repo if/when that's the consensus among the community?
What is the status of this CE thing relative to master? Is it a
relatively ephemeral (content wise) that generally acts as a staging
tree for integration? Or is it something else?
You can think of it as a staging tree, a "relatively" stable tree
compared to master. It also serve as a test vehicle for new features or
behavior changes that we are not sure we want to integrate with the main
release right away. For example, assume I want to push the new feature
that I have been working on: MTR-OSPF (RFC4915). Having that in the CE
(thing ;) ) for a few cycles might help us understand its impact on
users or whether it is worthy to be added to the main release or not. I
really think there is a value there.
Jafar mentioned issues there - they need to be resolved.
Are you referring to this post/thread?
https://lists.quagga.net/pipermail/quagga-dev/2016-June/015499.html
If CE is meant to be some way to get around the fact that some patches
in the backlog have review comments outstanding; and the contributor
concerned thinks it easier to engineer a crisis than just engage with
review comments and address them via revisions and/or persuasion,
then, sorry, no.
I don't think the CE is intended be to used that way. The community
should be able to handle the misuse of CE or anything else related to
the project for that matter. Comments or issues should be addressed,
there is no question about this.
Regards,
Jafar
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
