Helix is currently committing a couple type-o fixes, and I'm running through the dry-run phase.  Mark, is it worth it to get #91 in and wait on #88 or would you rather do them both for RC2?  

Let me know.  I'm just verifying everything now but I can wait to pull the actual trigger.


--
sands fish
Senior Software Engineer
MIT Libraries
Technology Research & Development
sands@MIT.EDU
E25-131

On Oct 5, 2012, at 12:23 PM, Tim Donohue wrote:

Hi Mark,

At Weds meeting, we had decided "if they are committed before RC1 that's fine, but RC1 shouldn't wait around for them".

* As it is, Pull #88 cannot be automerged & needs updating. Therefore, I'm assuming it is going to miss RC1 (which is about to be cut today), but we can work to get it in after RC1.

* Pull #91 looks like it could be automerged. But as Sands is about to cut RC1, you need to coordinate with him as to whether there's still enough time to commit it.  If it doesn't get into RC1, it could get in after RC1.

The main message here is that RC1 needs to be cut today if we are still going to start Testathon next week. So, we cannot wait around any longer.

- Tim


On 10/5/2012 11:14 AM, Mark Diggory wrote:
I'm still wondering if we have confirmation on accepting

https://github.com/DSpace/DSpace/pull/91

and fixing

https://github.com/DSpace/DSpace/pull/88

Mark

On Fri, Oct 5, 2012 at 7:59 AM, Sands Alden Fish <sands@mit.edu
<mailto:sands@mit.edu>> wrote:

   Hi Tim,

   Yes, I had indicated today.  I am just in the office now.  I will
   keep everyone updated concerning the RC1 cut.


   --
   sands fish
   Senior Software Engineer
   MIT Libraries
   Technology Research & Development
   sands@MIT.EDU <mailto:sands@MIT.EDU>
   E25-131

   On Oct 5, 2012, at 10:45 AM, Tim Donohue wrote:

   Must have been my mistake then! Sorry if I caused extra confusion. :)

   Hopefully we'll still have time to get the demo.dspace.org
   <http://demo.dspace.org> (and other
   Testathon servers) updated today.

   Though I guess we could always just update them to the latest
   "master"
   code (i.e. the soon-to-be RC1), rather than waiting for RC1 to
   appear in
   Maven Central.

   - Tim

   On 10/5/2012 9:29 AM, Robin Taylor wrote:
   Hi Tim,

   I thought Sands had indicated he wanted to do it today ?

   Cheers.


   On 05/10/12 15:08, Tim Donohue wrote:
   Hi all,

   Just checking in on the status of the 3.0 RC1 release?

   I thought the plan was to release it yesterday, so that folks
   setting up
   Testathon servers could do that work today. But, maybe I had
   misunderstood?

   - Tim




   ------------------------------------------------------------------------------
   Don't let slow site performance ruin your business. Deploy New
   Relic APM
   Deploy New Relic app performance management and know exactly
   what is happening inside your Ruby, Python, PHP, Java, and .NET app
   Try New Relic at no cost today and get our sweet Data Nerd shirt too!
   http://p.sf.net/sfu/newrelic-dev2dev
   _______________________________________________
   Dspace-release mailing list
   Dspace-release@lists.sourceforge.net
   <mailto:Dspace-release@lists.sourceforge.net>
   https://lists.sourceforge.net/lists/listinfo/dspace-release


   ------------------------------------------------------------------------------
   Don't let slow site performance ruin your business. Deploy New Relic APM
   Deploy New Relic app performance management and know exactly
   what is happening inside your Ruby, Python, PHP, Java, and .NET app
   Try New Relic at no cost today and get our sweet Data Nerd shirt too!
   http://p.sf.net/sfu/newrelic-dev2dev
   _______________________________________________
   Dspace-release mailing list
   Dspace-release@lists.sourceforge.net
   <mailto:Dspace-release@lists.sourceforge.net>
   https://lists.sourceforge.net/lists/listinfo/dspace-release




--
@mire Inc.
*Mark Diggory *(Schedule a Meeting <http://doodle.com/mdiggory>)
/2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010/
/Esperantolaan 4, Heverlee 3001, Belgium/
http://www.atmire.com <http://www.atmire.com/>