X-Git-Url: https://git.donarmstrong.com/?p=lilypond.git;a=blobdiff_plain;f=Documentation%2Fcontributor%2Fissues.itexi;h=434ead511a139e1181b417f0cfb7997e4da18ae6;hp=782d84d155056ec20e54c2a3e5dacec5fb53587f;hb=f938685c1aa5af0316d762068577460c8fc663e6;hpb=708aa920d682cf9aa3ed647cd129afd8509760f4 diff --git a/Documentation/contributor/issues.itexi b/Documentation/contributor/issues.itexi index 782d84d155..434ead511a 100644 --- a/Documentation/contributor/issues.itexi +++ b/Documentation/contributor/issues.itexi @@ -69,93 +69,80 @@ If you would like to be part of the Bug Squad, please contact the @node Bug Squad setup @subsection Bug Squad setup -We highly recommend that you configure your email to use effective -sorting; this can reduce your workload @emph{immensely}. The -email folders names were chosen specifically to make them work if -you sort your folders alphabetically. +We highly recommend that you configure your email client to use some +kind of sorting and filtering as this will significantly reduce and +simplify your workload. Suggested email folder names are mentioned +below to work when sorted alphabetically. @enumerate @item -Read every section of this chapter, @ref{Issues}. +Read every section of the @ref{Issues} chapter in this guide. @item -If you do not have one already, create a gmail account and send -the email address to the @ref{Meisters, Bug Meister}. +Subscribe your email account to @code{bug-lilypond}. See +@uref{https://lists.gnu.org/mailman/listinfo/bug-lilypond}. @item -Subscribe your gmail account to @code{bug-lilypond}. +Send your email address to the @ref{Meisters, Bug Meister}. @item -Configure your google code account: +Create your own Sourceforge login (required for the Allura issue +tracker): -@enumerate +@itemize @item -Wait until your gmail account is listed in: - -@example -@uref{http://code.google.com/p/lilypond/people/list} -@end example +Go to @uref{https://sourceforge.net/p/testlilyissues/issues/} @item -Sign in to google code by clicking in the top-right corner of: - -@example -@uref{http://code.google.com/p/lilypond/issues/list} -@end example - -You cannot log on if you have Google Sharing enabled -@uref{http://www.googlesharing.net/}. +Click on 'Join' in the top-right corner. @item -Go to your @qq{Profile}, and select @qq{Settings}. +Fill in your details as required and click the @emph{Register} button to +complete the registration. -@item -Scroll down to @qq{Issue change notification}, and make sure that -you have @emph{selected} @qq{If I starred the issue}. +@end itemize -@end enumerate +@item +Send your Sourceforge @emph{username} (not your email address) to +@email{bug-lilypond@@gnu.org} asking to be given appropriate permissions +to either create, edit and comment on tracker issues. @item Configure your email client: -@enumerate +@itemize @item -Any email sent with your gmail address in the @code{To:} or -@code{CC:} fields should go to a @code{bug-answers} folder. - -When setting up your filtering rules, be aware that Google Code -might use different versions of your email address, such as ones -ending in @code{@@googlemail.com} or @code{@@gmail.com}. +Any email sent with your address in the @code{To:} or @code{CC:} fields +should be configured to go into a @code{bug-answers} folder. @item -Any other email either from, or CC'd to, +Any email either @code{From:} or @code{CC:} to, @example -lilypond@@googlecode.com +testlilyissues-auto@@lists.sourceforge.net @end example @noindent -should go into a separate @code{bug-ignore} folder. Alternately, -you may automatically delete these emails. - -You will @strong{not read} these emails as part of your Bug Squad -duties. If you are curious, go ahead and read them later, but it -does @strong{not} count as Bug Squad work. +should be configured to go into a @code{bug-ignore} folder or, +alternately, configure your email client to delete these automatically. +You do @emph{not} need to read mails in the @code{bug-ignore} folder. +If you are curious (and have time) then read them, but they are not +necessary for Bug Squad work. @item -Any other email sent to (or CC'd to): +Any email sent @code{To:} or @code{CC:} to, @example bug-lilypond @end example @noindent -should go into a separate @code{bug-current} folder. +should be configured to go into a @code{bug-current} folder. -@end enumerate +@end itemize @end enumerate @@ -187,7 +174,7 @@ Monday: Federico Bruni Tuesday: Simon Albrecht Wednesday: Simon Albrecht Thursday: Colin Campbell -Friday: +Friday: Ralph Palmer Saturday: Colin Campbell Sunday: @end example @@ -341,21 +328,26 @@ After @strong{every release} (both stable and unstable): @item Issues to verify: go to -@example -@uref{http://code.google.com/p/lilypond/issues/list?can=7} -@end example +@smallexample +@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AFixed} +@end smallexample -(You can also generate this list by selecting -@qq{Issues to verify} from the drop-down list next to the search -box.) +(You can also generate this list by selecting the @qq{Open (Fixed)} +button down the left-hand frame) -You should see a list of Issues that have been claimed fixed by a +You should see a list of Issues that have been marked as 'Fixed' by a developer. If the developer has done their job properly, the -Issue should have a tag @qq{Fixed_mm_MM_ss}, where mm is -the major version, MM the minor version and ss the current -release. This will help you work out which you can verify - do -not verify any Issues where the claimed fixed build is not yet -released. Work your way through these as follows: +Issue should have the @qq{Labels} field filled in with @qq{Fixed_x_y_z}, +where X is the major version, y the minor version and z the current +release. + +@example +Fixed_2_19_39 +@end example + +This will help you work out which you can verify - do not verify any +Issues where the claimed fixed build is not yet released. Work your +way through these as follows: If the Issue refers to a bug, try to reproduce the bug with the latest officially released version (not one you've built yourself from @@ -839,10 +831,10 @@ available to do this task if required). @subsubheading Project overview -Grid view provides the best overview: +Project activity @smallexample -@uref{http://code.google.com/p/lilypond/issues/list?mode=grid&y=Priority&x=Type&cells=ids} +@uref{https://sourceforge.net/projects/testlilyissues/} @end smallexample @subsubheading Hindering development @@ -850,28 +842,61 @@ Grid view provides the best overview: These issues stop or slow development work: @smallexample -@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:Maintainability} +@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status:Accepted%20AND%20_type:Maintainability} @end smallexample @subsubheading Easy tasks Issues tagged with @code{Frog} indicates a task suitable for a -relatively new contributor. The time given is a quick -(inaccurate) estimate of the time required for somebody who is -familiar with material in this manual, but does not know anything -else about LilyPond development. +relatively new contributor. The time given is a quick (and probably +inaccurate) estimate of the time required for somebody who is familiar +with material in this manual, but does not know anything else about +LilyPond development. @smallexample -@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:Frog} +@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status:Accepted%20AND%20labels:Frog} @end smallexample -@subsubheading Patches to review +@subsubheading Patches currently in the Patch Review cycle + +Overview -Patches which have no @qq{obvious} problems: +@c The following URL is provided by one of the Developers giving a much +@c easier way to see all patches at all stages of the Review cycle in a +@c single place. @example -@uref{http://code.google.com/p/lilypond/issues/list?can=2&q=label:patch-review} +http://philholmes.net/lilypond/allura/ @end example +@noindent +New patches +@smallexample +@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+_patch%3Anew} +@end smallexample + + +@noindent +Patches under Review + +@smallexample +@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+_patch%3Areview} +@end smallexample + + +@noindent +Patches on final Countdown + +@smallexample +@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+_patch%3Acountdown} +@end smallexample + + +@noindent +Patches that can be pushed + +@smallexample +@uref{https://sourceforge.net/p/testlilyissues/issues/search/?q=status%3AStarted+AND+_patch%3Apush} +@end smallexample