[U-Boot] release timing wrt linux
can we shorten/elongate (doesnt matter to me) the next release process ? the original time frame was picked so as to not overlap with the linux kernel, but the current merge window did exactly that :(. -mike
Dear Mike,
In message 200904020716.34368.vapier@gentoo.org you wrote:
can we shorten/elongate (doesnt matter to me) the next release process ? the original time frame was picked so as to not overlap with the linux kernel, but the current merge window did exactly that :(.
Yes, I'm aware of this, but at least it's not our fault. We've been releasing mostly on schedule, it was the Linux kernel releases that shifted and shifted...
Shorten is IMHO not an option, but we can delay it.
Please suggest where and when? Make this merge window longer by one week, and this testing phase longer by two weeks?
Best regards,
Wolfgang Denk
On 13:40 Thu 02 Apr , Wolfgang Denk wrote:
Dear Mike,
In message 200904020716.34368.vapier@gentoo.org you wrote:
can we shorten/elongate (doesnt matter to me) the next release process ? the original time frame was picked so as to not overlap with the linux kernel, but the current merge window did exactly that :(.
Yes, I'm aware of this, but at least it's not our fault. We've been releasing mostly on schedule, it was the Linux kernel releases that shifted and shifted...
Shorten is IMHO not an option, but we can delay it.
Please suggest where and when? Make this merge window longer by one week, and this testing phase longer by two weeks?
why not create a release to integrate the Kconfig?
Best Regards, J.
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090402112949.GC2651@game.jcrosoft.org you wrote:
Please suggest where and when? Make this merge window longer by one week, and this testing phase longer by two weeks?
why not create a release to integrate the Kconfig?
You would still have to pla for that release, and schedule it.
Feel free to submit the Kconfig stuff for 2009.07. Or now, the merge window is stil open :-)
Best regards,
Wolfgang Denk
On 20:00 Thu 02 Apr , Wolfgang Denk wrote:
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090402112949.GC2651@game.jcrosoft.org you wrote:
Please suggest where and when? Make this merge window longer by one week, and this testing phase longer by two weeks?
why not create a release to integrate the Kconfig?
You would still have to pla for that release, and schedule it.
Feel free to submit the Kconfig stuff for 2009.07. Or now, the merge window is stil open :-)
I've not finished but near
the only thing is that we will need time to write all the Kconfig
so these 3 weeks could be you use for this purpose specialy if no drivers will added every day
Best Regards, J.
On Thursday 02 April 2009 07:40:09 Wolfgang Denk wrote:
In message Mike wrote:
can we shorten/elongate (doesnt matter to me) the next release process ? the original time frame was picked so as to not overlap with the linux kernel, but the current merge window did exactly that :(.
Yes, I'm aware of this, but at least it's not our fault. We've been releasing mostly on schedule, it was the Linux kernel releases that shifted and shifted...
Shorten is IMHO not an option, but we can delay it.
Please suggest where and when? Make this merge window longer by one week, and this testing phase longer by two weeks?
that sounds reasonable to me ... maybe leave the exact release time in May open so that if the kernel releases sooner, we can push out, or if it releases later, we can push up. -mike
On Apr 2, 2009, at 7:03 AM, Mike Frysinger wrote:
On Thursday 02 April 2009 07:40:09 Wolfgang Denk wrote:
In message Mike wrote:
can we shorten/elongate (doesnt matter to me) the next release process ? the original time frame was picked so as to not overlap with the linux kernel, but the current merge window did exactly that :(.
Yes, I'm aware of this, but at least it's not our fault. We've been releasing mostly on schedule, it was the Linux kernel releases that shifted and shifted...
Shorten is IMHO not an option, but we can delay it.
Please suggest where and when? Make this merge window longer by one week, and this testing phase longer by two weeks?
that sounds reasonable to me ... maybe leave the exact release time in May open so that if the kernel releases sooner, we can push out, or if it releases later, we can push up.
What's the concern w/overlap or conflict with the kernel release? I doubt whatever we pick will ever be insync w/the kernel.
- k
On Thursday 02 April 2009 09:27:55 Kumar Gala wrote:
On Apr 2, 2009, at 7:03 AM, Mike Frysinger wrote:
On Thursday 02 April 2009 07:40:09 Wolfgang Denk wrote:
In message Mike wrote:
can we shorten/elongate (doesnt matter to me) the next release process ? the original time frame was picked so as to not overlap with the linux kernel, but the current merge window did exactly that :(.
Yes, I'm aware of this, but at least it's not our fault. We've been releasing mostly on schedule, it was the Linux kernel releases that shifted and shifted...
Shorten is IMHO not an option, but we can delay it.
Please suggest where and when? Make this merge window longer by one week, and this testing phase longer by two weeks?
that sounds reasonable to me ... maybe leave the exact release time in May open so that if the kernel releases sooner, we can push out, or if it releases later, we can push up.
What's the concern w/overlap or conflict with the kernel release?
it's pretty common for people who work on u-boot to also work on the kernel. trying to balance merge windows of two major projects simultaneously is unnecessarily strenuous.
I doubt whatever we pick will ever be insync w/the kernel.
the idea is to be out of sync ;). no, things wont always line up perfectly, but that doesnt mean we cant adjust when the kernel does change. -mike
Hello everybody
in message 200904020716.34368.vapier@gentoo.org Mike Frysinger wrote:
can we shorten/elongate (doesnt matter to me) the next release process ? the original time frame was picked so as to not overlap with the linux kernel, but the current merge window did exactly that :(.
This being a correct and reasonable request, I decided to extend the stabilzation phase for the next release by 3 weeks. i. e. the release schedule (see also http://www.denx.de/wiki/U-Boot/ReleaseCycle) now looks like this:
- The next version will be called v2009.06
- The merge window for v2009.06 closes in 2 hours from now. So better hurry up if you still want to get something into this release ;-)
- The release of v2009.06 is scheduled for Sunday, June 14, 2009.
Best regards,
Wolfgang Denk
participants (4)
-
Jean-Christophe PLAGNIOL-VILLARD -
Kumar Gala -
Mike Frysinger -
Wolfgang Denk