+1
On 4/2/2010 8:12 AM, George Paul wrote:
> +1
> We should review the jira issues for 2.0.0 release and determine the
> final 2.0.0 list.
> -George
>
> On 3/31/10 7:12 PM, Leif Hedstrom wrote:
>> Hi all,
>>
>> I'd like to suggest that we start the 2.0.0 release process on 4/12, and
>> wanted to
+1
We should review the jira issues for 2.0.0 release and determine the
final 2.0.0 list.
-George
On 3/31/10 7:12 PM, Leif Hedstrom wrote:
> Hi all,
>
> I'd like to suggest that we start the 2.0.0 release process on 4/12, and
> wanted to see what everyone thinks about that. I was going to suggest
+1 on all 3 items. I've gone through the current 2.0.0 issues/features
list on Jira and signed up for the ones I can commit to currently.
-George
On 2/1/10 2:08 PM, Leif Hedstrom wrote:
> Hi all,
>
> I'd like to make a number of "proposals" here for a release schedule.
> Please comment and/or vot
On 02/01/2010 06:09 PM, John Plevyak wrote:
+1, though I would like to see the list of features
we want/anticipate for 2.0.0 and maybe some names
(particularly if I am on that list :)
I don't think you are on the hook for any of them, but feel free to look
at that Jira list :
+1, though I would like to see the list of features
we want/anticipate for 2.0.0 and maybe some names
(particularly if I am on that list :)
john
On 2/1/2010 2:08 PM, Leif Hedstrom wrote:
> Hi all,
>
> I'd like to make a number of "proposals" here for a release schedule.
> Please comment
On 02/01/2010 05:42 PM, Nick Kew wrote:
No votes yet, but +1 on taking a direction that can lead to release.
It would be good to see the trunk-vs-dev issue sorted at the same
time, so people like me know where to start from when hacking on
the edges of the code or contributing patches.
Yes
On Mon, 01 Feb 2010 15:08:06 -0700
Leif Hedstrom wrote:
> Hi all,
>
> I'd like to make a number of "proposals" here for a release schedule.
> Please comment and/or vote +- on each one of the items below.
No votes yet, but +1 on taking a direction that can lead to release.
It would be good to s
