Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Merge remote branch 'origin/github-links'

  • Loading branch information...
commit 8b3aa4a5e508f5cff815e30fca94dc5a006c6d4f 2 parents a8aab9f + de92e5e
@moritz moritz authored
Showing with 125 additions and 269 deletions.
  1. +1 −1  README
  2. +1 −1  RESPONSIBLE_PARTIES
  3. +3 −3 TODO
  4. +36 −36 api.yaml
  5. +1 −1  config/gen/makefiles/root.in
  6. +2 −2 docs/book/draft/appe_source_code.pod
  7. +7 −7 docs/book/draft/ch01_introduction.pod
  8. +7 −7 docs/book/pct/ch01_introduction.pod
  9. +7 −8 docs/book/pir/ch01_introduction.pod
  10. +2 −2 docs/deprecations/deprecations.pod
  11. +1 −1  docs/faq.pod
  12. +1 −1  docs/gettingstarted.pod
  13. +3 −3 docs/intro.pod
  14. +0 −2  docs/parrot.pod
  15. +1 −1  docs/project/cage_cleaners_guide.pod
  16. +2 −27 docs/project/metacommitter_guide.pod
  17. +1 −1  docs/project/release_manager_guide.pod
  18. +7 −3 docs/project/ticket_triaging.pod
  19. +21 −141 docs/submissions.pod
  20. +1 −1  docs/translations/README.BGR
  21. +1 −1  docs/translations/README.deutsch
  22. +1 −1  docs/translations/README.espanol
  23. +1 −1  docs/translations/README.francais
  24. +1 −1  docs/translations/README.polski
  25. +1 −1  docs/translations/README.pt-BR
  26. +2 −2 examples/languages/abc/setup.pir
  27. +1 −1  examples/languages/squaak/doc/tutorial_episode_1.pod
  28. +2 −2 examples/pir/befunge/setup.pir
  29. +2 −3 parrotbug
  30. +2 −2 src/ops/experimental.ops
  31. +3 −2 src/ops/sys.ops
  32. +1 −1  src/string/api.c
  33. +1 −1  t/pmc/exporter.t
  34. +1 −1  t/tools/install/testlib/README
