Mailing List Archive

release plans?
Hi,

I am new to conserver, but I got it working for my use case without
too much fuss. I think it is very nice!

However, as soon as I tried to use the tasks functionality, I
encountered the issue which this patch fixes:

https://www.conserver.com/pipermail/users/2014-September/msg00003.html

I have verified that this fixes the issue for me, and I have opened a
bug with my distribution (Fedora) to have the fix included in their
conserver package:

https://bugzilla.redhat.com/show_bug.cgi?id=1225592

Are there plans to make a maintenance/stable release with this fix included?
_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users
Re: release plans? [ In reply to ]
> Are there plans to make a maintenance/stable release with this fix included?

There were plans, but then I spaced out and haven’t just gone through the appropriate motions. Thanks for mentioning it, though.

I’ll work on getting this and anything else that got queued up out soon - by the end of the week at the latest. It’s been ignored way too long.

Bryan


_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users
Re: release plans? [ In reply to ]
On Wed, May 27, 2015 at 4:43 PM, Bryan Stansell <bryan@conserver.com> wrote:
>
>> Are there plans to make a maintenance/stable release with this fix included?
>
> There were plans, but then I spaced out and haven’t just gone through the appropriate motions. Thanks for mentioning it, though.
>
> I’ll work on getting this and anything else that got queued up out soon - by the end of the week at the latest. It’s been ignored way too long.

Great, thanks!

_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users
Re: release plans? [ In reply to ]
Hello Bryan,

On Wed, May 27, 2015 at 02:43:33PM -0700, Bryan Stansell wrote:
> > Are there plans to make a maintenance/stable release with this fix included?
> There were plans, but then I spaced out and haven’t just gone through the appropriate motions. Thanks for mentioning it, though.
> I’ll work on getting this and anything else that got queued up out soon - by the end of the week at the latest. It’s been ignored way too long.
Are there plans to include the breaksequence patch ([1])?
I also have another one that adds CONSERVER_USERNAME and
CONSERVER_PEERNAME variables to task's environment. It's a simple patch,
but I don't think it went through proper testing just yet.
Would that be something that can be merged as well?

1. https://www.conserver.com/pipermail/users/2015-March/msg00000.html

--
Regards,
Artem
_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users
Re: release plans? [ In reply to ]
Yep, going through all the reports/patches/posts since the last release is part of the plan. The break list patch will be included.

If you have the username/peername "stable", send it along, otherwise we can try and work it in when you're comfortable with it. Is the peername the result of getpeername(), or more a remote username like from SO_PEERCRED? I just ask because the latter is less portable.

Thanks.

Bryan

> On May 29, 2015, at 12:25 AM, Artem Savkov <asavkov@redhat.com> wrote:
>
> Are there plans to include the breaksequence patch ([1])?
> I also have another one that adds CONSERVER_USERNAME and
> CONSERVER_PEERNAME variables to task's environment. It's a simple patch,
> but I don't think it went through proper testing just yet.
> Would that be something that can be merged as well?
>
> 1. https://www.conserver.com/pipermail/users/2015-March/msg00000.html
>
> --
> Regards,
> Artem
>

_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users