Re: ELPA update

[Ted Zlatanov]

On Thu, 29 Sep 2011 10:16:10 +0900 "Stephen J. Turnbull" <address@hidden> 
wrote: 

SJT> PJ Weisberg writes:
>> You could set up your cron job to publish new versions only of
>> packages that have had their version number changed.  Updating the
>> version number could be analogous to "tagging" a release in a normal
>> one-project repository.

SJT> That's a little constraining.  I don't do it for any personal projects
SJT> since I started using git, but I used to bump versions every time I
SJT> got a new working version.  In a multi-developer project, that kind of
SJT> custom might be harder to terminate.

SJT> How about triggering based on a tag name convention, like "a tag of
SJT> the form 'release-FOO-N-NN' means to update the downloadable package"?

I don't see what's wrong with my proposal to have a `elpa-dev' branch
for unstable and `elpa-stable' for stable packages; merging `elpa' into
`elpa-dev' will be a much clearer sign to publish a new version than
incrementing the version number (which, as we know, is often
unparseable).

Ted