EPICS Home

Experimental Physics and Industrial Control System


 
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: R3.15.0 deadline approaching
From: Michael Davidsaver <[email protected]>
To: [email protected]
Date: Wed, 30 May 2012 10:54:11 -0400
Hi Andrew,

I just want to summarize my plans. The branches I'm planning to propose for inclusion are the following. When I

Ralph's server side plugins work. The remaining work is to figure out how best to run the unit tests on RTEMS and vxWorks.

https://code.launchpad.net/~epics-core/epics-base/server-side-plugins


I pushed a few more revisions to

https://code.launchpad.net/~epics-core/epics-base/dontcant

these actually back out some of the changes already merged. This re-adds some uses of cantProceed() to errors which are not allocation failures (epicsMutexMustLock() being one).


I'm also going to propose:

https://code.launchpad.net/~epics-core/epics-base/thread-pool

I think the API at this point is fixed. I'm planning to replace the internal mutexs with something which can be used from interrupt context for RTEMS and vxWorks.


And if I have time

https://code.launchpad.net/~epics-core/epics-base/callback-error

Although I think I will make some changes to this as well. I'm having second thoughts about adding a field to the CALLBACK structure which existing code may not initialize correctly.


Michael


On 5/29/2012 7:04 PM, Andrew Johnson wrote:
Calling all Base 3.15 developers...

According to the 3.15.0 release timetable slide that I presented at the SLAC
meeting, we have a major deadline approaching this Friday:

– All code branches to be considered for inclusion must be
   • published on Launchpad and
   • a merge requested by 2012-06-01 (Friday 1st June)

Since I don't know what the status is of many of the branches published,
please make sure that any major work to be included has had a merge requested.
If it's not quite ready yet that's Ok, just include a note to that effect in
the merge request.

- Andrew


Replies:
Re: R3.15.0 deadline approaching Michael Davidsaver
Re: R3.15.0 deadline approaching Andrew Johnson
References:
R3.15.0 deadline approaching Andrew Johnson

Navigate by Date:
Prev: R3.15.0 deadline approaching Andrew Johnson
Next: Re: R3.15.0 deadline approaching Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: R3.15.0 deadline approaching Andrew Johnson
Next: Re: R3.15.0 deadline approaching Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024