You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Stefan Seelmann <ma...@stefan-seelmann.de> on 2016/03/12 13:17:51 UTC
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Hi Shawn,
On 03/12/2016 12:13 PM, Shawn McKinney wrote:
> The fact that we’re now 70 hours in w/out a response tells me one of two things. Either nobody’s interested, or the test procedures are too hard / confusing. I choose the latter.
Just to clarify: the 72 hours vote period are the minimum, it's totally
ok to let the vote open for longer.
But I agree that it's strange to not get any response at all.
I'll check the packages this weekend. But I'll only check the build and
the Apache release requirements. I won't check the functionality because
(I'm honest) I don't have any usecase where to use Fortress (neither at
job nor at private projects) and I just cannot invest the time to dig into.
Instead I'd like to encourage the Fortress community (Chris, Jan, the
other Shawn, just to name a few) to test the release packages and give
your vote. That is really important because you use it all the time and
you can jugde if it works or not. Your vote counts!
Kind Regards,
Stefan
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Chris Pike <cl...@psu.edu>.
+1
Rebuilt VM with 1.0-RC42 tag, ran junit tests (still have to run them twice since one fails on first run...), built our app with tag and ran some smoke tests
----- Original Message -----
From: "Shawn McKinney" <sm...@apache.org>
To: fortress@directory.apache.org
Cc: "Apache Directory Developers List" <de...@directory.apache.org>
Sent: Saturday, March 12, 2016 8:41:55 AM
Subject: Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
> On Mar 12, 2016, at 7:20 AM, Chris Pike <cl...@psu.edu> wrote:
>
> I'm new to the process and I think it would help if you provided a basic overview... Who is allowed vote, how does someone vote, what happens when a vote is passed, what is expected of someone who votes yes, etc...?
Chris,
a really good question. The short answer, anyone can vote.
The longer answer. There are two types of votes, binding and non-binding. PMC’s are binding, everyone else is non. As for what is expected, make sure the packages build cleanly on either / both java 7 & 8. Usually that is enough as tests should automatically run on mvn install. Fortress is a bit different now and requires the tests to be run manually after the setup and config (which is itself a problem that deserves attention).
Test the component in the way you use it. I know you have run with a mirror. Pull the 1.0-RC42 tag and run that through your smoke tests. A reasonable effort is good. You shouldn’t have to spend more than an hour in the worst case. In truth it should be more like 10 minutes.
To place your vote, reply to this thread with a
+1 (accept)
+/- 0 (abstain)
-1 (reject)
Your vote is non-binding but like Stefan said actually counts for quite a lot. I usually also comment on the specifics of what I did. e.g. ran the mvn install and mvn tests on java 8, centos 7, or whatever.
There is of course more to this answer, but this should get you started. I’ll let the old-timers chime in with the definitive version.
Shawn
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Shawn McKinney <sm...@apache.org>.
> On Mar 12, 2016, at 7:20 AM, Chris Pike <cl...@psu.edu> wrote:
>
> I'm new to the process and I think it would help if you provided a basic overview... Who is allowed vote, how does someone vote, what happens when a vote is passed, what is expected of someone who votes yes, etc...?
Chris,
a really good question. The short answer, anyone can vote.
The longer answer. There are two types of votes, binding and non-binding. PMC’s are binding, everyone else is non. As for what is expected, make sure the packages build cleanly on either / both java 7 & 8. Usually that is enough as tests should automatically run on mvn install. Fortress is a bit different now and requires the tests to be run manually after the setup and config (which is itself a problem that deserves attention).
Test the component in the way you use it. I know you have run with a mirror. Pull the 1.0-RC42 tag and run that through your smoke tests. A reasonable effort is good. You shouldn’t have to spend more than an hour in the worst case. In truth it should be more like 10 minutes.
To place your vote, reply to this thread with a
+1 (accept)
+/- 0 (abstain)
-1 (reject)
Your vote is non-binding but like Stefan said actually counts for quite a lot. I usually also comment on the specifics of what I did. e.g. ran the mvn install and mvn tests on java 8, centos 7, or whatever.
There is of course more to this answer, but this should get you started. I’ll let the old-timers chime in with the definitive version.
Shawn
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Pierre Smits <pi...@gmail.com>.
Hi Chris,
Every contributor participating in any of the Apache Directory's
(sub)projects is allowed to vote. Though some votes have mere impact.
See various descriptive documents of the project and of the ASF.
Best regards,
Pierre
On Saturday, March 12, 2016, Chris Pike <cl...@psu.edu> wrote:
> Shawn,
>
> I'm new to the process and I think it would help if you provided a basic
> overview... Who is allowed vote, how does someone vote, what happens when a
> vote is passed, what is expected of someone who votes yes, etc...?
>
> Thanks,
>
> ~Chris
>
>
>
> ----- Original Message -----
> From: "Shawn McKinney" <smckinney@apache.org <javascript:;>>
> To: "Apache Directory Developers List" <dev@directory.apache.org
> <javascript:;>>
> Cc: fortress@directory.apache.org <javascript:;>
> Sent: Saturday, March 12, 2016 8:13:21 AM
> Subject: Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
>
> > On Mar 12, 2016, at 6:48 AM, Shawn McKinney <smckinney@apache.org
> <javascript:;>> wrote:
> >
> >>
> >>
> >> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <mail@stefan-seelmann.de
> <javascript:;>> wrote:
> >>
> >> Instead I'd like to encourage the Fortress community (Chris, Jan, the
> >> other Shawn, just to name a few) to test the release packages and give
> >> your vote. That is really important because you use it all the time and
> >> you can jugde if it works or not. Your vote counts!
> >
> > This is a very good point and I too encourage others, regardless of
> project status, to place your vote. If you have benefited from this
> project in the past, now is a good time to show your appreciation.
>
> I want to turn this message around as it sounds a bit harsh. I neither
> expect nor compel testing help from this community. Your continued
> participation, via bug reports, code fixes, etc, is all that is needed from
> you for this project to continue to grow. But we would be appreciative of
> additional help testing this release, if possible.
>
> Thanks
>
> Shawn
>
--
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Shawn McKinney <sm...@apache.org>.
> On Mar 12, 2016, at 7:20 AM, Chris Pike <cl...@psu.edu> wrote:
>
> I'm new to the process and I think it would help if you provided a basic overview... Who is allowed vote, how does someone vote, what happens when a vote is passed, what is expected of someone who votes yes, etc...?
Chris,
a really good question. The short answer, anyone can vote.
The longer answer. There are two types of votes, binding and non-binding. PMC’s are binding, everyone else is non. As for what is expected, make sure the packages build cleanly on either / both java 7 & 8. Usually that is enough as tests should automatically run on mvn install. Fortress is a bit different now and requires the tests to be run manually after the setup and config (which is itself a problem that deserves attention).
Test the component in the way you use it. I know you have run with a mirror. Pull the 1.0-RC42 tag and run that through your smoke tests. A reasonable effort is good. You shouldn’t have to spend more than an hour in the worst case. In truth it should be more like 10 minutes.
To place your vote, reply to this thread with a
+1 (accept)
+/- 0 (abstain)
-1 (reject)
Your vote is non-binding but like Stefan said actually counts for quite a lot. I usually also comment on the specifics of what I did. e.g. ran the mvn install and mvn tests on java 8, centos 7, or whatever.
There is of course more to this answer, but this should get you started. I’ll let the old-timers chime in with the definitive version.
Shawn
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Chris Pike <cl...@psu.edu>.
Shawn,
I'm new to the process and I think it would help if you provided a basic overview... Who is allowed vote, how does someone vote, what happens when a vote is passed, what is expected of someone who votes yes, etc...?
Thanks,
~Chris
----- Original Message -----
From: "Shawn McKinney" <sm...@apache.org>
To: "Apache Directory Developers List" <de...@directory.apache.org>
Cc: fortress@directory.apache.org
Sent: Saturday, March 12, 2016 8:13:21 AM
Subject: Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
> On Mar 12, 2016, at 6:48 AM, Shawn McKinney <sm...@apache.org> wrote:
>
>>
>>
>> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>>
>> Instead I'd like to encourage the Fortress community (Chris, Jan, the
>> other Shawn, just to name a few) to test the release packages and give
>> your vote. That is really important because you use it all the time and
>> you can jugde if it works or not. Your vote counts!
>
> This is a very good point and I too encourage others, regardless of project status, to place your vote. If you have benefited from this project in the past, now is a good time to show your appreciation.
I want to turn this message around as it sounds a bit harsh. I neither expect nor compel testing help from this community. Your continued participation, via bug reports, code fixes, etc, is all that is needed from you for this project to continue to grow. But we would be appreciative of additional help testing this release, if possible.
Thanks
Shawn
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Chris Pike <cl...@psu.edu>.
Shawn,
I'm new to the process and I think it would help if you provided a basic overview... Who is allowed vote, how does someone vote, what happens when a vote is passed, what is expected of someone who votes yes, etc...?
Thanks,
~Chris
----- Original Message -----
From: "Shawn McKinney" <sm...@apache.org>
To: "Apache Directory Developers List" <de...@directory.apache.org>
Cc: fortress@directory.apache.org
Sent: Saturday, March 12, 2016 8:13:21 AM
Subject: Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
> On Mar 12, 2016, at 6:48 AM, Shawn McKinney <sm...@apache.org> wrote:
>
>>
>>
>> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>>
>> Instead I'd like to encourage the Fortress community (Chris, Jan, the
>> other Shawn, just to name a few) to test the release packages and give
>> your vote. That is really important because you use it all the time and
>> you can jugde if it works or not. Your vote counts!
>
> This is a very good point and I too encourage others, regardless of project status, to place your vote. If you have benefited from this project in the past, now is a good time to show your appreciation.
I want to turn this message around as it sounds a bit harsh. I neither expect nor compel testing help from this community. Your continued participation, via bug reports, code fixes, etc, is all that is needed from you for this project to continue to grow. But we would be appreciative of additional help testing this release, if possible.
Thanks
Shawn
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Shawn McKinney <sm...@apache.org>.
> On Mar 12, 2016, at 6:48 AM, Shawn McKinney <sm...@apache.org> wrote:
>
>>
>>
>> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>>
>> Instead I'd like to encourage the Fortress community (Chris, Jan, the
>> other Shawn, just to name a few) to test the release packages and give
>> your vote. That is really important because you use it all the time and
>> you can jugde if it works or not. Your vote counts!
>
> This is a very good point and I too encourage others, regardless of project status, to place your vote. If you have benefited from this project in the past, now is a good time to show your appreciation.
I want to turn this message around as it sounds a bit harsh. I neither expect nor compel testing help from this community. Your continued participation, via bug reports, code fixes, etc, is all that is needed from you for this project to continue to grow. But we would be appreciative of additional help testing this release, if possible.
Thanks
Shawn
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Shawn McKinney <sm...@apache.org>.
> On Mar 12, 2016, at 6:48 AM, Shawn McKinney <sm...@apache.org> wrote:
>
>>
>>
>> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>>
>> Instead I'd like to encourage the Fortress community (Chris, Jan, the
>> other Shawn, just to name a few) to test the release packages and give
>> your vote. That is really important because you use it all the time and
>> you can jugde if it works or not. Your vote counts!
>
> This is a very good point and I too encourage others, regardless of project status, to place your vote. If you have benefited from this project in the past, now is a good time to show your appreciation.
I want to turn this message around as it sounds a bit harsh. I neither expect nor compel testing help from this community. Your continued participation, via bug reports, code fixes, etc, is all that is needed from you for this project to continue to grow. But we would be appreciative of additional help testing this release, if possible.
Thanks
Shawn
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Shawn McKinney <sm...@apache.org>.
> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
>
> On 03/12/2016 12:13 PM, Shawn McKinney wrote:
>> The fact that we’re now 70 hours in w/out a response tells me one of two things. Either nobody’s interested, or the test procedures are too hard / confusing. I choose the latter.
>
> Just to clarify: the 72 hours vote period are the minimum, it's totally
> ok to let the vote open for longer.
Yes that’s fine. It’s been almost a year since last release, a few more days won’t hurt anything.
>
> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
>
> I'll check the packages this weekend. But I'll only check the build and
> the Apache release requirements. I won't check the functionality because
> (I'm honest) I don't have any usecase where to use Fortress (neither at
> job nor at private projects) and I just cannot invest the time to dig into.
Stefan I understand (and respect) that viewpoint and appreciate your honesty. It’s refreshing. For the record, you’ve always been helpful, throughout our move of fortress into the apache directory project, up to the present time. And I will gladly accept any further help you can find the time for. Certainly verifying apache release requirements is important. Especially now we have added the other three as official apache releases. Actually I counted on exactly that from you and would have been surprised w/out it. :-)
>
> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
> Instead I'd like to encourage the Fortress community (Chris, Jan, the
> other Shawn, just to name a few) to test the release packages and give
> your vote. That is really important because you use it all the time and
> you can jugde if it works or not. Your vote counts!
This is a very good point and I too encourage others, regardless of project status, to place your vote. If you have benefited from this project in the past, now is a good time to show your appreciation.
Shawn
Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
Posted by Shawn McKinney <sm...@apache.org>.
> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
>
> On 03/12/2016 12:13 PM, Shawn McKinney wrote:
>> The fact that we’re now 70 hours in w/out a response tells me one of two things. Either nobody’s interested, or the test procedures are too hard / confusing. I choose the latter.
>
> Just to clarify: the 72 hours vote period are the minimum, it's totally
> ok to let the vote open for longer.
Yes that’s fine. It’s been almost a year since last release, a few more days won’t hurt anything.
>
> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
>
> I'll check the packages this weekend. But I'll only check the build and
> the Apache release requirements. I won't check the functionality because
> (I'm honest) I don't have any usecase where to use Fortress (neither at
> job nor at private projects) and I just cannot invest the time to dig into.
Stefan I understand (and respect) that viewpoint and appreciate your honesty. It’s refreshing. For the record, you’ve always been helpful, throughout our move of fortress into the apache directory project, up to the present time. And I will gladly accept any further help you can find the time for. Certainly verifying apache release requirements is important. Especially now we have added the other three as official apache releases. Actually I counted on exactly that from you and would have been surprised w/out it. :-)
>
> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>
> Instead I'd like to encourage the Fortress community (Chris, Jan, the
> other Shawn, just to name a few) to test the release packages and give
> your vote. That is really important because you use it all the time and
> you can jugde if it works or not. Your vote counts!
This is a very good point and I too encourage others, regardless of project status, to place your vote. If you have benefited from this project in the past, now is a good time to show your appreciation.
Shawn