On Thu, Jun 30, 2011 at 12:16 AM, Igor Stasenko <[email protected]> wrote:
> On 30 June 2011 00:12, Stephan Eggermont <[email protected]> wrote: > > Igor wrote: > >>On 29 June 2011 15:56, Schwab,Wilhelm K <bschwab at anest.ufl.edu wrote: > >>> Having an archive seems sufficient - those who need old versions for > use or research can get them; they don't have to be clogging up the build > server. Sounds great. > >> > >>Indeed. If people would like to use older releases, they should look > >>for another place, not for build server. > >>Since build server are there to build & test bleeding-edge (under > >>development) versions, but not ones which already released and years > >>old. > > > > Ok, so you simply do not want the builds to be used by others. > > Its not about that we don't want users to download older versions > (they are available for download at pharo official site). > > No. Builds purpose is to follow a development process: new update -> new > build. > Now since we're done with 1.2 (and even almost done with 1.3) there > will be no new versions for these lines, > since all development is now in 1.4. > So, there is no reason to keep jobs for 1.2 and then 1.3 on build > server, because there will be no activity around it. > > What I understood is that there could be activity and changes not in pharo, but in the other project that is build/tested in Pharo. Say I am still quite developing Fuel, and I am commiting every day. No matter if it is on Pharo 1.2 or 1.3 what I want to say is that there is activity. Ok, the resources let us to that with the latest Pharo, so that we can test both at the same time: pharo itself and the third party. If you want third part with old pharo images, then you should get your own IC server. > > > > That's fine. > > > > Stephan Eggermont > > > -- > Best regards, > Igor Stasenko AKA sig. > > -- Mariano http://marianopeck.wordpress.com
