On Mon, Jan 30, 2017 at 5:49 PM, Pavel Krivanek <[email protected]> wrote:
> Hi all, > > as announced, for the Pharo 6 release we set milestone of almost all low > priority issues to "Later". If you feel that some of the postponed issues > you reported are important and needs to be fixed before the release, please > change the milestone back to Pharo 6. > Bah, not only... If there is no code available for the fix, even it it says "Pharo 6" it cannot be integrated... > > All issues where it was possible to decide were tagged as ExistedInPharo5 > or NewInPharo6. The priority of most of the cases tagged as ExistedInPharo5 > were decreased to priority "Fix if time". If you think think that some of > these issues must be fixed for the next release, please increase their > priority. Otherwise such issues will be marked as "Later" before the > release. > > Again, increasing the priority does not magically fix the issues. > If you have a lot of subscribed issues, sorry for the noise in your inbox. > Thanks :P > > We have now 153 open issues for Pharo 6. > 48 issues are now with priority "Must fix" or higher. > We hope in release date on the 1st of April. > > Cheers, > -- Pavel > > >
