> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <[email protected]> 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 <[email protected]> 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 <[email protected]> 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
