Requirements for bugsquad team for alternatives to Bugzilla/cgit
Carlos Soriano <[email protected]> Wed, 3 May 2017 19:12:17 +0200
| Newsgroups | gmane.comp.gnome.bugsquad |
|---|---|
| Message-ID | <CAPoe4L4Sp+_Sr79RmC6_EqEZDsskVt3WTiR+JOrh_DBUXaqbVA@mail.gmail.com> |
--===============0972528024947339559== Content-Type: multipart/alternative; boundary=001a114ac08862620f054ea1c35d --001a114ac08862620f054ea1c35d Content-Type: text/plain; charset=UTF-8 Hello Bugsquad team, I'm trying to writte down the requirements of the bugsquad team regarding git repository and issue tracker, in the context on evaluating possible alternatives to cgit and Bugzilla. Could someone help on this and write down what are the requirements and workflow the bugsquad need to have? You can write it here https://wiki.gnome.org/Sysadmin/CodeHostingComparisonMatrix/Bugsquad We are focusing on your current needs and not regress on those, but you can add a section that is "nice to have" and we will take that into account too. You can write it in prosa, an example would be "In an upcoming release, we need to make sure blockers are seen by maintainers. For that, we mark a milestone for those bug reports, and we search across projects for those blockers. Then we update the bug report to "ping" the maintainer" It will be very appreciated if we can have something for this week if possible. Thanks! Carlos Soriano --001a114ac08862620f054ea1c35d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hello Bugsquad team,<br><br>I'm trying to writte down = the requirements of the bugsquad team regarding git repository and issue tr= acker, in the context on evaluating possible alternatives to cgit and Bugzi= lla. Could someone help on this and write down what are the requirements an= d workflow the bugsquad need to have?<div>You can write it here=C2=A0<a hre= f=3D"https://wiki.gnome.org/Sysadmin/CodeHostingComparisonMatrix/Bugsquad">= https://wiki.gnome.org/Sysadmin/CodeHostingComparisonMatrix/Bugsquad</a><br= ><div><br></div><div>We are focusing on your current needs and not regress = on those, but you can add a section that is "nice to have" and we= will take that into account too.</div><div><br></div><div>You can write it= in prosa, an example would be "In an upcoming release, we need to mak= e sure blockers are seen by maintainers. For that, we mark a milestone for = those bug reports, and we search across projects for those blockers. Then w= e update the bug report to "ping" the maintainer"</div><div>= <br></div><div>It will be very appreciated if we can have something for thi= s week if possible.</div><div><br></div><div>Thanks!</div><div>Carlos Soria= no</div></div></div> --001a114ac08862620f054ea1c35d-- --===============0972528024947339559== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ gnome-bugsquad mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-bugsquad --===============0972528024947339559==--