View
2  README
@@ -170,8 +170,8 @@ WEB SITES
The following web sites have all the information you need about Parrot:
http://www.parrot.org/
- http://trac.parrot.org/
http://docs.parrot.org/
+ https://github.com/parrot/parrot/
Have fun,
The Parrot Team.
View
2  RESPONSIBLE_PARTIES
@@ -6,7 +6,7 @@ commit access, just those who have a role they've taken responsibility
for.
See docs/project/roles_responsibilities.pod for role definitions, and
-https://trac.parrot.org/parrot/wiki/Languages for language authors/maintainers.
+https://github.com/parrot/parrot/wiki/Languages for language authors/maintainers.
Project Team
View
6 TODO
@@ -1,9 +1,9 @@
-All todo items should have a corresponding trac ticket. See the current list:
+All todo items should have a corresponding github issue. See the current list:
- https://trac.parrot.org/parrot/report/9
+ https://github.com/parrot/parrot/issues?labels=todo
To open a new todo ticket, use
- https://trac.parrot.org/
+ https://github.com/parrot/parrot/issues/new
View
72 api.yaml
@@ -12,7 +12,7 @@
tags:
- 'PMC'
- 'experimental'
- ticket: 'http://trac.parrot.org/parrot/ticket/2034'
+ ticket: 'https://github.com/parrot/parrot/issues/651'
-
name: '"Advanced" NCI parameter types'
eligible: '3.1'
@@ -23,7 +23,7 @@
-
name: 'Pointer, UnManagedStruct, and ManagedStruct'
eligible: '3.4'
- ticket: 'http://trac.parrot.org/parrot/ticket/2035'
+ ticket: 'https://github.com/parrot/parrot/issues/657'
-
name: 'add write barrier to all PMCs that write in unusual VTABLE functions'
eligible: '3.4'
@@ -44,7 +44,7 @@
detection:
regex:
pir: '^ ".sub" .+ ":init"'
- ticket: 'https://trac.parrot.org/parrot/ticket/1896'
+ ticket: 'https://github.com/parrot/parrot/issues/469'
-
name: '":load" and ":init" Sub flags doing different things'
eligible: '3.1'
@@ -63,9 +63,9 @@
- 'PIR'
- 'syntax'
tickets:
- - 'https://trac.parrot.org/parrot/ticket/1033'
- - 'https://trac.parrot.org/parrot/ticket/1704'
- - 'https://trac.parrot.org/parrot/ticket/1705'
+ - 'https://github.com/parrot/parrot/issues/600'
+ - 'https://github.com/parrot/parrot/issues/571'
+ - 'https://github.com/parrot/parrot/issues/578'
-
name: 'Action methods in rules'
note: 'Per Synopsis 5, all regexes will have an implied {*} token at the end which cause invocation of an action method if a ":action" object is supplied.'
@@ -79,7 +79,7 @@
tags:
- 'library'
- 'experimental'
- ticket: 'https://trac.parrot.org/parrot/ticket/1598'
+ ticket: 'https://github.com/parrot/parrot/issues/375'
-
name: 'Assigning to registers in parrot_debugger'
tags:
@@ -112,13 +112,13 @@
detection:
regex:
pir: 'new\s\[?\''Complex\''\]?'
- ticket: 'https://trac.parrot.org/parrot/ticket/1892'
+ ticket: 'https://github.com/parrot/parrot/issues/462'
-
name: 'Cross-HLL library loading'
tags:
- 'library'
- 'experimental'
- ticket: 'https://trac.parrot.org/parrot/ticket/754'
+ ticket: 'https://github.com/parrot/parrot/issues/266'
-
name: 'GC timely destruction'
eligible: '3.1'
@@ -126,14 +126,14 @@
tags:
- 'deprecated'
- 'functions'
- ticket: 'https://trac.parrot.org/parrot/ticket/1800'
+ ticket: 'https://github.com/parrot/parrot/issues/278'
-
name: 'GC_SYS_NAME option to interpinfo_s_i'
note: 'Ability to get the string name of the current GC core from the interpinfo_s_i. See r43900 and r43904 for details.'
tags:
- 'Opcodes'
- 'experimental'
- ticket: 'https://trac.parrot.org/parrot/ticket/1581'
+ ticket: 'https://github.com/parrot/parrot/issues/347'
-
name: 'IPv6 Support'
tags:
@@ -146,13 +146,13 @@
tags:
- 'deprecated'
- 'library'
- ticket: 'https://trac.parrot.org/parrot/ticket/508'
+ ticket: 'https://github.com/parrot/parrot/issues/494'
-
name: 'LWP, https::Message, URI & URI::Escape'
tags:
- 'library'
- 'experimental'
- ticket: 'https://trac.parrot.org/parrot/ticket/1637'
+ ticket: 'https://github.com/parrot/parrot/issues/431'
-
name: 'ManagedStruct reallocations based on shape changes'
eligible: '2.4'
@@ -160,13 +160,13 @@
tags:
- 'deprecated'
- 'PMC'
- ticket: 'https://trac.parrot.org/parrot/ticket/1554'
+ ticket: 'https://github.com/parrot/parrot/issues/319'
-
name: 'MappedByteArray PMC'
tags:
- 'PMC'
- 'experimental'
- ticket: 'https://trac.parrot.org/parrot/ticket/1877'
+ ticket: 'https://github.com/parrot/parrot/issues/420'
-
name: 'Meta-model implementation used by PCT'
eligible: '2.7'
@@ -189,7 +189,7 @@
tags:
- 'opcodes'
- 'experimental'
- ticket: 'https://trac.parrot.org/parrot/ticket/1582'
+ ticket: 'https://github.com/parrot/parrot/issues/354'
-
name: 'OpenGL bindings and libraries'
tags:
@@ -227,7 +227,7 @@
tags:
- 'deprecated'
- 'compiler'
- ticket: 'https://trac.parrot.org/parrot/ticket/463'
+ ticket: 'https://github.com/parrot/parrot/issues/464'
-
name: 'PCT::HLLCompiler stages'
eligible: '1.1'
@@ -256,7 +256,7 @@
tags:
- 'PMC'
- 'experimental'
- ticket: 'https://trac.parrot.org/parrot/ticket/1599'
+ ticket: 'https://github.com/parrot/parrot/issues/382'
-
name: 'Parrot_load_bytecode_file'
note: 'Load a .pbc file into the interpreter. Experimental.'
@@ -310,7 +310,7 @@
tags:
- 'deprecated'
- 'PMC'
- ticket: 'https://trac.parrot.org/parrot/ticket/1553'
+ ticket: 'https://github.com/parrot/parrot/issues/311'
-
name: 'UnManagedStruct handling nested structure'
eligible: '2.4'
@@ -318,7 +318,7 @@
tags:
- 'PMC'
- 'deprecated'
- ticket: 'https://trac.parrot.org/parrot/ticket/1551'
+ ticket: 'https://github.com/parrot/parrot/issues/298'
-
name: 'UnManagedStruct initializer structure'
eligible: '2.4'
@@ -326,7 +326,7 @@
tags:
- 'deprecated'
- 'PMC'
- ticket: 'https://trac.parrot.org/parrot/ticket/1552'
+ ticket: 'https://github.com/parrot/parrot/issues/305'
-
name: 'charset, charsetname, find_charset, trans_charset'
eligible: '2.10'
@@ -352,7 +352,7 @@
tags:
- 'deprecated'
- 'opcodes'
- ticket: 'https://trac.parrot.org/parrot/ticket/1565'
+ ticket: 'https://github.com/parrot/parrot/issues/340'
-
name: 'finalize'
note: 'Finalize exception handler, unrolling inner runloops if needed.'
@@ -377,7 +377,7 @@
tags:
- 'deprecated'
- 'opcodes'
- ticket: 'https://trac.parrot.org/parrot/ticket/218'
+ ticket: 'https://github.com/parrot/parrot/issues/303'
-
name: 'get_results opcode order and features'
eligible: '2.1'
@@ -411,7 +411,7 @@
tags:
- 'opcodes'
- 'experimental'
- ticket: 'https://trac.parrot.org/parrot/ticket/1583'
+ ticket: 'https://github.com/parrot/parrot/issues/361'
-
name: 'logical PMC ops'
eligible: '2.7'
@@ -434,7 +434,7 @@
tags:
- 'deprecated'
- 'functions'
- ticket: 'https://trac.parrot.org/parrot/ticket/907'
+ ticket: 'https://github.com/parrot/parrot/issues/460'
-
name: 'multiple dispatch within core PMC'
eligible: '1.1'
@@ -449,7 +449,7 @@
tags:
- 'deprecated'
- 'opcodes'
- ticket: 'https://trac.parrot.org/parrot/ticket/1548'
+ ticket: 'https://github.com/parrot/parrot/issues/291'
-
name: 'opcode numbering'
tags:
@@ -464,7 +464,7 @@
tags:
- 'deprecated'
- 'opcodes'
- ticket: 'https://trac.parrot.org/parrot/ticket/1697'
+ ticket: 'https://github.com/parrot/parrot/issues/550'
-
name: 'packfile structure'
tags:
@@ -486,7 +486,7 @@
tags:
- 'experimental'
- 'functions'
- ticket: 'https://trac.parrot.org/parrot/ticket/1996'
+ ticket: 'https://github.com/parrot/parrot/issues/602'
-
name: 'LANG search path with -L'
tags:
@@ -508,7 +508,7 @@
name : 'Eval PMC'
tags:
- 'deprecated'
- ticket: 'http://trac.parrot.org/parrot/ticket/1969'
+ ticket: 'https://github.com/parrot/parrot/issues/567'
-
name : 'PackFile_* API functions'
tags :
@@ -524,7 +524,7 @@
name : 'load_bytecode_p_s opcode'
tags :
- 'experimental'
- ticket : 'http://trac.parrot.org/parrot/ticket/2146'
+ ticket : 'https://github.com/parrot/parrot/issues/435'
-
name : 'FixedPMCArray.set_pmc'
eligible : '3.1'
@@ -535,7 +535,7 @@
-
name : 'Scalar PMC'
note : 'The Scalar PMC can be removed, so long as the behaviors of PMCs which inherit from it do not change.'
- ticket : 'https://trac.parrot.org/parrot/ticket/1754'
+ ticket : 'https://github.com/parrot/parrot/issues/672'
eligible : '3.1'
-
name : 'encoding:charset:"" string literals'
@@ -551,11 +551,11 @@
name : 'PIR compiler availability'
eligible : '3.1'
note : 'The PIR compiler (currently IMCC) will be extracted to a separately loadable component.'
- ticket : 'http://trac.parrot.org/parrot/ticket/1868'
+ ticket : 'https://github.com/parrot/parrot/issues/406'
-
name : '"constant" PObj'
eligible : '3.1'
- note :
+ note:
"constant" PObj (which is never collected) are deprecated. All PMCs and STRINGs
should be properly marked during GC.
@@ -571,7 +571,7 @@
-
name : 'Non-const STRING* arguments'
eligible : '3.1'
- note :
+ note :
Due to the immutable nature of STRINGs we are changing the internal handling to use only
const STRING pointers. This will improve optimizations possibilities for compilers,
and make parrot const-correct.
@@ -579,12 +579,12 @@
Passing of non-const STRING* arguments is deprecated and will be changed to
const STRING*. This includes (but is not limited to) all string API functions,
VTABLEs, PCC, etc
- ticket : 'http://trac.parrot.org/parrot/ticket/1906'
+ ticket : 'https://github.com/parrot/parrot/issues/483'
-
name : 'X-to-Y native PBC reading'
eligible : '3.1'
note : 'Support for PBC files optimized for alternate platforms will be dropped in favour of a universal network PBC format.'
- ticket : 'https://trac.parrot.org/parrot/ticket/1961'
+ ticket : 'https://github.com/parrot/parrot/issues/553'
-
name : 'The PIR and PASM compreg PMCs'
eligible : '3.1'
View
2  config/gen/makefiles/root.in
@@ -808,7 +808,7 @@ help :
@echo "Fetch from source repository:"
@echo " update: git pull."
@echo " status: git status."
- @echo " patch: Create a patch to attach to https://trac.parrot.org/"
+ @echo " patch: Create a patch to attach to https://github.com/parrot/parrot/issues"
@echo ""
@echo "Development:"
@echo " lint: An alias for sunlint."
View
4 docs/book/draft/appe_source_code.pod
@@ -15,7 +15,7 @@ If you plan to get involved in development, you'll want to check out
the source from the git repository directly. Anyone can get
anonymous access to read the files and download a working copy to
explore and test. For commit access, volunteers need a
-U<https://trac.parrot.org> username, and need to be approved by a
+U<https://github.com> username, and need to be approved by a
Metacommitter. To download the most recent version from git, type this
command into your terminal N<This is for Linux users, on Mac or
Windows systems, follow the instructions from your git client>:
@@ -42,7 +42,7 @@ There are a number of existing language implementations for Parrot:
Perl 6, Python ("Pynie"), Ruby ("Cardinal"), PHP ("Pipp"), Lisp, Lua,
Tcl ("partcl"), WMLScript, Forth, Scheme, Befunge, BASIC, and many
others. These language compilers are in various stages of partial
-completion. The page L<https://trac.parrot.org/parrot/wiki/Languages>
+completion. The page L<https://github.com/parrot/parrot/wiki/Languages>
provides meta information on these languages and where to find them.
If you have a language you're particularly interested to see implemented
on Parrot, you can see how far along the effort is, or you can start the
View
14 docs/book/draft/ch01_introduction.pod
@@ -55,13 +55,13 @@ questions or see how things are progressing.
=head3 Issue Tracking & Wiki
-X<trac.parrot.org website>
-X<issue tracking (trac.parrot.org)>
+X<github.com wiki>
+X<issue tracking (github.com)>
-Parrot developers track issues with a Trac site at U<https://trac.parrot.org/>.
-Users can submit new tickets and track the status of existing tickets. The
-site also includes a wiki used in project development, a source code browser,
-and the project roadmap.
+Parrot developers track issues using the Github issues system at
+L<https://github.com/parrot/parrot/issues/> Users can submit new tickets and
+track the status of existing tickets. Github also provides a wiki used in
+project development and a source code browser.
=head2 Parrot Development
@@ -150,7 +150,7 @@ Developers who work on any of the high-level languages that target
ParrotE<mdash>such as Lua, Perl, PHP, Python, Ruby, or TclE<mdash>are
high-level language developers. The Parrot repository includes a few example
languages. A full list of languages is available at
-U<https://trac.parrot.org/parrot/wiki/Languages>.
+L<https://github.com/parrot/parrot/wiki/Languages>
=item Build Manager
View
14 docs/book/pct/ch01_introduction.pod
@@ -55,13 +55,13 @@ questions or see how things are progressing.
=head3 Issue Tracking & Wiki
-X<trac.parrot.org website>
-X<issue tracking (trac.parrot.org)>
+X<github.com wiki>
+X<issue tracking (github.com)>
-Parrot developers track issues with a Trac site at U<https://trac.parrot.org/>.
-Users can submit new tickets and track the status of existing tickets. The
-site also includes a wiki used in project development, a source code browser,
-and the project roadmap.
+Parrot developers track issues using the Github issues system at
+L<https://github.com/parrot/parrot/issues/> Users can submit new tickets and
+track the status of existing tickets. Github also provides a wiki used in
+project development and a source code browser.
=head2 Parrot Development
@@ -150,7 +150,7 @@ Developers who work on any of the high-level languages that target
ParrotE<mdash>such as Lua, Perl, PHP, Python, Ruby, or TclE<mdash>are
high-level language developers. The Parrot repository includes a few example
languages. A full list of languages is available at
-U<https://trac.parrot.org/parrot/wiki/Languages>.
+L<https://github.com/parrot/parrot/wiki/Languages>
=item Build Manager
View
15 docs/book/pir/ch01_introduction.pod
@@ -69,14 +69,13 @@ Parrot in real time.
=head3 Issue Tracking & Wiki
-X<trac.parrot.org website>
-X<issue tracking (trac.parrot.org)>
-
-Parrot developers track bugs, feature requests, and roadmap tasks at
-U<https://trac.parrot.org/>, the open source Trac issue tracker. Users
-can submit new tickets and track the status of existing tickets. The
-site also includes a wiki used in project development, a source code
-browser, and the project roadmap.
+X<github.com wiki>
+X<issue tracking (github.com)>
+
+Parrot developers track issues using the Github issues system at
+L<https://github.com/parrot/parrot/issues/> Users can submit new tickets and
+track the status of existing tickets. Github also provides a wiki used in
+project development and a source code browser.
=head2 Parrot Development
View
4 docs/deprecations/deprecations.pod
@@ -66,7 +66,7 @@ notice here and F<deprecations_3_0.pod>, so the list should
be exhaustive.
If you find a deprecation that should be listed here, file a ticket
- L<http://trac.parrot.org/parrot/newticket>
+ L<https://github.com/parrot/parrot/issues/new>
or hop on #parrot on irc.parrot.org and let us know.
=over 4
@@ -146,7 +146,7 @@ This list is a summary. A more complete description and migration path for
each change is at F<deprecations_2_9.pod>.
If you find a deprecation that should be listed here, file a ticket
- L<http://trac.parrot.org/parrot/newticket>
+ L<https://github.com/parrot/parrot/issues/new>
or hop on #parrot on irc.parrot.org and let us know.
=over 4
View
2  docs/faq.pod
@@ -39,7 +39,7 @@ PIR is a high-level assembly language. See the L<examples> directory.
While the languages that are shipped with our pre-release versions of
parrot are in varying states of development, many of them are quite
-functional. See L<https://trac.parrot.org/parrot/wiki/Languages>
+functional. See L<https://github.com/parrot/parrot/wiki/Languages>
for information about the various languages that are targeting parrot.
=head2 What language is Parrot written in?
View
2  docs/gettingstarted.pod
@@ -194,4 +194,4 @@ See F<docs/submissions.pod> for details.
=head2 What other useful resources are there for developers?
A number of other useful resources that can be found via on the Parrot
-wiki, located at L<http://trac.parrot.org/parrot/wiki>.
+wiki, located at L<https://github.com/parrot/parrot/wiki>
View
6 docs/intro.pod
@@ -131,9 +131,9 @@ with. When this completes, you will have a working C<parrot> executable.
Please report any problems that you encounter while building Parrot so the
developers can fix them. You can do this by creating a login and opening
-a new ticket at L<https://trac.parrot.org>. Please include the F<myconfig>
-file that was generated as part of the build process and any errors that you
-observed.
+a new ticket at L<https://github.com/parrot/parrot/issues/new>. Please
+include the F<myconfig> file that was generated as part of the build
+process and any errors that you observed.
=head2 The Parrot test suite
View
2  docs/parrot.pod
@@ -135,8 +135,6 @@ See:
=item * L<http://www.parrot.org/>
-=item * L<https://trac.parrot.org/>
-
=item * L<http://github.com/parrot/parrot>
=back
View
2  docs/project/cage_cleaners_guide.pod
@@ -367,6 +367,6 @@ Paul Cochrane a.k.a. ptc; original document by Andy Lester
=head1 SEE ALSO
F<docs/project/roles_responsibilities.pod>, F<RESPONSIBLE_PARTIES>
-and the list of Cage items in Trac L<http://trac.parrot.org>.
+and the list of Cage items in github L<https://github.com/parrot/parrot/issues?labels=cage&state=open>.
=cut
View
29 docs/project/metacommitter_guide.pod
@@ -47,34 +47,9 @@ pending list-admin approval.
=head2 To manage the list of Metacommitters
-Only existing Metacommitters can perform this activity.
+To make somebody a new metacommitter, add their github account to the "Owners"
+team at L<https://github.com/organizations/parrot/teams/>.
-=over 4
-
-=item 1
-
-Navigate to the Admin -> Permissions page
-L<https://trac.parrot.org/parrot/admin/general/perm> and add/remove
-"admin" users as desired.
-
-=back
-
-=head2 To manage the list of Bug Admins.
-
-Only existing Metacommitters can perform this activity.
-
-=over 4
-
-=item 1
-
-Navigate to the Admin -> Permissions page
-L<https://trac.parrot.org/parrot/admin/general/perm> and add/remove
-"developer" users as desired.
-
-Verify that the username is the one the user intends to use to
-administer tickets. (Some bugadmins have multiple Trac accounts.)
-
-=back
=head1 SEE ALSO
View
2  docs/project/release_manager_guide.pod
@@ -64,7 +64,7 @@ C<parrot-dev@lists.parrot.org> and to the IRC channel C<#parrot>. Ask whether
there are any showstopping bugs. Check in again with the language
project leads. It's also good to ask for updates to F<ChangeLog>, F<CREDITS>,
F<PLATFORMS>, F<RESPONSIBLE_PARTIES>, F<api.yaml> and
-L<http://trac.parrot.org/parrot/wiki/Languages>.
+L<https://github.com/parrot/parrot/wiki/Languages>.
=item 6
View
10 docs/project/ticket_triaging.pod
@@ -16,15 +16,19 @@ F<docs/submissions.pod>.
=head1 WHAT ABOUT TRAC?
-Our preferred method of bug tracking at this point is trac:
-L<https://trac.parrot.org/>
+Our preferred method of bug tracking at this point is github issues:
+L<https://github.com/parrot/parrot/issues/>
All Parrot developers are expected to pitch in and help keep the ticket tracker
in a healthy state. I<This means you!> Most of the document below still makes
sense in terms of activities in trac, but the specifics are of course different
with the new system.
-Our previous bug tracking system was RT. In November 2009 all remaining RT
+Our previous bug tracking system was trac, hosted at
+L<https://trac.parrot.org/>. In January 2012 the trac tickets have been
+migrated to github issues.
+
+The bug tracking system before trac was RT. In November 2009 all remaining RT
tickets were closed, with many being reopened in Trac. No new issues should
be opened in RT, but the old system is available at L<https://rt.perl.org>.
The Parrot issues are in the queue I<parrot>.
View
162 docs/submissions.pod
@@ -18,10 +18,7 @@ simplest way to use it is to run
in the distribution's root directory, and follow the prompts.
-If you just want to use email to create the bug report, send an email to
-L<tickets@parrot.org>.
-
-If you know how to fix the problem you encountered, then think about
+If you know how to fix the problem you encountered, then think about
submitting a patch, or (see below) getting commit privileges.
=head1 A Note on Random Failures
@@ -84,11 +81,9 @@ for whatever the distribution's parent directory is called on your machine.
=item C<git>
-If you are working with a git repository of parrot then please generate
-your patch with C<git diff>.
-
- cd parrot
- git diff > my_contribution.patch
+If you are working with a git repository of parrot then please submit your
+patch as a pull request on github. You can find instructions at
+L<http://help.github.com/send-pull-requests/>
=item Single C<diff>
@@ -128,57 +123,9 @@ The format for entries in F<CREDITS> is defined at the top of the file.
=head1 How To Submit A Patch
-=over 4
-
-=item 1
-
-Go to Parrot's ticket tracking system at
-L<https://trac.parrot.org/parrot/>. Log in, or create an account if you
-don't have one yet.
-
-=item 2
-
-If there is already a ticket for the bug or feature that your patch relates
-to, just attach the patch directly to the ticket.
-
-=item 3
-
-Otherwise select "New Ticket" at the top of the site.
-L<https://trac.parrot.org/parrot/newticket>
-
-=item 4
-
-Give a clear and concise Summary. You do B<NOT> need to prefix the Summary
-with a C<[PATCH]> identifier. Instead, in the lower-right corner of the
-F<newticket> page, select status C<new> in the F<Patch status> drop-down box.
-
-=item 5
-
-The Description should contain an explanation of the purpose of the patch, and
-a list of all files affected with summary of the changes made in each file.
-Optionally, the output of the C<diffstat(1)> utility when run on your patch(s)
-may be included at the bottom of the message body.
-
-=item 6
-
-Set the Type of the ticket to "patch". Set other relevant drop-down
-menus, such as Version (the version of Parrot where you encountered the
-problem), Platform, or Severity. As mentioned above, select status C<new> in
-the F<Patch status> drop-down box.
-
-=item 7
-
-Check the box for "I have files to attach to this ticket". Double-check
-that you've actually done this, because it's easy to forget.
-
-B<DO NOT> paste the patch file content into the Description.
-
-=item 8
-
-Click the "Create ticket" button. On the next page attach your patch
-file(s).
-
-=back
+The preferrred method to submit matches to Parrot is as pull requests via
+github. Please follow the instructions at
+L<http://help.github.com/send-pull-requests/>.
=head1 Applying Patches
@@ -216,88 +163,21 @@ the MANIFEST and MANIFEST.SKIP file should be regenerated with:
perl tools/dev/mk_manifest_and_skip.pl
-=head1 How To Submit Something New
-
-If you have a new feature to add to Parrot, such as a new test.
-
-=over
-
-=item 1
-
-Add your new file path(s), relative to F<parrot>, to the file MANIFEST. Create
-a patch for the MANIFEST file according to the instructions in B<How To Submit
-A Patch>.
-
-=item 2
-
-If you have a new test script ending in C<.t>, some mailers may become confused
-and consider it an application/x-troff. One way around this (for *nix users) is
-to diff the file against /dev/null like this:
-
- cd parrot
- diff -u /dev/null newfile.t > newfile.patch
-
-=item 3
-
-Go to Parrot's ticket tracking system at
-L<https://trac.parrot.org/parrot/>. Log in, or create an account if you
-don't have one yet.
-
-=item 4
-
-Select "New Ticket" L<https://trac.parrot.org/parrot/newticket>.
-
-=item 5
-
-Give a clear and concise Summary.
-
-Prefix it with a C<[NEW]> identifier.
-
-=item 6
-
-The Description should contain an explanation of the purpose of the feature
-you are adding. Optionally, include the output of the C<diffstat(1)> utility
-when run on your patch(es).
-
-=item 7
-
-Set the Type of the ticket to "patch". Set other relevant drop-down
-menus, such as Version, Platform, or Severity.
-
-=item 8
-
-Check the box for "I have files to attach to this ticket"
-
-Double-check that you've actually done this, because it's easy to forget.
-
-B<DO NOT> paste the content of the new file or files into the body of the
-message.
-
-=item 9
-
-Click the "Create ticket" button. On the next page attach the patch for
-MANIFEST and your new file(s).
-
-=back
-
=head1 What Happens Next?
-If you created a new ticket for the submission, you will be taken to the page
-for the new ticket and can check on the progress of your submission there.
-This identifier should be used in all correspondence concerning the submission.
-
-Everyone on Trac sees the submission and can comment on it. A developer with
-git commit privileges can commit it to git once it is clear that it is the
-right thing to do.
-
-However developers with commit privileges may not commit your changes
-immediately if they are large or complex, as we need time for peer review.
+If you created a new issue, you will be taken to the issue page and can
+check on the progress of discussion there. The issue number should be
+used in all out-of-band correspondence concerning the issue (e.g., in
+email to the C<parrot-dev> mailing list). Otherwise, everyone on the
+parrot project can see the issue and can comment on it.
-A list of active tickets can be found here:
-L<http://trac.parrot.org/parrot/report/1>
+A developer with git commit privileges can merge your changes into the
+main parrot repository, once it is clear that this is the right thing to
+do. However your pull request may not be processed right away if the
+changes are large or complex, as we need time for peer review.
-A list of all the unresolved patches is at:
-L<http://trac.parrot.org/parrot/report/15>
+A list of open issues can be found here:
+L<https://github.com/parrot/parrot/issues?state=open>
=head1 Patches for the Parrot website
@@ -313,12 +193,12 @@ the procedure:
=item 1
-Submit several high quality patches (and have them committed) via the process
-described in this document. This process may take weeks or months.
+Obtain a github account at L<http://github.com>
=item 2
-Obtain a Trac account at L<https://trac.parrot.org/parrot>
+Submit several high quality patches (and have them committed) via the process
+described in this document. This process may take weeks or months.
=item 3
View
2  docs/translations/README.BGR
@@ -169,8 +169,8 @@ docs/submissions.pod. Тези документи са в POD формат. М
Тези сайтове съдържат всичките нужна информация за Parrot:
http://www.parrot.org/
- http://trac.parrot.org/
http://docs.parrot.org/
+ https://github.com/parrot/parrot/
Забавлявайте се,
Екипът на Parrot.
View
2  docs/translations/README.deutsch
@@ -184,8 +184,8 @@ WEBSEITEN
Die folgenden Webseiten geben alle Informationen, die Sie brauchen, über Parrot:
http://www.parrot.org/
- http://trac.parrot.org/
http://docs.parrot.org/
+ https://github.com/parrot/parrot/
Viel Spaß,
Ihr Parrot-Team
View
2  docs/translations/README.espanol
@@ -176,8 +176,8 @@ SITIOS WEB
Los siguientes sitios web contienen toda la información que necesitas sobre Parrot:
http://www.parrot.org/
- http://trac.parrot.org/
http://docs.parrot.org/
+ https://github.com/parrot/parrot/
Que se diviertan,
El equipo de Parrot.
View
2  docs/translations/README.francais
@@ -182,8 +182,8 @@ SITES WEB
Les sites web suivants contiennent toutes les informations dont vous pourriez
avoir besoin sur Parrot:
http://www.parrot.org/
- http://trac.parrot.org/
http://docs.parrot.org/
+ https://github.com/parrot/parrot/
Amusez vous bien,
L'Équipe Parrot.
View
2  docs/translations/README.polski
@@ -179,8 +179,8 @@ STRONY INTERNETOWE
Następujące strony przechowują wszelkie informacje o Parrocie, jakie mogą
być Ci potrzebne:
http://www.parrot.org/
- http://trac.parrot.org/
http://docs.parrot.org/
+ https://github.com/parrot/parrot/
Miłej zabawy,
The Parrot Team.
View
2  docs/translations/README.pt-BR
@@ -184,8 +184,8 @@ WEB SITES
Os seguintes sites contém todas as informações que você precisa saber
sobre Parrot.
http://www.parrot.org/
- http://trac.parrot.org/
http://docs.parrot.org/
+ https://github.com/parrot/parrot/
Se divirta,
A equipe do Parrot.
View
4 examples/languages/abc/setup.pir
@@ -32,8 +32,8 @@ See F<runtime/library/distutils.pir>.
$P0['license_uri'] = 'http://www.perlfoundation.org/artistic_license_2_0'
$P0['copyright_holder'] = 'Parrot Foundation'
$P0['checkout_uri'] = 'https://github.com/parrot/parrot/tree/master/examples/languages/abc'
- $P0['browser_uri'] = 'http://trac.parrot.org/parrot/browser/trunk/examples/languages/abc'
- $P0['project_uri'] = 'http://trac.parrot.org/parrot/browser/trunk/examples/languages/abc'
+ $P0['browser_uri'] = 'https://github.com/parrot/parrot/tree/master/examples/languages/abc'
+ $P0['project_uri'] = 'https://github.com/parrot/parrot/tree/master/examples/languages/abc'
# build
$P1 = new 'Hash'
View
2  examples/languages/squaak/doc/tutorial_episode_1.pod
@@ -273,7 +273,7 @@ F<compilers/pct/src/PCT/HLLCompiler.pir>.
=item * Perl 6/NQP rules syntax: Synopsis 5 at http://perlcabal.org/syn/S05.html or http://svn.pugscode.org/pugs/docs/Perl6/Spec/S05-regex.pod
-=item * List of HLL projects: http://trac.parrot.org/parrot/wiki/Languages
+=item * List of HLL projects: https://github.com/parrot/parrot/wiki/Languages
=back
View
4 examples/pir/befunge/setup.pir
@@ -32,8 +32,8 @@ See F<runtime/library/distutils.pir>.
$P0['license_uri'] = 'http://www.perlfoundation.org/artistic_license_2_0'
$P0['copyright_holder'] = 'Parrot Foundation'
$P0['checkout_uri'] = 'https://github.com/parrot/parrot/tree/master/examples/pir/befunge'
- $P0['browser_uri'] = 'http://trac.parrot.org/parrot/browser/trunk/examples/pir/befunge'
- $P0['project_uri'] = 'http://trac.parrot.org/parrot/browser/trunk/examples/pir/befunge'
+ $P0['browser_uri'] = 'https://github.com/parrot/parrot/tree/master/examples/pir/befunge'
+ $P0['project_uri'] = 'https://github.com/parrot/parrot/tree/master/examples/pir/befunge'
# build
$P1 = new 'Hash'
View
5 parrotbug
@@ -584,9 +584,8 @@ sub save_report {
print <<TRAC;
Message saved. Please go to
- https://trac.parrot.org/parrot/newticket
- and either paste content of saved file into 'Description'
- or attach file to ticket.
+ https://github.com/parrot/parrot/issues
+ and paste content of saved file into 'Description'
TRAC
}
View
4 src/ops/experimental.ops
@@ -21,8 +21,8 @@ This file contains experimental opcodes.
These opcodes should be considered implicitly deprecated - that is, they
may be removed in any release.
-If you rely on any of these opcodes, please open a
-Trac ticket at L<https://trac.parrot.org/>.
+If you rely on any of these opcodes, please open an issue at
+L<https://github.com/parrot/parrot/issues>
When making changes to any ops file, run C<make bootstrap-ops> to regenerate
all generated ops files.
View
5 src/ops/sys.ops
@@ -33,10 +33,11 @@ system-dependent, goes in $1.
TT #847: C<spawnw()> should itself handle splitting up command-line arguments,
rather than depending on the shell to do so in potentially unsafe manner.
-See https://trac.parrot.org/parrot/ticket/847.
+See https://github.com/parrot/parrot/issues/362
+(formerly https://trac.parrot.org/parrot/ticket/847).
TT #848: C<spawnw()> should return something less system-dependent, and more
-object-like. See https://trac.parrot.org/parrot/ticket/848.
+object-like. See https://github.com/parrot/parrot/issues/369.
=cut
View
2  src/string/api.c
@@ -2079,7 +2079,7 @@ Parrot_str_to_num(PARROT_INTERP, ARGIN_NULLOK(const STRING *s))
/* powl() could be used here, but it is an optional POSIX extension that
needs to be checked for at Configure-time.
- See https://trac.parrot.org/parrot/ticket/1176 for more details. */
+ See https://github.com/parrot/parrot/issues/451 for more details. */
# define POW pow
View
2  t/pmc/exporter.t
@@ -463,7 +463,7 @@ ok 1
OUT
# Test exporting mmd subs: TT #1205
-# https://trac.parrot.org/parrot/ticket/1205
+# https://github.com/parrot/parrot/issues/542
# Local Variables:
# mode: cperl
View
2  t/tools/install/testlib/README
@@ -134,7 +134,7 @@ WEB SITES
The following web sites have all the information you need about Parrot:
http://www.parrot.org/
- http://trac.parrot.org/
+ http://github.com/parrot/parrot/
http://www.parrotblog.org/
And Perl6:
Please sign in to comment.
Something went wrong with that request. Please try again.