Hi,
> I've updated the release notes page now, but I haven't done anything to
> the
> > 4x documentation yet. Should I do that right away, or wait until the 4.x
> > release cycle is a bit further along?
>
> Thanks. The 4x documentation is there for this kind of edits - so
> definitely yes, please do it at your soonest convenience.
>
I don't seem to have edit rights to the documentation page:
https://wiki.duraspace.org/display/DSDOC4x/SWORDv2+Server
> > I had a battle with this this morning, but didn't have much success. In
> the
> > end I followed this how-to:
> >
> >
> http://jasonrudolph.com/blog/2009/02/25/git-tip-how-to-merge-specific-files-from-another-branch/
>
> Yeah, we aren't anywhere near as strict about this as the LKML, so no
> worries. Although I can recall one code-dump of not-so-much-related
> features from the 3.0 release cycle that was then problematic because
> they couldn't be reviewed separately and we could either take it or
> leave it as a whole. So it's best to avoid this from early on, if at
> all possible.
>
The changes with the full version history are available in the original
fork of the DSpace repository.
https://github.com/nye-duo/DSpace/tree/duo
You are welcome to pull the changes from there instead. Everything in the
dspace-swordv2 directory plus the swordv2-config.cfg and the metadata
registry.
Cheers,
Richard
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
