On May 4, 2015 1:36:42 PM CDT, Sebastian Huber <sebastian.hu...@embedded-brains.de> wrote: >There is for sure a lot to do before the release, but in terms of >features the master branch is ready to turn into the 4.11 branch. We >can do all release related stuff on this branch. With Git it is easy >to back port changes provided the file system structure remains intact. >There is no need to delay the RTEMS development. I have currently more >than two man months of patches pending and some of them will be >difficult to merge if someone else works on cleanup patches with the >current master. We have the FreeBSD timecounters, the watchdog >changes, a new thread queue implementation, fine grained locking for >events, message queues and semaphores, a rework of the thread priority >change procedure.
I am not opposed to making the branch but let's wait for Chris to wake up and comment. >----- Joel Sherrill <joel.sherr...@oarcorp.com> schrieb: >> >> Sorry to reply again. >> >> On 5/4/2015 9:24 AM, Gedare Bloom wrote: >> > On Mon, May 4, 2015 at 7:28 AM, Thomas Doerfler >> > <thomas.doerf...@embedded-brains.de> wrote: >> >> Hi, >> >> >> >> I am glad 4.11 will be branched soon. from our side, branching is >ok. >> >> So: Any open items left? Anything we can do to make the branch >happen >> >> soon? Any chance to do the branch within this week? >> >> >> > I get the feeling now the holdup is solely for Joel to manage the >> > technical process. Any way to help him push through the various git >> > commands and coordinate which repos need to have the same releases >> > (RSB, examples-v2, others?) would probably be good. >> Defining the process is a bit part of this. Chris also wanted to make >> sure the >> on-ramp documentation was up to date and clear. >> >> As my last push illustrated, we also have remnants of CVS still >laying >> around >> so at least a quick review of each repo to be tagged and released is >needed. >> >> Overall, Chris just wanted a publicly documented procedure and >checklist. >> >> > Alternately, if EB would be interested to suggest a "Release >Engineer" >> > for this job, it might be good to remove the burden and bottleneck >> > from Joel. >> > >> >> We have held back a set of patches which are too new to be useful >for >> >> the 4.11 branch. On the other side we would like to commit them >soon >> >> without spoiling the branch point. >> >> >> >> wkr, >> >> >> >> Thomas. >> >> >> >> >> >> Am 30.04.2015 um 16:11 schrieb Sebastian Huber: >> >>> Hello, >> >>> >> >>> is there anything left that prevents us to do the branch now? We >can >> >>> still do some work on the branch before we actually make the >release. >> >>> >> >> -- >> >> -------------------------------------------- >> >> embedded brains GmbH >> >> Thomas Doerfler >> >> Dornierstr. 4 >> >> D-82178 Puchheim >> >> Germany >> >> email: thomas.doerf...@embedded-brains.de >> >> Phone: +49-89-18 94 741-12 >> >> Fax: +49-89-18 94 741-09 >> >> PGP: Public key available on request. >> >> >> >> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des >EHUG. >> >> _______________________________________________ >> >> devel mailing list >> >> devel@rtems.org >> >> http://lists.rtems.org/mailman/listinfo/devel >> > _______________________________________________ >> > devel mailing list >> > devel@rtems.org >> > http://lists.rtems.org/mailman/listinfo/devel >> >> -- >> Joel Sherrill, Ph.D. Director of Research & Development >> joel.sherr...@oarcorp.com On-Line Applications Research >> Ask me about RTEMS: a free RTOS Huntsville AL 35805 >> Support Available (256) 722-9985 >> >> _______________________________________________ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel --joel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
