Allow creating non-FINAL release tarballs.

Allow creating non-FINAL release tarballs.

In the charm, when juju-gui-source is a branch,
a release tarball is created from the checkout
running "NO_BZR=1 make distfile".
The "distfile" target was included in the 
released/unreleased check by our Makefile.
This means that trying to deploy the charm
from a branch whose CHANGES.yaml does not
include "unreleased:" always fails with 
the error reported by therve: 
"non-FINAL releases must have a most-recent 
version number of unreleased in CHANGES.yaml".
This branch removes that check from the distfile
target: I think we should protect "dist", but
I don't see, given the problems described above,
a valid reason to continue preventing users
to create non-FINAL tarballs, even if the 
branch is a final release.

https://code.launchpad.net/~frankban/juju-gui/bug-1102633-make-distfile/+merge/144245

(do not edit description out of merge proposal)

[frankban, 2013-01-22 09:08:56]

Please take a look.

[teknico, 2013-01-22 11:23:53]

Land as is.

This looks like a reasonable fix to the mismatch.

[bac, 2013-01-22 11:51:09]

Thank you.  Land as is.

[frankban, 2013-01-22 11:55:20]

*** Submitted:

Allow creating non-FINAL release tarballs.

In the charm, when juju-gui-source is a branch,
a release tarball is created from the checkout
running "NO_BZR=1 make distfile".
The "distfile" target was included in the 
released/unreleased check by our Makefile.
This means that trying to deploy the charm
from a branch whose CHANGES.yaml does not
include "unreleased:" always fails with 
the error reported by therve: 
"non-FINAL releases must have a most-recent 
version number of unreleased in CHANGES.yaml".
This branch removes that check from the distfile
target: I think we should protect "dist", but
I don't see, given the problems described above,
a valid reason to continue preventing users
to create non-FINAL tarballs, even if the 
branch is a final release.

R=teknico, bac
CC=
https://codereview.appspot.com/7189043