[NOTICE] Windows build machine setted up

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[NOTICE] Windows build machine setted up

Michal Hriň-3
Thanks for providing a binary, but I am a bit concerned that a version
is
made public, before the PMC have even spoken about being ready to make
a
release candidate or started voting on a release candidate.

Is this coordinated with the release manager for 4.1.2 ?

Please do not misunderstand me, I think it is great that work is being
done, I am just surprised we are ready to go public with 4.1.2 even as
a
pre-view.

<hrin>

OK. Binary is deleted.

This was not coordinated, that was only snapshot .. not release
candidate. All in all Linux 32bit builds from AOO410 branch are on
buildbots, so everybody can downlaod it, this is not secret.

Sorry, that I was excited and want to show it publically.


</hrin>



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Windows build machine setted up

Jürgen Schmidt-3
On 07/08/15 09:50, Michal Hriň wrote:

> Thanks for providing a binary, but I am a bit concerned that a version
> is
> made public, before the PMC have even spoken about being ready to make
> a
> release candidate or started voting on a release candidate.
>
> Is this coordinated with the release manager for 4.1.2 ?
>
> Please do not misunderstand me, I think it is great that work is being
> done, I am just surprised we are ready to go public with 4.1.2 even as
> a
> pre-view.
>
> <hrin>
>
> OK. Binary is deleted.
>
> This was not coordinated, that was only snapshot .. not release
> candidate. All in all Linux 32bit builds from AOO410 branch are on
> buildbots, so everybody can downlaod it, this is not secret.
>
> Sorry, that I was excited and want to show it publically.

no problem you did a good job and I don't see any problem, you did not
publish anything official and just provided a new fresh binary for
preview and testing if your build env is working as expected and can be
used for a Windows release build. Please continue your tests and keep us
informed. I'm would be happy if I don't have to prepare windows builds.

Juergen



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Windows build machine setted up

Rich Bowen


On 08/07/2015 04:00 AM, Jürgen Schmidt wrote:

> On 07/08/15 09:50, Michal Hriň wrote:
>> Thanks for providing a binary, but I am a bit concerned that a version
>> is
>> made public, before the PMC have even spoken about being ready to make
>> a
>> release candidate or started voting on a release candidate.
>>
>> Is this coordinated with the release manager for 4.1.2 ?
>>
>> Please do not misunderstand me, I think it is great that work is being
>> done, I am just surprised we are ready to go public with 4.1.2 even as
>> a
>> pre-view.
>>
>> <hrin>
>>
>> OK. Binary is deleted.
>>
>> This was not coordinated, that was only snapshot .. not release
>> candidate. All in all Linux 32bit builds from AOO410 branch are on
>> buildbots, so everybody can downlaod it, this is not secret.
>>
>> Sorry, that I was excited and want to show it publically.
>
> no problem you did a good job and I don't see any problem, you did not
> publish anything official and just provided a new fresh binary for
> preview and testing if your build env is working as expected and can be
> used for a Windows release build. Please continue your tests and keep us
> informed. I'm would be happy if I don't have to prepare windows builds.
>

I'm finding this conversation perplexing, and, no doubt, I lack some
back-story.

Surely it's wonderful that someone is producing binaries for folks to
try out, right? Why would we want them to be deleted, and not publicized?

Binaries are not (as has been discussed DOZENS of times) official
releases. And anyone is free to take our code and push out binaries.

Can someone explain to me what the problem is here? We should be
encouraging the work that Michal is doing, celebrating it, tweeting it,
and encouraging everyone and their grandmothers to try out this new build.

What am I missing?

--
Rich Bowen - [hidden email] - @rbowen
http://apachecon.com/ - @apachecon

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[NOTICE] Windows build machine setted up

jan i
On Friday, August 7, 2015, Rich Bowen <[hidden email]
<javascript:_e(%7B%7D,'cvml','[hidden email]');>> wrote:

