Hi,
I see, the other work flows are pretty much easier for sane than git flow.
Am 20.05.2017 um 03:45 schrieb Olaf Meeuwissen:
> Hi,
>
> Rolf Bensch writes:
>
>> Hi,
>>
>>
>> Am 19.05.2017 um 15:02 schrieb Olaf Meeuwissen:
>>> Hi All(an),
>>>
>>> m. allan noah writes:
>>>
What is the natur
Hi,
Rolf Bensch writes:
> Hi,
>
>
> Am 19.05.2017 um 15:02 schrieb Olaf Meeuwissen:
>> Hi All(an),
>>
>> m. allan noah writes:
>>
>>> What is the nature of the bug fix? Is it going to cause scanners that
>>> worked with the prior release to be broken with this one? How big is
>>> the fix? How lik
Hi,
Am 19.05.2017 um 15:02 schrieb Olaf Meeuwissen:
> Hi All(an),
>
> m. allan noah writes:
>
>> What is the nature of the bug fix? Is it going to cause scanners that
>> worked with the prior release to be broken with this one? How big is
>> the fix? How likely to cause regressions?
>
> Here's
Hi All(an),
m. allan noah writes:
> What is the nature of the bug fix? Is it going to cause scanners that
> worked with the prior release to be broken with this one? How big is
> the fix? How likely to cause regressions?
Here's where git branches come in nice. Rolf creates a branch, commits
his
What is the nature of the bug fix? Is it going to cause scanners that
worked with the prior release to be broken with this one? How big is
the fix? How likely to cause regressions?
allan
On Fri, May 19, 2017 at 5:13 AM, Rolf Bensch wrote:
> Are we already in Code Freeze?
>
> I would like to comm
Hi Rolf,
Rolf Bensch writes:
> Are we already in Code Freeze?
Allan wrote:
>> May 14: Code freeze (only update docs after this date)
and since there has been nothing on the mailing list to the contrary,
I'd say, yes, we are in Code Freeze. For a good five days already.
> I would like to comm
Are we already in Code Freeze?
I would like to commit a bug fix this weekend.
Rolf
Am 28.04.2017 um 14:04 schrieb m. allan noah:
> Ok folks, it's time to get another sane-backends release out the door.
>
> Olaf has done a good job of cleaning up our contributors list and
> curating the bug trac
On Sun, 2017-05-07 at 07:34 +0900, Olaf Meeuwissen wrote:
> Hi all,
>
> Louis Lagendijk writes:
>
> > On Sat, 2017-05-06 at 15:55 +0200, Wilhelm wrote:
> > > Am 06.05.2017 um 14:27 schrieb m. allan noah:
> > > > On Sat, May 6, 2017 at 5:52 AM, Louis Lagendijk > > > et>
> > > > wrote:
> > > > >
Hi all,
Louis Lagendijk writes:
> On Sat, 2017-05-06 at 15:55 +0200, Wilhelm wrote:
>> Am 06.05.2017 um 14:27 schrieb m. allan noah:
>> > On Sat, May 6, 2017 at 5:52 AM, Louis Lagendijk
>> > wrote:
>> > >
>> > > Hi,
>> > > Yesterday when I had a look at our bug tracker for any issues in
>> > > m
Hmm, I think we should not rush this change. We can do another sane
release once we have something we all agree on, and have spent more
time testing.
allan
On Sat, May 6, 2017 at 2:13 PM, Louis Lagendijk wrote:
> On Sat, 2017-05-06 at 15:55 +0200, Wilhelm wrote:
>> Am 06.05.2017 um 14:27 schrieb
On Sat, 2017-05-06 at 15:55 +0200, Wilhelm wrote:
> Am 06.05.2017 um 14:27 schrieb m. allan noah:
> > On Sat, May 6, 2017 at 5:52 AM, Louis Lagendijk
> > wrote:
> > > On Fri, 2017-04-28 at 08:04 -0400, m. allan noah wrote:
> > > > Ok folks, it's time to get another sane-backends release out
> > >
Am 06.05.2017 um 14:27 schrieb m. allan noah:
> On Sat, May 6, 2017 at 5:52 AM, Louis Lagendijk wrote:
>> On Fri, 2017-04-28 at 08:04 -0400, m. allan noah wrote:
>>> Ok folks, it's time to get another sane-backends release out the
>>> door.
>>>
>>> Olaf has done a good job of cleaning up our contr
On Sat, May 6, 2017 at 5:52 AM, Louis Lagendijk wrote:
> On Fri, 2017-04-28 at 08:04 -0400, m. allan noah wrote:
>> Ok folks, it's time to get another sane-backends release out the
>> door.
>>
>> Olaf has done a good job of cleaning up our contributors list and
>> curating the bug tracker. However
On Fri, 2017-04-28 at 08:04 -0400, m. allan noah wrote:
> Ok folks, it's time to get another sane-backends release out the
> door.
>
> Olaf has done a good job of cleaning up our contributors list and
> curating the bug tracker. However, there are a handful of patches in
> the bug tracker that cou
Hi Olaf,
I tried to build a recent version for zesty some weeks ago with my test
ppa: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test/+packages .
I'll try to investigate this issue next week. If you can provide a patch
before, I can merge it into the build system very quickly.
Hope t
Hi again,
Olaf Meeuwissen writes:
> Hi Allan,
>
> m. allan noah writes:
>
>> Ok folks, it's time to get another sane-backends release out the door.
>
> [snip]
>> However, there are a handful of patches in
>> the bug tracker that could still be applied, once they are reviewed.
>
> I'm working thro
Hi Allan,
m. allan noah writes:
> Ok folks, it's time to get another sane-backends release out the door.
I was about to ping you on that ;-)
> Olaf has done a good job of cleaning up our contributors list and
> curating the bug tracker.
I don't think I did a good job (yet?) with the bug tracke
You can send translations at any time, up to the day of the release.
allan
On Fri, Apr 28, 2017 at 10:20 AM, Yuri Chornoivan wrote:
> п'ятниця, 28-кві-2017 08:04:55 m. allan noah написано:
>> Ok folks, it's time to get another sane-backends release out the door.
>>
>> Olaf has done a good job of
п'ятниця, 28-кві-2017 08:04:55 m. allan noah написано:
> Ok folks, it's time to get another sane-backends release out the door.
>
> Olaf has done a good job of cleaning up our contributors list and
> curating the bug tracker. However, there are a handful of patches in
> the bug tracker that could
19 matches
Mail list logo
