Skip to contentSkip to conversation

v2009.06-rc1 is out

U-Boot Wolfgang Denk 2 participants 3 messages May 1, 2009

lore
Share & tools
lore
#0 lore raw

Hi everybody...

v2009.06-rc1 has just been released.

Please help testing, and submit fixes to the remaining problems. Things still missing should be submitted ASAP. I would like to have a -rc2 by the end of next week, and strictly only bug fixes after this.

v2009.06-rc1 will also be the base for the "next" branch which I will create soon.

Please use the "next" branch as base for any new work. Note: Please keep in mind that it will be rebased against master every now and then without warning.

Best regards,

Wolfgang Denk

Signature · 6 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Conceptual integrity in turn dictates that the  design  must  proceed
from  one  mind,  or  from  a  very small number of agreeing resonant
minds.               - Frederick Brooks Jr., "The Mythical Man Month"
#1 lore raw
Quoted 3 lines · Wolfgang Denk

Please use the "next" branch as base for any new work. Note: Please keep in mind that it will be rebased against master every now and then without warning.

It is difficult to use as a base a branch that is itself being rebased.

Why not just merge unless there's something that absolutely cannot stay in the history?

Will you be pulling things into the next branch periodically (by request?), or is it just for things that aren't going into custodian next branches? When the next merge window opens, will next beecome master, or is it just an integration test as in linux-next?

-Scott

#2 lore raw

Dear Scott,

Quoted 6 lines · In message <[email protected]> you wrote:
Quoted 3 lines · Wolfgang Denk

Please use the "next" branch as base for any new work. Note: Please keep in mind that it will be rebased against master every now and then without warning.

It is difficult to use as a base a branch that is itself being rebased.

Yes, I am aware of this problem.

Quoted 2 lines

Why not just merge unless there's something that absolutely cannot stay in the history?

I can do that. But it might happen that I decide to rebase, and I wanted you to warn in advance that this might happen.

Quoted 4 lines

Will you be pulling things into the next branch periodically (by request?), or is it just for things that aren't going into custodian next branches? When the next merge window opens, will next beecome master, or is it just an integration test as in linux-next?

I will pull into next if anybody sends me a pull request (and I appreciate if that happens as it reduces the amount of pending patches).

Before the merge window opens, I will merge next into master.

If integration tests are needed, we use u-boot-testing for this purpose.

Best regards,

Wolfgang Denk

Signature · 4 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Beware of programmers carrying screwdrivers."      - Chip Salzenberg