Re: Issue 6190 in pharo: Fix "Software Update" for current release

Updates:
        Summary: Fix "Software Update" for current release
        Status: Accepted
        Cc: [hidden email]
        Labels: -Type-Enh Type-Bug

Comment #2 on issue 6190 by [hidden email]: Fix "Software Update"  
for current release
http://code.google.com/p/pharo/issues/detail?id=6190

Shouldn't updates past 14444 change the version to 1.4.1?


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

Comment #3 on issue 6190 by [hidden email]: Fix "Software Update"  
for current release
http://code.google.com/p/pharo/issues/detail?id=6190

We did that in the past. It's a mess. I was tired of it. Lots of work by  
hand...

We decided for 1.3 that the update number is enough and intermediate  
versions are not needed.

Now we un-decided. But I will not do it. :-)


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

Comment #4 on issue 6190 by [hidden email]: Fix "Software Update"  
for current release
http://code.google.com/p/pharo/issues/detail?id=6190

Ah, and it's of course the release that is 1.4.1, not the current.

Else what's the point of the 1.4.1?

In the past we had 1.2.1a and then 1.2.1... until I got mad changing the  
version umber wrongly all the time.




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

Comment #5 on issue 6190 by [hidden email]: Fix "Software Update"  
for current release
http://code.google.com/p/pharo/issues/detail?id=6190

Re the bug fix updates:
1. Is the first update after the 1.4 release part of 1.4.1 (which sounds  
right to me), or
2. are updates after the release of 1.4 part of 1.4 until the release of  
1.4.1?

If it's #1, it seems like immediately after a release, we should start a  
new update list & Jenkins job for the minor bug fix release e.g. 1.4.1, and  
disable the build for the released version, all at the same time we set all  
that up for the next major/feature release e.g. 2.0. This way, nothing will  
download until the release of 1.4.1, when we can maybe include one more  
update to 1.4 that updates the version number to 1.4.1 and kicks off the  
update for the new version. This would avoid any suffixes e.g.  
1.4.1alpha/beta...

It seems like changing the version in the image is easy enough. What else  
would be involved?


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

Comment #6 on issue 6190 by [hidden email]: Fix "Software Update" for  
current release
http://code.google.com/p/pharo/issues/detail?id=6190

it is 1.4 "Summer", with no number and that's on purpose... I don't want do  
the hard work either (and it is A LOT)... and the update number is enough  
to track problems.
The important part is to integrate the fixes and make a better release  
version (one-click included) so, we have a better environment for:

- stability of production environments
- "friendiness" to new comers




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

Comment #7 on issue 6190 by [hidden email]: Fix "Software Update"  
for current release
http://code.google.com/p/pharo/issues/detail?id=6190

Oh... now I understand. Thanks, Esteban... So we're really just talking  
about updating the download links and making an announcement?


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

Comment #8 on issue 6190 by [hidden email]: Fix "Software Update" for  
current release
http://code.google.com/p/pharo/issues/detail?id=6190

well... and include OB and Spotlight and maybe a better Configurations  
Browsers


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

Updates:
        Status: Closed

Comment #9 on issue 6190 by [hidden email]: Fix "Software Update"  
for current release
http://code.google.com/p/pharo/issues/detail?id=6190

Oh, good. I really like what you did with the config browser... much more  
useful already... and spotlight is coooool... So we can close this...


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