Makes sense.
Andrus
On Nov 10, 2008, at 10:43 AM, Aristedes Maniatis wrote:
>
> On 10/11/2008, at 7:31 PM, Andrus Adamchik wrote:
>
>> That's too optimistic (i.e. not gonna happen) .I think we should
>> keep 3.0 (without specific milestone) as a Fix Version for most
>> things, and change it to a next milestone once the issue is closed.
>
> I wanted to do some triaging though to get us out of this rut with
> 'M5 is just around the corner'. So I've created these versions:
>
> * 1.2.5 and 2.0.5 to keep anything we are targeting for a bug fix in
> those branches. Maybe that will be never in which case we delete the
> versions after 3.0 comes out. But it allowed me to mark 2.0 branch
> and 1.2 branch as being 'released' to get it out of the road map.
>
> * 3.0M1 - 3.0M4
>
> * 3.0M5. I've only assigned a couple of tasks to that which I
> thought people were working on. I moved inheritance away to 3.0 just
> now so only CAY-1077 and CAY-1058 are there now. In theory once they
> are done we release M5. Is there anything else which needs to go
> into the M5 list?
>
> * short term future: things which may or may not get done for 3.0.
> There are some things in here which should be moved to 3.0 if they
> definitely need to be done for that. But everyone needs to help out
> with those tasks they own. For instance any API changes which need
> to go into 3.0. Query generification anyone?
>
> * undefined future. Wish list ideas which no one is really working
> on any time soon.
>
>
> The goal is to get a better picture of what is left for M5 and for
> 3.0. Then we can answer the question "will there be M6 or just "3.0
> beta 1"?
>
>
> Ari
>
>
>
> -------------------------->
> ish
> http://www.ish.com.au
> Level 1, 30 Wilson Street Newtown 2042 Australia
> phone +61 2 9550 5001 fax +61 2 9550 4001
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
>
>
This archive was generated by hypermail 2.0.0 : Mon Nov 10 2008 - 03:57:50 EST