>
>
> On 08/07/2015 04:00 AM, Jürgen Schmidt wrote:
>
>> On 07/08/15 09:50, Michal Hriň wrote:
>>
>>> Thanks for providing a binary, but I am a bit concerned that a version
>>> is
>>> made public, before the PMC have even spoken about being ready to make
>>> a
>>> release candidate or started voting on a release candidate.
>>>
>>> Is this coordinated with the release manager for 4.1.2 ?
>>>
>>> Please do not misunderstand me, I think it is great that work is being
>>> done, I am just surprised we are ready to go public with 4.1.2 even as
>>> a
>>> pre-view.
>>>
>>> <hrin>
>>>
>>> OK. Binary is deleted.
>>>
>>> This was not coordinated, that was only snapshot .. not release
>>> candidate. All in all Linux 32bit builds from AOO410 branch are on
>>> buildbots, so everybody can downlaod it, this is not secret.
>>>
>>> Sorry, that I was excited and want to show it publically.
>>>
>>
>> no problem you did a good job and I don't see any problem, you did not
>> publish anything official and just provided a new fresh binary for
>> preview and testing if your build env is working as expected and can be
>> used for a Windows release build. Please continue your tests and keep us
>> informed. I'm would be happy if I don't have to prepare windows builds.
>>
>>
> I'm finding this conversation perplexing, and, no doubt, I lack some
> back-story.
>
> Surely it's wonderful that someone is producing binaries for folks to try
> out, right? Why would we want them to be deleted, and not publicized?
>
> Binaries are not (as has been discussed DOZENS of times) official
> releases. And anyone is free to take our code and push out binaries.
>
> Can someone explain to me what the problem is here? We should be
> encouraging the work that Michal is doing, celebrating it, tweeting it, and
> encouraging everyone and their grandmothers to try out this new build.
>
> What am I missing?

Since I was the cause, let me explain what I tried to write,

I think the work done is very good, and wrote so, and I do not think
anybody asked for it to be deleted.

My concern was the naming 4.1.2 early preview. Thats sounds official (not
as an apache release, but you know that for AOO the binary is downloaded
factors more than the release source tar ball) and I do not want a
confusion to arise between what the release manager does and what
individual committers does.

I think Michael is doing a very important job with preparing builds for the
upcomming release, his work is known here, so much more reason to be
carefull when naming intermidiate builds. Andrea wrote it more direct, this
is a michael build based on the 4.1.0 branch, this is totally correct and
something a lot of people should test.

So I do not think you missed a lot, but as always it is real difficult to
write something without
getting misinterpreted or misunderstood.

rgds
jan i.


> --
> Rich Bowen - [hidden email] - @rbowen
> http://apachecon.com/ - @apachecon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Sent from My iPad, sorry for any misspellings.
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Windows build machine setted up

Marcus (OOo)
In reply to this post by Rich Bowen
Am 08/07/2015 05:22 PM, schrieb Rich Bowen:

>
>
> On 08/07/2015 04:00 AM, Jürgen Schmidt wrote:
>> On 07/08/15 09:50, Michal Hriň wrote:
>>> Thanks for providing a binary, but I am a bit concerned that a version
>>> is
>>> made public, before the PMC have even spoken about being ready to make
>>> a
>>> release candidate or started voting on a release candidate.
>>>
>>> Is this coordinated with the release manager for 4.1.2 ?
>>>
>>> Please do not misunderstand me, I think it is great that work is being
>>> done, I am just surprised we are ready to go public with 4.1.2 even as
>>> a
>>> pre-view.
>>>
>>> <hrin>
>>>
>>> OK. Binary is deleted.
>>>
>>> This was not coordinated, that was only snapshot .. not release
>>> candidate. All in all Linux 32bit builds from AOO410 branch are on
>>> buildbots, so everybody can downlaod it, this is not secret.
>>>
>>> Sorry, that I was excited and want to show it publically.
>>
>> no problem you did a good job and I don't see any problem, you did not
>> publish anything official and just provided a new fresh binary for
>> preview and testing if your build env is working as expected and can be
>> used for a Windows release build. Please continue your tests and keep us
>> informed. I'm would be happy if I don't have to prepare windows builds.
>>
>
> I'm finding this conversation perplexing, and, no doubt, I lack some
> back-story.
>
> Surely it's wonderful that someone is producing binaries for folks to
> try out, right? Why would we want them to be deleted, and not publicized?

absolutely

> Binaries are not (as has been discussed DOZENS of times) official
> releases. And anyone is free to take our code and push out binaries.

