[hunchentoot-devel] edicl & Quicklisp - formal release tarballs or production-ready master branches?

[Hans Hübner]

Hi Sebastian,

Sorry for the delay. I will switch to git-flow in the future, but that will
take a little while. I would like to make a release in the not so far future
as git repository has a number of improvements an bug fixes, but I still
have not found the time to make a basic file system to go with the release.
Any volunteers?

Hans
Am 04.09.2011 17:01 schrieb "Sebastian Tennant" <sebyte at smolny.plus.com>:
> Hi Hans,
>
> I recently wrote the following post on the Quicklisp mailing list:
>
> http://permalink.gmane.org/gmane.lisp.quicklisp/69
>
> and you can read Zach's reply here:
>
> http://permalink.gmane.org/gmane.lisp.quicklisp/70
>
> Here's the final paragraph of Zach's reply, for the sake of convenience:
>
> "If the updated Ediware projects have important improvements, I would love
to
> see new versioned releases published in some formal way. If that's not
going
> to happen, I can look into pulling the projects from git [...]"
>
> I suspect formal release tarballs for each and every project in edicl
would be
> quite a lot of work for you (as it probably was for Edi) so how about
> maintaining production-ready master branches (as in git-flow[1]) to make
things
> as easy as possible for Zach?
>
> Seb
>
> [1] http://nvie.com/posts/a-successful-git-branching-model/
>
> --
> Emacs' AlsaPlayer - Music Without Jolts
> Lightweight, full-featured and mindful of your idyllic happiness.
> http://home.gna.org/eap
>
>
> _______________________________________________
> tbnl-devel site list
> tbnl-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/tbnl-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/tbnl-devel/attachments/20110909/3e6e05d8/attachment.html>