User avatar None

New strings to translate

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

New strings to translate 3 months ago
User avatar None

Resource update

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

Resource update 3 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

Hat currently held by: JosephMuhammad Moingroneur Rahman <email>jrmbofh@FreeBSD.org</email>.
3 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

$FreeBSD: head/en_US.ISO8859-1/books/dev-model/book.xml 519694306 201820-07-05 20:36:13Z jrm1 15:38:01Z bofh $
3 months ago
User avatar dbaio

New string to translate

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

New string to translate 4 months ago
Resource update 4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

The Documentation project has <link xlink:href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/">a primer</link>. This is used both to introduce new project members to the standard tools and syntaxes and to acts as a reference when working on the project.
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

<xref linkend="fig-ports"/> is taken from <link xlink:href="https://www.freebsd.org/ports/growth/status.png"> the FreeBSD web site</link>. It shows the number of ports available to FreeBSD in the period 1995 to 20058. It looks like the curve has first grown exponentionally, and then sincefrom the middle of 2001 to the middle of 20017 grown linearly at a rate of about 2000 ports/year, before its growth rate gets lower.
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

Number of ports added between 1996 and 20058
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

A <quote>port</quote> is a set of meta-data and patches that are needed to fetch, compile and install correctly an external piece of software on a FreeBSD system. The amount of ports haves grown at a tremendous rate, as shown by the following figure.
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

Pretty Good Privacy, better known as PGP, is a cryptosystem using a public key architecture to allow people to digitally sign and/or encrypt information in order to ensure secure communication between two parties. A signature is used when sending information out to many recipients, enabling them to verify that the information has not been tampered with before they received it. In the FreeBSD Project this is the primary means of ensuring that information has been written by the person who claims to have written it, and not altered in transit.
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

Mailman is a program that automates the management of mailing lists. The FreeBSD Project uses it to run 16 general lists, 60 technical lists, 4 limited lists and 5 lists with CVSSVN commit logs. It is also used for many mailing lists set up and used by other people and projects in the FreeBSD community. General lists are lists for the general public, technical lists are mainly for the development of specific areas of interest, and closed lists are for internal communication not intended for the general public. The majority of all the communication in the project goes through these 85 lists <citation><xref linkend="ref-bsd-handbook"/>, Appendix C</citation>.
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

Bugzilla is a maintenance database consisting of a set of tools to track bugs at a central site. It supports the bug tracking process for sending and handling bugs as well as querying and updating the database and editing bug reports. The project uses its web interface to send <quote>Problem Reports</quote> to the project's central Bugzilla server. The committers also have web and command-line clients.
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

Release branchescandidate
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

ReleasMake branches
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

For releases of the -STABLE-branch, the release process starts 45 days before the anticipated release date. During the first phase, the first 15 days, the developers merge what changes they have had in -CURRENT that they want to have in the release to the release branch. When this period is over, the code enters a 15 day code freeze in which only bug fixes, documentation updates, security-related fixes and minor device driver changes are allowed. These changes must be approved by the release engineer in advance. At the beginning of the last 15 day period a release candidate is created for widespread testing. Updates are less likely to be allowed during this period, except for important bug fixes and security updates. In this final period, all releases are considered release candidates. At the end of the release process, a release is created with the new version number, including binary distributions on web sites and the creation of a CD-ROM images. However, the release is not considered "really released" until a <xref linkend="tool-pgp"/>-signed message stating exactly that, is sent to the mailing list freebsd-announce; anything labelled as a "release" before that may well be in-process and subject to change before the PGP-signed message is sent. <_:footnote-1/>.
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

When a release is coming, the FreeBSD project changes shape somewhat. A release schedule is made containing feature- and code-freezes, release of interim releases and the final release. A feature-freeze means no new features are allowed to be committed to the branch without the release engineers' explicit consent. Code-freeze means no changes to the code (like bugs-fixes) are allowed to be committed without the release engineers' explicit consent. This feature- and code-freeze is known as stabilising. During the release process, the release engineer has the full authority to revert to older versions of code and thus "back out" changes should they find that the changes are not suitable to be included in the release.
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

For the suspensions to be efficient, any single core member can implement a suspension before discussing it on the <quote>core</quote> mailing list. Repeat offenders can, with a 2/3 vote by core, receive harsher penalties, including permanent removal of commit privileges. (However, the latter is always viewed as a last resort, due to its inherent tendency to create controversy).) All suspensions are posted to the <quote>developers</quote> mailing list, a list available to committers only.
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

<citation><xref linkend="freebsd-committer"/></citation> has a number of rules that committers should follow. However, it happens that these rules are broken. The following rules exist in order to be able to react to misbehavior. They specify what actions will result in how long a suspension of the committer's commit privileges. <_:itemizedlist-1/> <citation><xref linkend="ref-freebsd-trenches"/></citation>
4 months ago
User avatar None

Source string changed

FreeBSD Doc / books_dev-modelPortuguese (Brazil)

A problem is reported by the report originator. It is then classified by a bugbuster and handed to the correct maintainer. HeThey verifiesy the problem and discusses the problem with the originator until they hasve enough information to create a working patch. This patch is then committed and the problem report is closed.
4 months ago

Search