ADD Project releasing script

Create the releasing script for future releases.
It wasn't lost, in fact. That approach has some problems: first of all,
this is the approach followed in the Context Broker script, and I prefer to
keep the coherence (if its going to change we should agree the changes with
Orion's team); the approach you suggest is also different, as it would
provide a single global changelog outside the spec, while the purpose of
the current file is to hold the release changes until a new release is
created.
El 02/12/2014 13:26, "David Lopez" <notifications@github.com> escribió:

> In scripts/build/release.sh:
>
> > +#
> > +export NEW_VERSION=$1
> > +export PEP_RELEASE=$2
> > +
> > +#
> > +# correct date format
> > +#
> > +DATE=$(LANG=C date +"%a %b %d %Y")
> > +export dateLine="$DATE Daniel Moran <daniel.moranjimenez@telefonica.com> ${NEW_VERSION}-${PEP_RELEASE}"
> > +
> > +
> > +# Modify rpm/SPECS/pepProxy.spec only when step to a non-devel release
> > +if [ "$PEP_RELEASE" != "dev" ]
> > +then
> > +    #
> > +    # Edit rpm/SPECS/pepProxy.spec, adding the new changes from CHANGELOG_FILE
>
> I'm afraid this comment was lost. A file can be included in a SPEC file,
> thus saving from using a temporal file to append the changelog.
>
> %changelog
> %(cat CHANGES_NEXT_RELEASE)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/telefonicaid/fiware-orion-pep/pull/59/files#r21155468>
> .
>