Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 06/28/2009 02:56 PM, Ante Karamatić wrote: > Scott Inderlied wrote: > >> How much risk does this entail? Is the git image stable enough for production use? > > It's a release candidate[1]. One bug was found and was fixed. > > I'm not drbd developer, but I would suspect that current git would > become rc3 and than stable. Of course, rc3 could be skipped. Someone > from Linbit would know better. > > [1] http://en.wikipedia.org/wiki/Development_stage#Release_candidate Since you appear to understand very well what a release candidate is, why are you suggesting that someone go to production with a git snapshot that's not even a release candidate, but an intermediate version between two release candidates (or a release candidate and a final release, depending on community feed back and bug reports)? Scott, please use release candidates and git checkouts for testing only. Production systems should only get released versions (or certified hotfixes if included in your support SLA). Cheers, Florian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20090628/6f61a5c3/attachment.pgp>