You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@serf.apache.org by Bert Huijben <be...@qqmail.nl> on 2015/09/01 11:42:13 UTC

Short term release policy?

	Hi,

I received a number of very good questions this morning:
* Are we creating an announce@serf.apache.org mailinglist to announce serf
releases?

* Do we want to create future 1.3.x serf releases?
* If yes, do we want to change the license on 1.3.x?


* What is the status of the 1.4.0 release?
- [Subversion checks for >= 1.4 to enable logging]
- The function pointer inequality problem is not solved by just dropping one
function (remaining support), but not the other (config support).

- Would the release process be easier if we just go 2.0 and introduce a
proper versioning scheme?

Given that the current 1.4.x problem may already break existing linkage
scenarios...


	Bert


Re: Short term release policy?

Posted by Ivan Zhakov <iv...@visualsvn.com>.
On 8 September 2015 at 16:08, Bert Huijben <be...@qqmail.nl> wrote:
>> -----Original Message-----
>> From: Ivan Zhakov [mailto:ivan@visualsvn.com]
>> Sent: dinsdag 8 september 2015 14:50
>> To: Lieven Govaerts <lg...@mobsol.be>
>> Cc: Bert Huijben <be...@qqmail.nl>; dev@serf.apache.org
>> Subject: Re: Short term release policy?
>>
>> On 1 September 2015 at 22:04, Lieven Govaerts <lg...@mobsol.be> wrote:
>> > On Tue, Sep 1, 2015 at 11:42 AM, Bert Huijben <be...@qqmail.nl> wrote:
>> >>         Hi,
>> >>
>> >> I received a number of very good questions this morning:
>> >> * Are we creating an announce@serf.apache.org mailinglist to announce
>> serf
>> >> releases?
>> >>
>> >> * Do we want to create future 1.3.x serf releases?
>> >> * If yes, do we want to change the license on 1.3.x?
>> >
>> > Why would we? Can't we focus on 1.4.0 instead?
>> One reason could be to complete ASF transition and make ASF release
>> with minimal changes, then focus on 1.4.0 (or 1.5.0) release.
>>
>> My favorite option to release serf 1.4.0 by copying 1.3.x branch and
>> merging license changes commits.
>
> That by itself won't work for Subversion 1.9.
>
> Subversion expects that it can enable logging for >= 1.4.0... So at the very least we should add a dummy handler for that.
>
Oops, I forgot that Subversion 1.9 relies on unreleased feature.

> But if we do that, then I would also like to see the support for a few new error codes to help diagnosing ssl problems.
> ...
>
> Just releasing a 1.3.9 with the license change would work for me.
>
OK, releasing 1.3.9 with the license change also would work for me.

-- 
Ivan Zhakov

RE: Short term release policy?

Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Ivan Zhakov [mailto:ivan@visualsvn.com]
> Sent: dinsdag 8 september 2015 14:50
> To: Lieven Govaerts <lg...@mobsol.be>
> Cc: Bert Huijben <be...@qqmail.nl>; dev@serf.apache.org
> Subject: Re: Short term release policy?
> 
> On 1 September 2015 at 22:04, Lieven Govaerts <lg...@mobsol.be> wrote:
> > On Tue, Sep 1, 2015 at 11:42 AM, Bert Huijben <be...@qqmail.nl> wrote:
> >>         Hi,
> >>
> >> I received a number of very good questions this morning:
> >> * Are we creating an announce@serf.apache.org mailinglist to announce
> serf
> >> releases?
> >>
> >> * Do we want to create future 1.3.x serf releases?
> >> * If yes, do we want to change the license on 1.3.x?
> >
> > Why would we? Can't we focus on 1.4.0 instead?
> One reason could be to complete ASF transition and make ASF release
> with minimal changes, then focus on 1.4.0 (or 1.5.0) release.
> 
> My favorite option to release serf 1.4.0 by copying 1.3.x branch and
> merging license changes commits.

That by itself won't work for Subversion 1.9.

Subversion expects that it can enable logging for >= 1.4.0... So at the very least we should add a dummy handler for that.

But if we do that, then I would also like to see the support for a few new error codes to help diagnosing ssl problems.
...

Just releasing a 1.3.9 with the license change would work for me.

	Bert


Re: Short term release policy?

