Frank Shearar uploaded a new version of ReleaseBuilder to project The Trunk:
http://source.squeak.org/trunk/ReleaseBuilder-fbs.89.mcz ==================== Summary ==================== Name: ReleaseBuilder-fbs.89 Author: fbs Time: 31 December 2012, 8:46:19.365 pm UUID: a99900e3-d3c9-4284-afb5-89c046ddc44d Ancestors: ReleaseBuilder-fbs.88 Transferring packages to the new update stream requires valid credentials. This lets the release manager transfer things without changing source, and without storing credentials in the image. =============== Diff against ReleaseBuilder-fbs.88 =============== Item was removed: - ----- Method: ReleaseBuilder class>>transferCurrentPackages (in category 'scripts') ----- - transferCurrentPackages - "Copy the packages currently loaded in the image from the trunk repository to my releaseRepository." - | trunkRep releaseRep | - trunkRep := self trunkRepository. - releaseRep := self releaseRepository. - MCWorkingCopy allManagers do: - [ : eachWorkingCopy | eachWorkingCopy ancestors do: - [ : eachVersionInfo | (releaseRep includesVersionNamed: eachVersionInfo versionName) ifFalse: - [ (trunkRep versionWithInfo: eachVersionInfo) - ifNil: [ Warning signal: eachVersionInfo name , ' not found in ', trunkRep ] - ifNotNilDo: [ : ver | self storeVersion: ver ] ] ] ]! Item was added: + ----- Method: ReleaseBuilder class>>transferCurrentPackagesAsUser:password: (in category 'scripts') ----- + transferCurrentPackagesAsUser: username password: password + "Copy the packages currently loaded in the image from the trunk repository to my releaseRepository." + | trunkRep releaseRep | + trunkRep := self trunkRepository. + releaseRep := self releaseRepository + user: username; + password: password; + yourself. + MCWorkingCopy allManagers do: + [ : eachWorkingCopy | eachWorkingCopy ancestors do: + [ : eachVersionInfo | (releaseRep includesVersionNamed: eachVersionInfo versionName) ifFalse: + [ (trunkRep versionWithInfo: eachVersionInfo) + ifNil: [ Warning signal: eachVersionInfo name , ' not found in ', trunkRep ] + ifNotNilDo: [ : ver | releaseRep storeVersion: ver ] ] ] ]! |
On 31 December 2012 20:46, <[hidden email]> wrote:
> Frank Shearar uploaded a new version of ReleaseBuilder to project The Trunk: > http://source.squeak.org/trunk/ReleaseBuilder-fbs.89.mcz > > ==================== Summary ==================== > > Name: ReleaseBuilder-fbs.89 > Author: fbs > Time: 31 December 2012, 8:46:19.365 pm > UUID: a99900e3-d3c9-4284-afb5-89c046ddc44d > Ancestors: ReleaseBuilder-fbs.88 > > Transferring packages to the new update stream requires valid credentials. This lets the release manager transfer things without changing source, and without storing credentials in the image. Consider this the first commit on the 4.5 stream! frank |
On Mon, Dec 31, 2012 at 3:47 PM, Frank Shearar <[hidden email]> wrote: Consider this the first commit on the 4.5 stream! Does that mean I can push 4.5 stuff to trunk now?
Colin |
On 31 December 2012 21:19, Colin Putney <[hidden email]> wrote:
> > > On Mon, Dec 31, 2012 at 3:47 PM, Frank Shearar <[hidden email]> > wrote: >> >> Consider this the first commit on the 4.5 stream! > > > Does that mean I can push 4.5 stuff to trunk now? > > Colin Yes: the 4.4 update stream is up and running. I think. It might be a UI bug. I get "Unable to retrieve updates from remote repository." in Utilities class >> #updateFromServer because, I think, MCMcmUpdater class >> #updateListFor: returns an empty collection because there are in fact no changes between the base 4.4 image and the original versions of things in the squeak44 repository. I'll look into that another time though. So we can expect Environments to land soon? :) frank |
On Mon, Dec 31, 2012 at 5:40 PM, Frank Shearar <[hidden email]> wrote: So we can expect Environments to land soon? :) Yes. I've committed the Environments bootstrap, so the trunk should now have the same functionality as the prototype image I posted with the original proposal. The implementation is slightly different, because I renamed CompilationContext to CompilationCue to avoid naming conflicts inside the compiler. It's not the best name, but all the good ones already mean something else.
Colin |
Free forum by Nabble | Edit this page |