This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Mainline open


> Please announce major branch merges with 24-48 hours notice so we can be
> sure we don't do two at once.

Hmm.......

Am I alone in thinking that a more formal procedure for scheduling the
branch merges might be desirable (even if it is not enforcable...)? This
free for all is very exciting, but a bit chaotic. 

Chaos is cool, and all. I don't care, I'll put up with most things, but
I think that a bit more structure might go a long way. 

For instance, it would be nice to have reference-able testresults,
for all front ends, on the branch to be merged. Of course, it would be
great to have testsresults for more than one target, but I think asking
for more than one native and one cross is pushing it. (Native and one
cross should be required though.)

Also, could some kind of web page with status of what is in the queue,
and in what order, be established? Traffic on this list is high and
sorting through it to figure out what is going on is sub-optimal, but
may be symptomatic of my own personal disorganization. I'm having a hard
time figuring out when the tree is open, and when it is closed. 

-benjamin


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]