Posted by Ivan Zhakov <iv...@visualsvn.com>.
On 1 September 2015 at 22:04, Lieven Govaerts <lg...@mobsol.be> wrote:
> On Tue, Sep 1, 2015 at 11:42 AM, Bert Huijben <be...@qqmail.nl> wrote:
>>         Hi,
>>
>> I received a number of very good questions this morning:
>> * Are we creating an announce@serf.apache.org mailinglist to announce serf
>> releases?
>>
>> * Do we want to create future 1.3.x serf releases?
>> * If yes, do we want to change the license on 1.3.x?
>
> Why would we? Can't we focus on 1.4.0 instead?
One reason could be to complete ASF transition and make ASF release
with minimal changes, then focus on 1.4.0 (or 1.5.0) release.

My favorite option to release serf 1.4.0 by copying 1.3.x branch and
merging license changes commits.

-- 
Ivan Zhakov

Re: Short term release policy?

Posted by Lieven Govaerts <lg...@mobsol.be>.
On Tue, Sep 1, 2015 at 11:42 AM, Bert Huijben <be...@qqmail.nl> wrote:
>         Hi,
>
> I received a number of very good questions this morning:
> * Are we creating an announce@serf.apache.org mailinglist to announce serf
> releases?
>
> * Do we want to create future 1.3.x serf releases?
> * If yes, do we want to change the license on 1.3.x?

Why would we? Can't we focus on 1.4.0 instead?
Lieven

>
> * What is the status of the 1.4.0 release?
> - [Subversion checks for >= 1.4 to enable logging]
> - The function pointer inequality problem is not solved by just dropping one
> function (remaining support), but not the other (config support).
>
> - Would the release process be easier if we just go 2.0 and introduce a
> proper versioning scheme?
>
> Given that the current 1.4.x problem may already break existing linkage
> scenarios...
>
>
>         Bert
>

RE: Short term release policy?

Posted by Bert Huijben <be...@qqmail.nl>.

> -----Original Message-----
> From: justin.erenkrantz@gmail.com [mailto:justin.erenkrantz@gmail.com] On
> Behalf Of Justin Erenkrantz
> Sent: woensdag 2 september 2015 12:34
> To: Ivan Zhakov <iv...@visualsvn.com>
> Cc: Bert Huijben <be...@qqmail.nl>; dev@serf.apache.org
> Subject: Re: Short term release policy?


> For Subversion, I thought that we didn't touch the license blocks for
> the pre-ASF releases though we did a couple of patch releases after
> the migration.  I know I wasn't the only one around at that time on
> this list (*grin*) - anyone remember the specifics?  I'd really prefer
> not to have a big delta on a patch release if at all possible.  --
> justin

I think we officially maintained Subversion 1.6 outside the ASF to avoid code churn, but I'm not entirely sure.

But for Subversion we had a strict relicense, while for serf the licensing was always Apache v2 with CLAs on file.

	Bert


Re: Short term release policy?

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On Tue, Sep 1, 2015 at 9:03 AM, Ivan Zhakov <iv...@visualsvn.com> wrote:
> I think it's a good idea. I also suggest to reconsider decision about
> using dev@s.a.o for commit and JIRA notifications -- it's hard to
> filter them and important dev@ discussions could be missed with
> current approach.

*shrug*

Let's give it some time to settle down and see how much traffic it really is.

>> * Do we want to create future 1.3.x serf releases?
> I think it's good idea and I'm volunteering to backport necessary
> changes if nobody objects.
>
>> * If yes, do we want to change the license on 1.3.x?
>>
> I think we should, otherwise we need some special statements on
> Download page that this is not ASF release.

For Subversion, I thought that we didn't touch the license blocks for
the pre-ASF releases though we did a couple of patch releases after
the migration.  I know I wasn't the only one around at that time on
this list (*grin*) - anyone remember the specifics?  I'd really prefer
not to have a big delta on a patch release if at all possible.  --
justin

Re: Short term release policy?

Posted by Ivan Zhakov <iv...@visualsvn.com>.
On 1 September 2015 at 12:42, Bert Huijben <be...@qqmail.nl> wrote:
>         Hi,
>
> I received a number of very good questions this morning:
> * Are we creating an announce@serf.apache.org mailinglist to announce serf
> releases?
>
I think it's a good idea. I also suggest to reconsider decision about
using dev@s.a.o for commit and JIRA notifications -- it's hard to
filter them and important dev@ discussions could be missed with
current approach.

> * Do we want to create future 1.3.x serf releases?
I think it's good idea and I'm volunteering to backport necessary
changes if nobody objects.

> * If yes, do we want to change the license on 1.3.x?
>
I think we should, otherwise we need some special statements on
Download page that this is not ASF release.

-- 
Ivan Zhakov