Development

We recently released Buildr 1.3.2, focusing strictly on bug fixes.
1.3.3 release scheduled for August will also focus on bug fixes and
better error reporting.  The bulk consists of issues reported,
tested(!) and patched by community members.  There's parallel work to
add C/C++ support to Buildr, currently discussed on the mailing list,
and we're seeing the first set of test cases for Eclipse tasks.  Our
little master plan to not accept patches without test cases may work
out after all.

Community

In spite of our best efforts to send everyone on summer vacation,
traffic is steadily picking up on the mailing list.

Issues before graduation

1.3.2 cleared up some missing/mixed copyright issues that slipped past
QA in earlier releases, and as of now we have no outstanding licensing
issues.



On Mon, Aug 4, 2008 at 11:10 AM, Matthieu Riou <[EMAIL PROTECTED]> wrote:
> Actually, looking at the schedule it seems I've messed up somewhere as we've
> been reporting consistently one month early this year:
>
> http://wiki.apache.org/incubator/ReportingSchedule
>
> So by reporting this month, we should get back on track :)
>
> Matthieu
>
> On Mon, Aug 4, 2008 at 11:06 AM, Matthieu Riou <[EMAIL PROTECTED]>wrote:
>
>> Hi,
>>
>> I just realized that we forgot to report to the board last month. It's
>> partly my fault as I forgot to add us to the July report page [1] and so
>> nobody screamed. So we should report this month instead [2] (due for August
>> 13th) and then again in October.
>>
>> Anybody willing to give it a shot for this month? For reference, the last
>> one was in April [3].
>>
>> Thanks,
>> Matthieu
>>
>> [1] http://wiki.apache.org/incubator/July2008
>> [2] http://wiki.apache.org/incubator/August2008
>> [3] http://wiki.apache.org/incubator/April2008
>>
>

Reply via email to