+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
+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 tha
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 we wait until after graduation, but I'm not sure I want to
wait for that, particularly if there are some details that would
dule.
> Please comment and/or vote +- on each one of the items below.
>
> Thanks,
>
> -- leif
>
> 1. Feature freeze for 2.0.0 is 2/22 2010. Features that have not been
> committed before this date will not make it into the 2.0.0
> release. We create the 2.0.
t; version help produce bug triage lists for releases,
since it's really easy to produce this directly from the Jira "main" TS
page.
There are still a bunch of Yahoo features / fixes that Y! would like in
the 2.0.0 release, but, IMO at least, we need to put a deadline for
t
lease schedule.
> Please comment and/or vote +- on each one of the items below.
>
> Thanks,
>
> -- leif
>
> 1. Feature freeze for 2.0.0 is 2/22 2010. Features that have not been
> committed before this date will not make it into the 2.0.0
> release. We cre
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
into the 2.0.0
release. We create the 2.0.0 release branch on this day, and trunk
should be considered frozen the entire day (or until we declare it
open again on the mailing list).
2. We start preparing for an alpha release, following the release
management guidel