Of course, the official truth is in the source code - this applies also
for AOO. But please try to imagine that the AOO users think different.
Just a few percent are interested in the source code. But the very most
trust in the binaries as nearly no end-user is building from the source code

> Can someone explain to me what the problem is here? We should be
> encouraging the work that Michal is doing, celebrating it, tweeting it,
> and encouraging everyone and their grandmothers to try out this new build.
>
> What am I missing?

Maybe Jan was afraid that a new version could come into the public too
early, others can see it as new release - and then the problem is just
starting: we have to deny this, discussions here and there, and nobody
wants to have this mess.

However, all the problems can be easily solved with coordination and
communication (e.g., offering binaries only from Apache infra systems
like [hidden email], agreeing on file nameing to differentiate clearly from
release builds, etc.).

Marcus

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Windows build machine setted up

Rich Bowen
On Aug 7, 2015 12:04 PM, "Marcus" <[hidden email]> wrote:
>
>
>
> Maybe Jan was afraid that a new version could come into the public too
early, others can see it as new release - and then the problem is just
starting: we have to deny this, discussions here and there, and nobody
wants to have this mess.
>

I would think we would welcome the publicity.

> However, all the problems can be easily solved with coordination and
communication (e.g., offering binaries only from Apache infra systems like
[hidden email], agreeing on file nameing to differentiate clearly from release
builds, etc.).
>
> Marcus
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Windows build machine setted up

Marcus (OOo)
In reply to this post by Michal Hriň-3
Am 08/07/2015 09:50 AM, schrieb Michal Hriň:

> Thanks for providing a binary, but I am a bit concerned that a version
> is
> made public, before the PMC have even spoken about being ready to make
> a
> release candidate or started voting on a release candidate.
>
> Is this coordinated with the release manager for 4.1.2 ?
>
> Please do not misunderstand me, I think it is great that work is being
> done, I am just surprised we are ready to go public with 4.1.2 even as
> a
> pre-view.
>
> <hrin>
>
> OK. Binary is deleted.
>
> This was not coordinated, that was only snapshot .. not release
> candidate. All in all Linux 32bit builds from AOO410 branch are on
> buildbots, so everybody can downlaod it, this is not secret.
>
> Sorry, that I was excited and want to show it publically.
>
> </hrin>

please don't put too much negative interpretion into some answers. Of
course, it's great that you create builds from the new branch. It's also
OK to publish this as download offer.

Unfortunately, I haven't seen the file name structure you have used. But
please make sure that you always add a term like "Early Preview", "Early
Access", "Dev-Snapshot" or something else that cannot be mixed-up with a
Beta or Release version.

BTW:
Do you still have the access problem with your [hidden email] account? If
so, we (maybe together with Infra) should solve this. Then you can save
the binaries there to indicate that the work comes from an AOO committer
and not from somewhere else.

As said before, please keep up the good work. :-)

Marcus

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Windows build machine setted up

Michal Hriň-3
In reply to this post by Michal Hriň-3
BTW:
Do you still have the access problem with your [hidden email] account? If
so, we (maybe together with Infra) should solve this. Then you can save
the binaries there to indicate that the work comes from an AOO
committer
and not from somewhere else.

<hrin>

Yes, I have still this problems. Solving this will be great. Thanks !


</hrin>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Windows build machine setted up

jan i
On 8 August 2015 at 20:21, Michal Hriň <[hidden email]> wrote:

> BTW:
> Do you still have the access problem with your [hidden email] account? If
> so, we (maybe together with Infra) should solve this. Then you can save
> the binaries there to indicate that the work comes from an AOO
> committer
> and not from somewhere else.
>
> <hrin>
>
> Yes, I have still this problems. Solving this will be great. Thanks !
>
you wrote you had uploaded the SSH keys to id.apache.org, that is a good
first step.

Next a couple of questions:
- which terminal program do you use ?
I use putty, and had to generate the keys with puttygen, you also have to
remember to
configure the terminal program to use SSH (not telnet) and give a path to
your part of the key.

- What exactly happens ? is your key rejected or do you get some kind of
key error ?

rgds
jan i.


>
>
> </hrin>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>