Issue 5379 in pharo: Cut the .changes file upon release

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 5379 in pharo: Cut the .changes file upon release

pharo
Status: Workneeded
Owner: [hidden email]
Labels: Type-Cleanup Milestone-1.4

New issue 5379 by [hidden email]: Cut the .changes file upon release
http://code.google.com/p/pharo/issues/detail?id=5379

not really an issue,
but imo we cannot keep going like that.
The changes file is 36 MB now, and if we keep it like that i bet it will be  
over 50Mb in 1.5



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5379 in pharo: Cut the .changes file upon release

pharo

Comment #1 on issue 5379 by [hidden email]: Cut the .changes file  
upon release
http://code.google.com/p/pharo/issues/detail?id=5379

condensed changes is 12MB.

See

https://ci.lille.inria.fr/pharo/job/Pharo%201.4%20condenseChanges/

Condese sources is broken (as it should be because there is no test for  
it ;-)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5379 in pharo: Cut the .changes file upon release

pharo
Updates:
        Status: Duplicate
        Mergedinto: 4843

Comment #2 on issue 5379 by [hidden email]: Cut the .changes file  
upon release
http://code.google.com/p/pharo/issues/detail?id=5379

I merge this into the other report about large .changes and change the  
title of that


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