[Foresight-devel] Re: Foresight 1.x Plans

[Kevin Harriss]

On 1/3/08, Thilo Pfennig <thilopfennig at foresightlinux.org> wrote:
>
> Am Thu, 03 Jan 2008 09:52:56 -0500
> schrieb Ken VanDine <ken at vandine.org>:
>
> > My hope would be to redirect the groups in fl:1 to fl:2 shortly after
> > 2.0 is released... which i hope is before GNOME 2.22 :)
>
> Uhm, right now my estimate is that Foresight 2 has about 5 % of the
> functionality of FL1. The goal was 100% - right now FL2 cant really
> compete with FL1 if you look at the number of packages and also it
> rather looks to be in a flow rather than in a state where one could
> begin doing actual packaging besides the core stuff. The whole building
> process is yet untransparent so I would fear that instead of having
> 100% functionality we would get a massive degression if we would really
> release on AND force users to switch. I always feared that we might
> ending up supporting two branches for a longer time  but now I dont
> really see another way than doing just that.


We wouldn't setup the redirect until we felt that fl2 was ready.  I agree
that if we setup the redirect today there would be a drastic regression in
functionality but we are not talking about setting up the redirect today,
since fl2 is still only in alpha.  Once the core is finished it will not be
hard to quickly migrate packages from fl1->fl2.  I really don't think we
should maintain to branches as it is already cumbersome to debug problems
since we have people running fl1 and fl2.  Also by maintaining 2 branches we
would be reducing the quality of the final product by dividing our efforts
on two final products.


So I am saying a release id Ok for me but automatically switching I
> would veto as long as there hasnt been happening a massive improvement
> in FL2. I also like to suggest that we could freeze 1.4.x in the 2.22
> state and then give it another 6 months and then let it die - I
> also would volunteer in maintaining some packages.


Again we are not talking about today but when FL2 is ready for release.
 When its ready I think we should only offer FL2 isos and automatically
redirect FL1 users to FL2.  The plan is to have the process as seamless as
possible so they wouldn't even notice a transition.

Maybe I am pessimistic or my vision is not that strong but i cant
> imagine a stable FL2 on March 2008. But I depend on a stable system.


I believe that we can have a stable and better version of foresight ready by
March with FL2 and if that is the case we will redirect users after the
release is tested.  If we don't have an acceptable version by then we won't
redirect users.

-- 
specialKevin
Kevin Harriss
http://www.foresightlinux.org