Issue 6093 in pharo: Switch from SmalltalkHub to SS3 for ConfigurationBrowser in Pharo 2.0

Status: FixToInclude
Owner: [hidden email]
Labels: Type-Bug Milestone-2.0

New issue 6093 by [hidden email]: Switch from SmalltalkHub to SS3 for  
ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

Discussion is here:
http://lists.gforge.inria.fr/pipermail/pharo-project/2012-June/066377.html

Fix is attached

Attachments:
        MetacelloConfigurationBrowser-pharoDistribution.st  373 bytes


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

I'm not sure about this... I hardly believe there are "trusted" packages  
for Pharo 2.0 already. In part, because 2.0 itself is unstable now.
I much would prefer continue using MetacelloRepository as inbox while  
working on a process to auto-verify configurations (or be confident our  
trusted versions are really trusted)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

It is a kind of chicken-egg problem: if it remains empty, nothing will be  
tested/ported to 2.0, that can hardly be the goal. Not everything is  
Seaside or OB, there are lots of smaller libraries/frameworks.

Yes, things will break, but at the end, when we release 2.0, there will be  
stuff ready.

How the validation/blessing/trusting will work is an orthogonal problem  
that cannot be fixed at once, nor should it block progress.




_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

We have nothing to loose: Package maintainers can already follow the
progress, can easily load and update their configs and in the end we
have the configs that are already working or prepared for Pharo 2.0.

It will also quickly show which configs follow and which projects are long  
dead.

But we have to be aware that we do a final check on them
before releasing Pharo 2.0 into the wild.

Since we do not have a process to auto-verify we should follow our Pharo
rules: one little step after the other.

Currently I think it can help improving the situation so lets do it.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

yeah, but MetaRepos are intended to be for trusted configurations, for  
untrusted is the inbox (which, for now, is MetacelloRepository), I don't  
understand why we need another dirty repository.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #5 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

said so... we really need to move out from squeaksource. Maybe we need to  
create MetacelloInboxForPharo20 in ss3 (I can move all configurations from  
MetacelloRepository to there, if we agree)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #6 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

ok for me and I would prefer to move to smalltalk hub. Can you ask nicolas  
when we will finish the search?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #7 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

"MetacelloInboxForPharo20" and moving all configs there would
completely confuse people. Avoid more duplications

PLEASE DO NOT MAKE THE CHAOS BIGGER THAN IT ALREADY IS:

  1. people know that "MetacelloRepository" (on SqS) contains "ALL"  
configurations
     with each version

  2. and then we have repos like "MetaRepoForPharoXX" which are "VERSION  
SPECIFIC"
     where the configs that are working are copied to

This is easy to explain and enough duplication for now.

So if you maintain "MyKillerApp" you can
   - commit any new version of ConfigurationOfMyKillerApp  
in "MetacelloRepository"
   - if you know that it is working in Pharo 1.4. you make a copy  
in "MetaRepoForPharo14"


That SqSource is not reliable is another problem. But then we should
move the generell "MetacelloRepository" from SqS to SS3.


And to stay on topic for this issue: for Pharo 2.0 I again suggest to
use the already created http://ss3.gemstone.com/ss/MetaRepoForPharo20

since:
  - old squeaksource is not reliable
  - smalltalkhub is not yet ready






_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #8 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

+10 with Torsten

If we want to get one-click config loading to just work, we need to work on  
it now.

Cleanup, if necessary, and validation can be done later too.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #9 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

So what exactly now should be done?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #10 on issue 6093 by [hidden email]: Switch from  
SmalltalkHub to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

In the latest 2.0 the Configuration Browser shows 2 tabs:
- from http://smalltalkhub.com/mc/Pharo/Packages20/main that is empty and  
where we cannot write
- from http://www.squeaksource.com/MetacelloRepository that is full of too  
generic stuff
Torsten started this writeable repo for 2.0
- http://ss3.gemstone.com/ss/MetaRepoForPharo20
It would be nice if that were visible I guess.
During development of 2.0 we need to build up a set of metacello configs  
specific for 2.0
Currently we have an empty tab and one that is too full.
Ask Esteban.
We could make a 3rd tab for  
http://ss3.gemstone.com/ss/MetaRepoForPharo20 ;-)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Workneeded

Comment #11 on issue 6093 by [hidden email]: Switch from  
SmalltalkHub to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

I I guess this issue is not "FixToInclude"


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixToInclude

Comment #12 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

In the past
  - we used Squeaksource http://squeaksource.com/MetaRepoForPharo14 for  
Pharo 1.4

What is required
  - a repo for Pharo 2.0 proved configs

The situation
  - SqueakSource is unreliable so we will not host it there
  - SmalltalkHub is not ready yet
  - SS3 at gemstone is ready and usable

The proposal:
  - use http://ss3.gemstone.com/ss/MetaRepoForPharo20 which is already
    set up and ready for 2.0

the fix:
  - was attached on Jun 20, 2012

The next step:
  - the integration of "MetacelloConfigurationBrowser-pharoDistribution.st"  
as
    attached above

Later we can switch to SmalltalkHub at any time. No problem for the future  
and
we can move forward without loosing our energy in endless discussions

So the only work needed is to integrate the fix.

When SmalltalkHub is really usable in the future or an automatic config  
tester
is ready we can switch. For now I would just do the move from SqS to SS3
to get a reliable server. Nothing more




_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #13 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

Since the monkey does not like Changesets the fix is included in

SLICE-Issue-6093-Switch-from-SmalltalkHub-to-SS3-for-ConfigurationBrowser-in-Pharo-20-tbn.1


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Integrated

Comment #14 on issue 6093 by [hidden email]: Switch from  
SmalltalkHub to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

in 2.0 185


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #15 on issue 6093 by [hidden email]: Switch from SmalltalkHub  
to SS3 for ConfigurationBrowser in Pharo 2.0
http://code.google.com/p/pharo/issues/detail?id=6093

Thanks Markus for integration. The current broken SmalltalkHub

http://lists.gforge.inria.fr/pipermail/pharo-project/2012-July/067225.html

shows that it was a wise decision for the actual situation to use SS3.
That does not mean that we will not follow and watch SmalltalkHub
closely to switch to it in the future or find a general mirror strategy.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker