Simple check if current is broken

[Greg 'groggy' Lehey]

On Tuesday, 13 November 2012 at  9:11:21 +0200, Alexander Yerenkow wrote:
> Hello there!
> I sometimes see in this list such mails:
> "I got problem with rXXXXXX"
> "It's known, it's fixed in rYYYYYY".
>
> Sometimes it's my problem, sometimes it's problem of other peoples.
>
> How about make simple web-service where revision numbers could be "marked"
> as bwoken, with minimal info - like next working rev?
>
> Can we make small sub-task while buildworld/buildkernel going, to simply
> fetch info about current rev and if it's broken warn user?
>
> This probably would improve user experience for those who use current, but
> have no time/proficiency to read commit logs.

On Tuesday, 13 November 2012 at 12:15:29 -0800, Jakub Lach wrote:
On Tuesday, 13 November 2012 at 12:15:29 -0800, Jakub Lach wrote:
> What about cases when something is broken, but not for everybody?

Just say so.

> If only GENERIC build, how does that differ from existing
> tinderboxing?

It's all in one place.

The idea sounds good to me.  All we need is somebody to implement it
and somebody to maintain it.

Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20121114/8b3ad629/attachment.sig>