Geert mentioned in the Notification Emails thread that he'd like to get 2.6
released in less than a year, and Christian was pushing to do so this time
*last* year. On the principle that "Release is a misnomer. Software is never
released, it escapes." [1], it's probably time to release 2.5.0 so t
On Feb 7, 2013, at 8:42 AM, Geert Janssens wrote:
> On 07-02-13 16:42, John Ralls wrote:
>> Do we want to be sending commit-mail from gitolite while we're still
>> committing to svn? ISTM that's something to turn on after we drop svn. Not
>> that you shouldn't have done the work, of course. It
Geert Janssens writes:
> 3. Even though it may take some time before we're fully in git, we can
> already start sending mails from git and disable sending mails from
> svn earlier. It's one less dependency on svn that way. As said, I will
> first need to find a solution for the AUDIT feature befo
Geert Janssens writes:
>>> Of note still is that the mail is sent by GIT SVN Migration user
>>> (git-svn). This is because the mail generation is triggered by the
>>> the svn-git push, which is currently always performed by the user
>>> account git-svn. With the scripts as they are now, the sendi
On 07-02-13 16:42, John Ralls wrote:
Do we want to be sending commit-mail from gitolite while we're still committing
to svn? ISTM that's something to turn on after we drop svn. Not that you
shouldn't have done the work, of course. It's good to have everything ready,
even if it's another year b
One would think so, but the search for open bugs does not show resolved bugs
that are not closed.
David C
--- On Thu, 2/7/13, Colin Law wrote:
From: Colin Law
Subject: Re: Fw: Re: Proposed change to development Process was Fw: [Bug
650598] Cannot Enter Nth Day of Month Scheduled Transactions
On 7 February 2013 15:41, David Carlson wrote:
> Then is there some other way to show the bug unresolved (because it has not
> been released) but the code is in the queue?
Could one use a Status of Resolved to mean that the fix has been
committed but not yet released, and then close the bug when
After looking at the status choices, how about creating a bogus person named
something like "BugReleaseAgent" to assign the bug report to when the code is
written, then leaving it in his hands until it reaches the actual program
release?
Just a suggestion.
--- On Thu, 2/7/13, David Carlson wr
On Feb 7, 2013, at 7:25 AM, Geert Janssens wrote:
> On 07-02-13 16:00, John Ralls wrote:
>> On Feb 7, 2013, at 3:19 AM, Geert Janssens wrote:
>>
>>> On 07-02-13 02:37, John Ralls wrote:
You could use "short" commit numbers both for the subject line and the
URLs e.g.,
https://gi
Then is there some other way to show the bug unresolved (because it has not
been released) but the code is in the queue?
David C
--- On Thu, 2/7/13, John Ralls wrote:
From: John Ralls
Subject: Re: Proposed change to development Process was Fw: [Bug 650598] Cannot
Enter Nth Day of Month Sched
On Feb 7, 2013, at 7:21 AM, David Carlson wrote:
> As I requested in this closed bug, which is not in the current program
> release and may not be in the current release for many more months, how about
> adding a status "Awaiting next Program Release" so the bug can be found in a
> search for
On 07-02-13 16:00, John Ralls wrote:
On Feb 7, 2013, at 3:19 AM, Geert Janssens wrote:
On 07-02-13 02:37, John Ralls wrote:
You could use "short" commit numbers both for the subject line and the URLs
e.g.,
https://github.com/Gnucash/gnucash-docs/commit/8686314
works just fine, which will mak
As I requested in this closed bug, which is not in the current program release
and may not be in the current release for many more months, how about adding a
status "Awaiting next Program Release" so the bug can be found in a search for
unresolved bugs?
This should reduce duplicate bug report
On Feb 7, 2013, at 3:19 AM, Geert Janssens wrote:
> On 07-02-13 02:37, John Ralls wrote:
>> You could use "short" commit numbers both for the subject line and the URLs
>> e.g.,
>> https://github.com/Gnucash/gnucash-docs/commit/8686314
>> works just fine, which will make it a bit more readable.
On 07-02-13 02:37, John Ralls wrote:
You could use "short" commit numbers both for the subject line and the URLs
e.g.,
https://github.com/Gnucash/gnucash-docs/commit/8686314
works just fine, which will make it a bit more readable.
The preamble is way too long. The subject line says what the mai
15 matches
Mail list logo
