On Wed, Dec 18, 2013 at 09:20:22AM -0600, Tim Donohue wrote: > On 12/17/2013 8:01 PM, Mark H. Wood wrote: > > Should we not also promote the language packs to a new version, after > > a major release? Should we not then update the language pack > > dependency version ranges in dspace-parent? > > You are welcome to add these to the list of things to do "after the > release is finished": > > https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-AftertheReleaseisFinished > > I think the only reason they are *not* there, is that it is noted as > part of the release process that you need to: > > 1) Release an updated version of the lang packs, see: > https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-ReleaseDSpaceLanguagePacks%28I18N%29Modules > 2) Update the version numbers of the lang packs in the main pom.xml, see: > https://wiki.duraspace.org/display/DSPACE/Release+Procedure#ReleaseProcedure-DoubleCheckLanguagePacks%27VersionRanges
Got it. We develop DSpace N using language packs N-1 and upgrade language packs to N just before DSpace N. That's why something seemed odd, and that's why I asked. It makes sense, but I needed to think about it a bit more. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
