On May 31, 2013, at 12:07 PM, Geert Janssens wrote:
> On Saturday 18 May 2013 09:39:26 John Ralls wrote:
> > What ids do we want? I suggest:
> >
> > core (engine, backends, budgets, build, python, SX, general)
> > import (also export)
> > UI (register, general UI)
> > business
> > reports (incl
On May 31, 2013, at 11:51 AM, Geert Janssens wrote:
> On Friday 31 May 2013 06:52:49 John Ralls wrote:
> > On May 31, 2013, at 1:19 AM, Geert Janssens
> > wrote:
> > > I'll do it.
> > >
> > > What do I do with the current default assignees ? Just delete them
> > > or move them to the default
Geert Janssens writes:
> I decided to do a a little poll regarding these two lists, to
> determine how to handle them in the (git-only) future:
>
> 1. Which lists are you subscribed to ?
> a. gnucash-changes
> b. gnucash-patches
> c. both
> d. none
c (both)
> 2. If you're only subscribe
Geert Janssens writes:
>> I guess what I found odd were the links to github versus having links to
>> code.
>
> This is a deliberate choice, but may need some background to understand:
>
> The svn notification mails all have a reference that links back to the commit
> on our trac website. That is
On Saturday 18 May 2013 09:39:26 John Ralls wrote:
> What ids do we want? I suggest:
>
> core (engine, backends, budgets, build, python, SX, general)
> import (also export)
> UI (register, general UI)
> business
> reports (includes check printing)
> mac
> win
> documentation (includes translation
On May 31, 2013, at 4:52 AM, Geert Janssens wrote:
>
> 1. Which lists are you subscribed to ?
> a. gnucash-changes
> b. gnucash-patches
> c. both
> d. none
gnucash-patches only
> 2. If you're only subscribed to one, why that one ?
If I want to look at the details of the change it's easy en
On Friday 31 May 2013 06:52:49 John Ralls wrote:
> On May 31, 2013, at 1:19 AM, Geert Janssens wrote:
> > I'll do it.
> >
> > What do I do with the current default assignees ? Just delete them
> > or move them to the default qa contact or default cc list ?
> I'd move both default contact and defa
We have slightly changed the way we use bugzilla.
There are two fields in each bug: "Assigned to" and "QA Contact". These fields
take bugzilla
accounts that will automatically receive e-mails for every change to that bug.
The disadvantage of the way we used them so far was that only two e-mail
On May 31, 2013, at 1:52 AM, Geert Janssens wrote:
> My work on the transition to git accidentally brought up a small issue
> regarding the two
> mailing lists we have the record changes in the repositories: gnucash-changes
> and gnucash-
> patches.
>
> gnucash-changes publishes all commits
On May 31, 2013, at 1:19 AM, Geert Janssens wrote:
> I'll do it.
>
> What do I do with the current default assignees ? Just delete them or move
> them to the default qa contact or default cc list ?
>
I'd move both default contact and default qa to default cc, but it looks like
you already
Am 31.05.2013 10:52, schrieb Geert Janssens:
> I decided to do a a little poll regarding these two lists, to determine how
> to handle them in
> the (git-only) future:
>
> 1. Which lists are you subscribed to ?
> a. gnucash-changes
> b. gnucash-patches
> c. both
> d. none
Only gnucash-p
My work on the transition to git accidentally brought up a small issue
regarding the two
mailing lists we have the record changes in the repositories: gnucash-changes
and gnucash-
patches.
gnucash-changes publishes all commits with full details (diff of all files that
got changed)
gnucash-patc
On Thursday 30 May 2013 11:26:59 Derek Atkins wrote:
> Geert Janssens writes:
> >> I was wondering why there were all these links to github (see below)!
> >> That just looked very odd to me.
> >
> > This is certainly different from wat we got with the svn notification
> > script. But what exactly
I'll do it.
What do I do with the current default assignees ? Just delete them or move them
to
the default qa contact or default cc list ?
Geert
On Thursday 30 May 2013 20:01:12 John Ralls wrote:
> I'll be traveling tomorrow, so if anyone would like to set this up, go for
> it. Otherwise I'll
I will admit that it's not always clear when your topic differs sufficiently
from the original one
to warrant a new thread.
One clue can be: does the current thread subject match what you want to say ?
The original subject in this case was
"Comments Regarding New 2.5.1 Register"
Your message wa
15 matches
Mail list logo
