Enhance the "How do I know if my port is building correctly or not?" question. While there, axe the ports freeze category.
ClosedPublic
Actions

Authored by mat on Apr 29 2015, 9:25 PM.

Details

Reviewers

eadler
gjb
wblock

Diff Detail

Repository

rD FreeBSD doc repository - subversion

Lint

No Lint Coverage

Unit

No Test Coverage

Event Timeline

mat updated this revision to Diff 5092.Apr 29 2015, 9:25 PM

mat retitled this revision from to Enhance the "How do I know if my port is building correctly or not?" question. While there, axe the ports freeze category..

mat updated this object.

mat edited the test plan for this revision. (Show Details)

mat added reviewers: wblock, gjb.

mat added subscribers: Doc Committers, portmgr.

gjb accepted this revision.Apr 29 2015, 9:44 PM

gjb edited edge metadata.

This revision is now accepted and ready to land.Apr 29 2015, 9:44 PM

cool. I wasn't sure if we wanted to leave this question or not, but you're in a much better position to know :)

wblock added inline comments.Apr 30 2015, 12:10 AM

en_US.ISO8859-1/articles/committers-guide/article.xml
4253–4262	If this is no longer used, why not just remove the entry? If there is a reason to keep it... There are a lot of separate clauses in this sentence, and it is really more than one sentence. historical to ensure the quality of the packages shipped with a release used to be in a restricted state for a short period of time while most problems were fixed while the packages were being built Rearrange and split this up. I'd suggest explaining what a ports freeze was first, then in a separate sentence explain that it is no longer done. A <quote>ports freeze</quote> was ... This practice is no longer used. Packages for new releases are now built...
4256	s/builds/build/, but see above. s/short period of time/short time/
4263	If the <xref will not make this line too long, it is easier to read to keep it with the rest of the line.
4484	Passive->active: s/will be/is/ "will be emailed from" is a little weird. Maybe it means "will receive an email from"?
4487	"In addition" seems unnecessary. The "official..non-regression" part is really an aside and should be in parens if it is there: All package builds (official, experimental, and non-regression) are aggregated at... What does "aggregated" mean here?

mat added inline comments.Apr 30 2015, 11:57 AM

en_US.ISO8859-1/articles/committers-guide/article.xml
4253–4262	It's for historical reason, yes, so that people don't have to ask on a list what a port freeze is and why it's not documented.
4487	right now, there are six servers running the official i386/amd64 package builds, two other are running arm/mips builds, and a dozen other servers are running experimental and non-regression builds, pkg-status collects all the poudriere data from all the hosts and displays it in one place. I thought it was what aggregation is all about.

Rearrange the ports freeze question, and update the port is building correctly one.

This revision now requires review to proceed.Apr 30 2015, 12:08 PM

wblock added inline comments.Apr 30 2015, 2:12 PM

en_US.ISO8859-1/articles/committers-guide/article.xml
4262	Much better, thanks!
4487	"Aggregation" just means "combined". Saying the package builds are aggregated suggests that the builds are combined on one machine or cluster. But what it means here is that the status reports are combined and available. So maybe "Status reports for all of the package builds... are aggregated at..."