Maybe sage-feature branches don't get merged
because they are too optimistic, too much work, adding a feature that
nobody cares about...
I am thinking of feature branches that are fully implemented but not expected to be merged to sage soon because it is too special, too big, needs more work to start normal review process, etc, or the author simply does not want it merged to sage for some reason...
I imagine that we could have many such feature branches (which is a good thing, no?) if we support them by solving minor technical issues. If you advise me that it is just unrealistic imagination, then I will just stop.
The patchbot is meant to test other unrelated parts of Sage and to test
the patch on different systems. But that's something that you would
normally only do when the ticket is mostly finished.
needs_feedback is a shorthand of "needs_review with a comment that it's just for the patchbot and the interested people". The sage-feature tickets in needs_feedback status would have branches mostly finished.
I think that the patchbot is for tickets in the normal "needs_review". But it is easier to share the patchbot for feature tickets than to setup extra "feature-bots".
(Travis) -1 as it complicates things for something that would likely not be used.
Possibly... I am not sure whether we could have many such feature branches. We would never know if we do not encourage people to do so...
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
เขียนโดย computer ถึง computer เวลา 7/03/2560 01:37:00 หลังเที่ยง
เขียนโดย computer ถึง computer เวลา 7/03/2560 05:39:00 หลังเที่ยง