Ok that makes sense.  I will start working on the downloads section.  I
would like to get back in to coding after the release is done.  Also
potentially reviving the maven build.  But for now, I think working on the
web site will help let you all focus on code and release.  So that is what
I will do to contribute for now!

~Michael

On 12/22/13, 7:20 PM, "Ali Lown" <a...@lown.me.uk> wrote:

>> Great news on GIT.  I think that will hep us immensely.  I have been
>> following a lot of the mailing list.  Actually I spent quite while
>>reading
>> the list over the last few days.
>
>Yes. Subversion has been a point of 'stickiness' with new devs in the
>past, and the workflow was quite convoluted.
>
>> From an Apache perspective, I do think that since we have been
>>incubating
>> for several years now, it is important for us to make a release soon if
>>we
>> are to stay in this community.  We need to demonstrate some forward
>> progress.
>
>Indeed. We have spent most of this year iterating through the previous
>4 release candidates, so I think it would be hard to argue that we
>have made no forward progress.
>Getting the first release (on such a large codebase) is quite
>challenging, but I think we are now quite close to being in a suitable
>state for thorough inspection by the rest of the Incubator.
>
>> So it sounds like we need to get through the search feature, then turn
>> back to an RC5 release?
>
>Yep. Making the release once the search feature is pushed is a few hours
>work.
>Then, we want votes. Lots of votes. :)
>
>> What about the web site.  We don¹t really have a spot to advertise
>> releases. For a smooth re-entry, I could start to work on that as a
>> non-critical-path task, so that when we are ready to release the web
>>site
>> is ready.
>
>I haven't worked on that bit yet, since none of the RCs came close enough.
>If you could actually build the 'release download section' - which
>needs to make use of the Apache mirroring system - then that would be
>really useful!
>(Using the sample stuff on the wiki it can be thrown together in a few
>hours, but a polished, well-integrated download flow needs a bit more
>thought to link in to our existing site)
>
>More user documentation on the wiki (and actually pointing them to the
>wiki on the download/post-download page) is also always good!
>
>Ali


Reply via email to