Phil Holmes wrote Monday, May 04, 2015 3:57 PM
> As promised, a starter list of requirements for the issue handling system,
> to allow us to check potential replacements to Google code.
>
> 14. Allow export of the issue database in CSV form
Actually GoogleCode (and Allura for that matter) ex
Valentin Villenave wrote Tuesday, May 05, 2015 7:01 AM
> Surely there must be something I’ve overlooked, because all these
> talks of setting up a new system on Savannah must have a valid reason;
> having been using their bug tracker semi-regularly, I just can’t
> figure out what these reasons ma
On Mon, May 4, 2015 at 4:57 PM, Phil Holmes wrote:
> As promised, a starter list of requirements for the issue handling system,
> to allow us to check potential replacements to Google code.
Hi Phil, thanks for this recap.
This may well be a stupid question, and if so please forgive me, but:
many
Sorry if this raises old stuff again.
For me many of your requirwments could be rather easily (and partially
automatically ) be handled with an integrated system of code, review and
issues, i.e. a system that provides something like pull requests.
In addition to many of your list items this woul
As promised, a starter list of requirements for the issue handling system,
to allow us to check potential replacements to Google code.
1. Allow creation of a new sequentially numbered issue, with
text describing the issue’s title and details
2. Allow tagging the issue with a range of
