Hi Nicolai Athens is important for us too. Now none of us in the team has the experience in Cairo. Users of Athens usually do not want to invest understanding it either.
I tried to create the conditions that Igor could stay in the communautee but it failed because alone I could not do it. Now Athens is what is in Pharo. I have no idea of the rest. Stef On Wed, Jul 26, 2017 at 4:42 PM, Nicolai Hess <[email protected]> wrote: > > > 2017-07-26 16:25 GMT+02:00 Stephane Ducasse <[email protected]>: >> >> I imagine that hot-fixes means when we found a serious bug in the >> alpha version and see that it is also in the previous version. >> >> Now Hilaire if you want a change to be integrated in Pharo and Pharo >> 60 for example. >> >> - we should have a bug entry on fogbugz (you see when I read the >> emails I do not see the bug entry >> so I have to look for it and lose time - because crawling the bug >> database is tedious, so this is a lot more efficient to send also bug >> entries). >> - we should have a fix. >> - it should be tagged for Pharo 60. >> - it should be validated (pass the tests). >> >> Each time we introduce a fix, we may break sometimes so we pay really >> attention to have >> limited fixes with limited impact. >> >> For the ones you mentioned: >> >> - I cannot find the PNGReader bug entry. I read all the mails of the >> thread. >> So this is not efficient. >> >> - https://pharo.fogbugz.com/f/cases/20166/ is there but there is no >> fix so we will have > > > The problem with fixes for Athens is, that nobody could tell we what the > current state is. > > http://forum.world.st/current-athens-configuration-td4914441.html#a4914488 > > the latest changes are from alexej and I guess they are important for sparta > and the further development for bloc/sparte for pharo 7/8 > We can not just take the latest version and put it in pharo 6, and hope that > it will work. > We need for this external package a good communication about changes and > versions. > This did not happen here. And I am not sure if we maybe already put some > changes in pharo 6, that are not at the athens repository. > I once considered athens as an important package for the new pharo ui, but > the way it is handled now looks more like abandoned. > > that is the reason why I just put the fix for 20166 in the comment of the > bug entry instead of providing a slice / or update the version on the > repository. > > > It is ok if we tell hilaire to not just put bugreports on the ml but create > a bug report on fogbugz instead. So people can fix/provide a slice and run > the validation. > But this happend in this case. It is just that we do not get it right to > handle this case because it depens on athens. > > >> >> >> People are nice and trying to help now everybody has its own agenda >> and we set these "rules" >> to avoid that we all lose time. If you want that people help you then >> try to adhere to such best >> practices. >> >> Follow the Pharo process. >> >> Stef. >> >> >> On Tue, Jul 25, 2017 at 6:01 PM, Hilaire <[email protected]> wrote: >> > Hi, >> > >> > It is the other minor bugs fixes details which were missing. >> > >> > What is hot-fixes? >> > >> > Hilaire >> > >> > >> > -- >> > Dr. Geo >> > http://drgeo.eu >> > >> > >> > >> >
