From: Helmut Wollmersdorfer <helmut@wollmersdorfer.at>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] 0.7.11 soon
Date: Mon, 09 May 2005 18:07:04 +0200 [thread overview]
Message-ID: <427F8AA8.8000407@wollmersdorfer.at> (raw)
In-Reply-To: <LVlMtS7zpHS+KhTi1IqrJxc=lge@web.de>
Lars Ellenberg wrote:
> hm.
> maybe it is easier to NOT generate a drbd-0.7.10 package, but a drbd-0.7
> paackage, so it can be updated to our 0.7.X releases without violating
> any package release policies?
At Debian a freeze is a freeze. There is no workaround. After a freeze
and release of stable they only accept "security fixes".
The only question is, how serious the freeze is. AFAIR the last freeze
was summer last year, targeting September for Release. Then the release
was delayed to March ...
> mean, development is in 0.8, 0.7 is in "bugfix-only-mode" anyways.
Not all "bugfixes" are "security fixes".
IMHO the mainstream of users can live with 0.7.10.
If someone has special requirements, (s)he can
- install from Debian /unstable (or /testing after release)
- compile from tar/SVN
- request LINBIT services
- backport future releases to stable
- use another $distri
IMHO it's important for the popularity of DRBD to have the "pretty
stable" 0.7.10 in Debian.
Helmut Wollmersdorfer
next prev parent reply other threads:[~2005-05-09 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 8:30 [Drbd-dev] 0.7.11 soon Philipp Reisner
2005-05-09 8:58 ` Philipp Hug
2005-05-09 9:37 ` Philipp Reisner
2005-05-09 14:46 ` Lars Ellenberg
2005-05-09 16:07 ` Helmut Wollmersdorfer [this message]
2005-05-09 16:31 ` Lars Ellenberg
2005-05-09 16:55 ` Philipp Hug
2005-05-09 17:17 ` Helmut Wollmersdorfer
2005-05-09 21:17 ` Lars Ellenberg
2005-05-10 8:46 ` Philipp Reisner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=427F8AA8.8000407@wollmersdorfer.at \
--to=helmut@wollmersdorfer.at \
--cc=drbd-dev@lists.linbit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox