On 26 Dec 2013, at 15:37, Ben Coman <[email protected]> wrote:
> With the code freeze for Pharo 3.0 and potentially the milestone on some more
> invasive Fogbugz cases being pushed back, probably its better to set most of
> those to Pharo 4.0 or 3.1 rather than just 'later' and losing them among the
> historical ones carried forward from the old issue tracker (even though those
> also need to be dealt with).
>
> So could the next set of milestones following Pharo 3.0 be defined on Fogbugz?
>
yes! but not “a set”, but to keep it simple one for Pharo4.
Marucus
