Re: [Pharo-dev] A thought about backporting

On Nov 16, 2013, at 7:48 PM, Tudor Girba wrote: > Hi Stef, > > I think you should be happy that the finally you have a filter that filters > out automatically all the negative energy mails :). I would love to have this addons and also for the negative mails I sent :) Stef > > Cheers, > Doru

Re: [Pharo-dev] A thought about backporting

Hi Stef, I think you should be happy that the finally you have a filter that filters out automatically all the negative energy mails :). Cheers, Doru On Sat, Nov 16, 2013 at 5:59 PM, Stéphane Ducasse wrote: > > On Nov 15, 2013, at 7:05 PM, Sean P. DeNigris > wrote: > > > btc wrote > >> My a

Re: [Pharo-dev] A thought about backporting

kilon alios wrote: Yeap definetly I have my bad days too like everyone so its ok btc. :) Thanks & no problem.  Your initial response was correct.  The way to maintain community standards is to push them. cheers -ben On Sat, Nov 16, 2013 at 6:59 PM, Stéphane Ducasse

Re: [Pharo-dev] A thought about backporting

Yeap definetly I have my bad days too like everyone so its ok btc. :) On Sat, Nov 16, 2013 at 6:59 PM, Stéphane Ducasse wrote: > > On Nov 15, 2013, at 7:05 PM, Sean P. DeNigris > wrote: > > > btc wrote > >> My apologies for how badly that poured out of me. > > > > We all have bad days :) > > o

Re: [Pharo-dev] A thought about backporting

On Nov 15, 2013, at 7:05 PM, Sean P. DeNigris wrote: > btc wrote >> My apologies for how badly that poured out of me. > > We all have bad days :) oh yes What is strange is that I did not see the original mail.I wonder if I lose mails. > > Actually, your passion may have awakened interest in

Re: [Pharo-dev] A thought about backporting

btc wrote > My apologies for how badly that poured out of me. We all have bad days :) Actually, your passion may have awakened interest in this important topic. I agree with you - I've been pushing semantic versioning since Dale (IIRC) explained it to me. At the time, I think the barrier was addi

Re: [Pharo-dev] A thought about backporting

Camillo Bruni wrote: On 2013-11-15, at 14:26, Stephan Eggermont wrote: btc wrote: OMG! I only just noticed on the "RELEASE" page [1] the linked file "Pharo2.0-win.zip" [3] >has a last-modified-date of 2013-11-13. What crack [2] are you smoking? A "released" >fil

Re: [Pharo-dev] A thought about backporting

On 15 November 2013 14:31, Camillo Bruni wrote: > > On 2013-11-15, at 14:26, Stephan Eggermont wrote: > > > btc wrote: > > >OMG! I only just noticed on the "RELEASE" page [1] the linked file > "Pharo2.0-win.zip" [3] >has a last-modified-date of 2013-11-13. What crack > [2] are you smoking? A "

Re: [Pharo-dev] A thought about backporting

On 2013-11-15, at 14:26, Stephan Eggermont wrote: > btc wrote: > >OMG! I only just noticed on the "RELEASE" page [1] the linked file > >"Pharo2.0-win.zip" [3] >has a last-modified-date of 2013-11-13. What crack > >[2] are you smoking? A "released" >file with a name like "Pharo2.0-win.zip" >

Re: [Pharo-dev] A thought about backporting

btc wrote: >OMG! I only just noticed on the "RELEASE" page [1] the linked file >"Pharo2.0-win.zip" [3] >has a last-modified-date of 2013-11-13. What crack >[2] are you smoking? A "released" >file with a name like "Pharo2.0-win.zip" >should NEVER change its contents. NEVER! It >SHOULD always

Re: [Pharo-dev] A thought about backporting

2013/11/15 Stéphane Ducasse > The point of noury is that it is better to have 2.0 and 2.1 and 2.2 and as > few as possible > and to have that as a public interface. > > After people can really pick a given version. +1 to this. Now we have the build number, but it is not as semantically represen

Re: [Pharo-dev] A thought about backporting

. This way > >> people could spot the difference to old downloads more easily. > >> > >> One often see's download pages of open source projects stating "Download > >> latest here" and > >> "Download previous versions here" with

Re: [Pharo-dev] A thought about backporting

e projects stating > "Download latest here" and > >> "Download previous versions here" with a list of older releases. > >> By using the Major.minor-build like "Pharo 2.0-627" people could pick > up what they want. > >> > >> M

Re: [Pharo-dev] A thought about backporting

or-build like "Pharo 2.0-627" people could pick up what they want. My proposal: lets use the update number more often. It would also help when people report bugs to know about the specific update number. It would also avoid the "I have a problem in Pharo 2.0" and "the one

Re: [Pharo-dev] A thought about backporting

>> "Download previous versions here" with a list of older releases. >> By using the Major.minor-build like "Pharo 2.0-627" people could pick up >> what they want. >> >> My proposal: lets use the update number more often. It would also help when &

Re: [Pharo-dev] A thought about backporting

eople could pick up what > they want. > > My proposal: lets use the update number more often. It would also help when > people report bugs > to know about the specific update number. > > It would also avoid the "I have a problem in Pharo 2.0" and "the

Re: [Pharo-dev] A thought about backporting

> latest here" and > > "Download previous versions here" with a list of older releases. > > By using the Major.minor-build like "Pharo 2.0-627" people could pick up > what they want. > > > > My proposal: lets use the update number more oft

Re: [Pharo-dev] A thought about backporting

p what > they want. > > My proposal: lets use the update number more often. It would also help when > people report bugs > to know about the specific update number. > > It would also avoid the "I have a problem in Pharo 2.0" and "the one from > last y

Re: [Pharo-dev] A thought about backporting

e often. It would also help when people report bugs to know about the specific update number. It would also avoid the "I have a problem in Pharo 2.0" and "the one from last year or the newer one with the backports?" cycle ;) Thx T. > Gesendet: Donnerstag, 14. Novem

[Pharo-dev] A thought about backporting

Hi, Here is a thought I want to share with you. Please don't misunderstand me. I'm really valuing the effort that people put into pharo, but I think sharing this will hopefully result in improving our system. I believe that back-porting is a false good idea. Consider simply this question: what