If only there were some project with a release cycle you could emulate... :)
On Tue, Jun 18, 2013 at 11:44 AM, Christopher Zimmermann <
madro...@gmerlin.de> wrote:
> On Tue, 18 Jun 2013 18:04:22 +0100
> Stuart Henderson <st...@openbsd.org> wrote:
>
> > On 2013/06/18 18:46, Peter Hessler wrote:
> > > On 2013 Jun 18 (Tue) at 17:40:06 +0200 (+0200), Christopher
> > > Zimmermann wrote: :Hi,
> > > :
> > > :this has been rotting in openbsd-wip for quite some time now. But
> > > since :some people seem to be actually using it I updated it and
> > > propose it :for inclusion in the official ports tree.
> > > :I adopted this project from Vladimir Litovka who has abandoned it
> > > and :improved it security wise.
> > > :Because I don't plan to add new features, only to fix bugs I have
> > > no :real scheme for releases and versioning numbers, so I figured
> > > it would :probably be best to version it by date. Is this sensible?
> > > OK for commit? :
> > >
> > >
> > > Please use "PKGNAME = minimalist-0.0.${DATE}" so if they ever do
> > > real releases, we don't need EPOCH.
> >
> > Better still Christopher, since you're upstream anyway, how about
> > rolling a real release :-)
>
> I did a release 3.0 and 3.1, but since I will only do bugfixes, what
> sense is there in doing a "release" for every bug I fix?
> This is no rhetorical question. I really am looking for input on this
> matter. If I do releases how do I decide when...
>
