Frank, So, if I understand correctly, in order to close FCREPO-1023, 1) trippi/fcrepo-1023 needs to be applied to trippi/master, 2) a new release of Trippi needs to cut (including publishing to Maven central) 3) fcrepo/fcrepo-1023 needs to be applied fcrepo/master (including updating pom to reference new Trippi version)
I think 1 & 2 will probably eat up 30mins-1 hour, not including Maven central sync time, so your call if you think you can get #3 done for today's code freeze =) On Aug 27, 2012, at 2:43 PM, "Asseg, Frank" <frank.as...@fiz-karlsruhe.de> wrote: > And another question... > In order to merge fcrepo-1023 into master the fix for trippi at > https://github.com/fcrepo/trippi/tree/fcrepo-1023 > has to be merged as well and of course used in the 3.6.1 distribution. > Should i just merge both of these into their respective masters? but > since i added an integration test, it will fail as long as the new > trippi has not been installed. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fedora-commons-developers mailing list Fedora-commons-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
