summaryrefslogtreecommitdiff
path: root/pod/perlpolicy.pod
Commit message (Collapse)AuthorAgeFilesLines
* update the range of versions we support and do not supportKaren Etheridge2021-08-211-3/+3
|
* perlpolicy: update moderator listRicardo Signes2021-05-011-1/+1
|
* perlpolicy: remove Steffen Müller from moderatorsRicardo Signes2021-02-041-2/+1
|
* pod: update a few documents for perlgov changesRicardo Signes2020-12-281-24/+33
|
* perlpolicy: Adjust the list of moderators.Andy Dougherty2020-07-061-1/+1
|
* Bump perl version in various places for 5.32.0Sawyer X2020-05-301-3/+3
|
* Perl 6 -> Raku where appropriateH.Merijn Brand2020-05-301-1/+1
|
* Aaron Crane is a moderatorSawyer X2020-05-271-1/+1
|
* Update perlpolicy to reference GitHub issue trackerDan Book2019-11-261-3/+3
|
* Aaron Crane is no longer a p5p moderatorAaron Crane2019-10-201-1/+1
| | | | | Sorry, everybody: I no longer have time to keep up with the list, and it's therefore unreasonable to claim I can do an adequate job of moderation.
* Bump the perl version in various places for 5.30.0Sawyer X2019-05-101-3/+3
|
* Update perlpolicy for 5.28.0Sawyer X2018-05-201-3/+3
|
* perlpolicy: update policy in accordance with recent moderator discussionsAaron Crane2018-01-211-14/+32
| | | | | | | | | | | | | | | | | | | | | | | | | Substantive changes: Firstly, as promised earlier, we have clarified that, by forwarding a message to the list, the sender takes responsibility for the content of the message in question. Secondly, we have changed the policy regarding ban lengths. Previously, third or subsequent instances of unacceptable behaviour resulted in a ban twice the length of the person's previous ban. Under the new policy, a third instance of unacceptable behaviour results in a further warning, and a fourth instance results in a ban of indefinite length. Our rationale is that temporary bans are for the offender: to give them the opportunity to change their behaviour in a way that aligns with our community expectations. However, if the person in question fails to take advantage of that opportunity, our focus must shift to the community: we aim to protect other list members from having to bear the burden of unacceptable behaviour. Finally, we welcome Karen Etheridge and Todd Rinaldo as additional moderators. I'd like to offer both Karen and Todd my personal thanks for agreeing to serve.
* perlpolicy - Mention the maint-votes branchSteve Hay2017-07-201-11/+19
| | | | | | | | The maint-votes branch has been used for some time now to keep track of which commits should be cherry-picked into maint branches, but this has never been mentioned in perlpolicy.pod. Document it now to avoid possible confusion -- especially during long maint branch freeze periods, which occurred recently.
* perlpolicy: add Sawyer X to list moderatorsRicardo Signes2016-04-281-1/+1
|
* perlpolicy: update the supported versions for v5.24 onRicardo Signes2016-04-131-3/+3
|
* update security contact information.David Mitchell2016-04-081-4/+4
| | | | | | Point out that the security-reporting email address now creates an RT ticket. Also, consolidate this information purely within perlsec.pod, and make all the other places link to it with L<>.
* maint policy: allow fixes for new featuresAaron Crane2015-11-191-0/+5
| | | | | | | | | | | | | | | | | | | As (Steve Hay)++ said on-list: I think it's a shame if users get a 5.X.0 release with some shiny new features which I hope they're excited about and start making use of, but then find bugs in those features and have to wait until 5.X+2.0, rather than 5.X.1, for fixes. rjbs++ clarified that, although such changes constitute a break in backwards compatibility, there are two reasons why bugs in new features should be fixed in maint: * they delay people from using a feature for a year, because it does something stupid * they risk enshrining bad behavior under the usual program of bugward compatibility
* Require civility; aspire to kindness.Craig A. Berry2015-08-121-3/+7
| | | | | | Suggestion that we "aspire to kindness" from the ever-kind Tim Bunce. Signed-off-by: Ricardo Signes <rjbs@cpan.org>
* Update supported versions in perlpolicy.podMatthew Horsfall (alh)2015-03-261-3/+3
|
* maint policy: Note that some changes don't need voting onSteve Hay2015-03-061-0/+6
| | | | | Again, this is just a statement of the reality that I have experienced in the course of releasing 5.20.1 and 5.20.2.
* maint policy: Note that other voting mechanisms may be used instead of p5pSteve Hay2015-03-061-0/+5
| | | | | This simply reflects the reality of how 5.20.2's changes were voted on, namely, by the use of the maint-5.20-votes branch.
* maint policy: Reword/expand the ambiguous "as few changes as possible" phraseSteve Hay2015-03-061-1/+15
| | | | | | | | | | | | | | | This phrase caused much debate during the release of 5.20.2. A literal interpretation of it would be just a version bump, which was clearly not its intention. Debate ensued as to what was its real meaning, and the consensus seemed to be that the list of "acceptable"/"unacceptable" types of change was about right, but that not every eligible change should be included. Not many committers are interested in reviewing a long list of minor spelling corrections etc, causing a lack of interest in voting, and an attendant risk of something important being missed amongst all the "noise". The focus should mainly be on security / crash / regression / installation issues, with the aim being to produce a worthwhile release without needlessly increasing risk and/or burning people out. I hope the new wording captures this.
* maint policy: Move paragraph about controversial changesSteve Hay2015-03-061-3/+4
| | | | | | | | | The point was also raised during discussions over whether to include perlunicook.pod in 5.20.2 that exceptions can be made to the rules under the terms of "Rule 2" and the fact that the pumpking is acting on Larry's behalf. However, this is probably best left being implicit, rather than explicitly stating it. Exceptions should be exceptional; we don't want to encourage them!
* maint policy: Minor grammar and style changeSteve Hay2015-03-061-1/+1
|
* maint policy: Separate build/installation issues from test failuresSteve Hay2015-03-061-2/+6
| | | | Also clarify a what kind of build/installation "issue" we are referring to.
* maint policy: Note that old regressions are acceptable tooSteve Hay2015-03-061-1/+2
|
* maint policy: Put notes about CPAN modules in one placeSteve Hay2015-03-061-4/+4
|
* maint policy: No need to keep saying "are [NOT] acceptable" nowSteve Hay2015-03-061-16/+12
|
* maint policy: Sort acceptable/unacceptable lists into rough priority orderSteve Hay2015-03-061-26/+26
| | | | This commit makes no changes to any of the wording.
* maint policy: Separate acceptable/unacceptable changes into two litssSteve Hay2015-03-061-13/+23
|
* perlpolicy: add a missing verbRicardo Signes2015-01-061-1/+1
|
* perlpolicy: clarify what "feature can be replaced" meansRicardo Signes2015-01-051-7/+8
|
* perlpolicy: the point is caution, not low stakesRicardo Signes2015-01-051-2/+2
|
* forward reference from "new features" to "experimental"Ricardo Signes2015-01-051-1/+3
|
* proposed changes for perlpolicy updatesRicardo Signes2015-01-051-17/+13
| | | | see http://nntp.perl.org/group/perl.perl5.porters/219866
* perlpolicy: Be explicit wrt crashing bug policyFather Chrysostomos2014-12-091-1/+2
| | | | | This new wording states explicitly what has been the de facto under- standing of this policy of late.
* perlpolicy: clarify that bans related to RT as well as p5pRicardo Signes2014-09-241-4/+4
|
* document how to graduate from experimental statusRicardo Signes2014-09-151-0/+8
|
* perlpolicy - Add encoding to fix podcheck.t following 0c6082f411Steve Hay2014-07-181-0/+2
|
* perlpolicy: update list of moderatorsRicardo Signes2014-07-181-2/+2
|
* perlpolicy - Note that minimal build fixes are acceptable for maint tooSteve Hay2014-07-181-1/+1
| | | | | Changes like 31114fe991, which has just been cherry-picked into maint-5.20, should be allowed.
* Update which stable release series are now "officially" supportedSteve Hay2014-07-091-3/+3
|
* add the standards of conduct to perlpolicyRicardo Signes2014-07-071-4/+39
|
* perlpolicy: We generally deprecate for 2 major releasesKarl Williamson2014-05-041-4/+9
| | | | Update perlpolicy to reflect the current policy,
* perlpolicy: remove 5.12 references from maint cherry pick policyDavid Golden2012-11-081-4/+4
|
* perlpolicy.pod: clarify module deprecation/removalDavid Golden2012-09-271-6/+11
|
* with 5.16.0, 5.12.x is security-onlyRicardo Signes2012-05-071-3/+3
|
* yes, regression fixes are generally okay for maintRicardo Signes2012-03-201-0/+5
|
* 5.14.0 has been released, so update the versions used for support examples.Nicholas Clark2012-01-201-3/+3
| | | | Also state explicitly that 5.10.1 and earlier are now out of support.
View Lorry Controller Status