point development and bleedingEdge for Pharo1 & 2 to release 3.1

> On 25 Jan 2016, at 15:59, Stephan Eggermont <[hidden email]> wrote:
>
> Name: ConfigurationOfSeaside3-StephanEggermont.282
> Author: StephanEggermont
> Time: 25 January 2016, 3:49:27.912877 pm
> UUID: 0555e1e9-9b01-46e1-9317-0d018afd478a
> Ancestors: ConfigurationOfSeaside3-EstebanMaringolo.281
>
> No development and bleedingEdge of release3.2 for Pharo 1 and 2,
>
> spec for: #('pharo1.x' 'pharo2.x') version: #'release3.1'.
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

> On 31 Jan 2016, at 16:56, Stephan Eggermont <[hidden email]> wrote:
>
> On 31-01-16 11:23, Johan Brichau wrote:
>> Hi Stephan,
>>
>> Is it a good idea to tag bleedingEdge and development on Pharo 1 and 2 such that it’s a fixed release 3.1 ?
>>
>> Sounds confusing to me for people, no?
>
> Yes, and I presume it is better than non-running code?
> Should I add a "no development and bleedingEdge anymore on Pharo 1 and 2"?

>
>> On 31 Jan 2016, at 16:56, Stephan Eggermont <[hidden email]> wrote:
>>
>> On 31-01-16 11:23, Johan Brichau wrote:
>>> Hi Stephan,
>>>
>>> Is it a good idea to tag bleedingEdge and development on Pharo 1 and 2 such that it’s a fixed release 3.1 ?
>>>
>>> Sounds confusing to me for people, no?
>>
>> Yes, and I presume it is better than non-running code?
>> Should I add a "no development and bleedingEdge anymore on Pharo 1 and 2"?
>
> Can we make Metacello say there is no development nor bleedingEdge versions on those platforms ?
> I seem to remember there was a way to do that but my mind might play tricks on me…