AFAIK, Lazarus 0.9.30 will be the last Lazarus release able to be compiled with an official FPC release. The current Lazarus trunk needs FPC 2.5.1 and FPC 2.6.0 is going to be released in a distant future. So we have, for the first time, a "gap": you can't be partly bleeding-edge anymore. Before that, I used to get Lazarus from SVN (and report a few issues/send some patches along the way) with a "stable" FPC. When 0.9.30 comes out in a few days, we will have to choose between Lazarus/FPC both official releases (an no more bug reports/patches) or Lazarus/FPC both from bleeding edge SVN, with 2 times more probability of instability. I'm aware I'm whining here, but I think I'm not the only one in this situation.
2011/3/4 Marco van de Voort <mar...@stack.nl> > On Mon, Feb 28, 2011 at 10:23:44AM -0300, Alexsander Rosa wrote: > > Ok, thanks. The bugtrack "roadmap" page has 3.0.0 only, probably I was > > looking in the wrong place. > > See http://www.freepascal.org/faq.var#versions for a short summary about > versioning. > > > Where do I find the roadmap for 2.6.0? Is there a way to filter the > issues > > list to show what's missing? > > FPC does not maintain roadmaps and the featureset of a major branch is more > or less based on what is in SVN on the moment of branching. There is of > course some communication about that, but it is mostly internal and > informal. > > That being said, specially when branching a major branch, it is hard to get > an overview what has been added but not merged (for e.g. the release > manifest), and some more administration on this front wouldn't be bad. > > Something like Jonas did with User changes, and then for all features, not > just the breaking ones. > > -- > -- Atenciosamente, Alexsander da Rosa http://rednaxel.com
-- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
