Change accompanying texts.

API-CHANGES.txt

@@ -1,249 +0,0 @@
-0.12.4:
-
-* Package Canvas renamed to Web
-
-* Object >> try:catch: deprecated in favour of BlockClosure >> tryCatch:
-
-+ Announcer >>
-  + on:do:for:
-+ Node >>
-  + navigationNodeAt:ifAbsent:
-+ BlockClosure >>
-  + tryCatch:
-+ Environment >>
-  + evaluate:for:
-+ AmberCli >>
-  + version:
-+ Object >>
-  + deprecatedAPI:
-- Environment >>
-  - eval:on:
-  - evaluateString:on:
-
-
-0.12.3:
-
-* Package Import-Export renamed to Kernel-ImportExport
-* A dozen of methods moved from Object to ProtoObject
-
-* HashedCollection >> at:ifAbsentPut: pushed up to SequenceableCollection
-* HashedCollection >> , is now allowed (removed shouldNotImplement)
-* HashedCollection and Dictionary both subclasses of AssociativeCollection
-* Smalltalk class moved to SmalltalkImage class, Smalltalk is now global var
-* Smalltalk current deprecated in favour of Smalltalk
-* Smalltalk at:[put:] deprecated in favour of Smalltalk globals at:[put:]
-* <smalltalk.ClassName> deprecated in favour of <globals.ClassName>
-
-+ CompiledMethod >>
-  + defaultProtocol
-+ Behavior >>
-  + compile:protocol:
-  + removeProtocolIfEmpty:
-+ Package >>
-  + load
-  + loadFromNamespace:
-+ Package class >>
-  + load:
-  + load:fromNamespace:
-+ PackageTransport >> load
-+ PackageHandler >> load:
-+ AmdPackageHandler >> load:
-+ Set >> removeAll
-+ AssociativeCollection class
-+ BucketStore class
-+ SmalltalkImage >>
-  + globals
-  + vm
-  + settings
-+ Setting class
-+ String >>
-  + asSetting
-  + asSettingIfAbsent:
-  + settingValue
-  + settingValueIfAbsent:
-  + settingValue:
-+ Smalltalk global variable
-
-- CompiledMethod >>
-  - category: (use #protocol:)
-  - defaultCategory
-- Behavior >> compile:category:
-- HTMLCanvas class >>
-  - browserVersion
-  - isMSIE
-  - isMozilla
-  - isOpera
-  - isWebkit
-
-
-0.12.2:
-
-* Collection >> contains: is deprecated in favor of anySatisfy:
-
-
-+ Announcer >> on:doOnce:
-+ String >>
-  + uriEncoded
-  + uriDecoded
-  + uriComponentEncoded
-  + uriComponentDecoded
-+ Collection >>
-  + removeAll
-  + ifEmpty:ifNotEmpty:
-  + ifNotEmpty:ifEmpty:
-  + anyOne
-  + noneSatisfy:
-  + anySatisfy:
-  + allSatisfy:
-
-
-0.12.0:
-
-* SmalltalkMethodContext.prototype.fillBlock() takes a third 'index' parameter
-* Existing classes moved to new KernelInfrastructure package
-* ImporterExporter
-  * are now StreamExporters
-  * aware of AMD namespaces
-  * support transport types and commit channels
-
-
-+ Node >>
-  + nextChild
-  + method
-  + postCopy
-  + isCascadeNode
-  + isLastChild
-+ BlockNode >>
-  + nextNode:
-  + nextChild
-+ SendNode >>
-  + isCascadeSendNode
-  + shouldBeAliased
-+ CompiledMethod >> sendTo:arguments:
-+ Array >>
-  + addFirst:
-  + removeLast
-+ Number >>
-  + ceiling
-  + floor
-  + asNumber
-  + //
-  + cos
-  + sin
-  + tan
-  + arcCos
-  + arcSin
-  + arcTan
-  + log
-  + log:
-  + raisedTo:
-  + sign
-  + **
-  + ln
-  + e
-+ String class >> esc
-+ String >>
-  + asMutator
-  + capitalized
-  + isCapitalized
-+ JSProxy >> printString
-+ Behavior >>
-  + ownProtocols
-  + ownMethods
-+ JSStream >> nextPutSendIndexFor:
-+ InterfacingObject class
-+ Interpreter class
-+ DocumentFragmentTag class
-+ AbstractExporter class
-+ PlatformInterface class
-
-
-- Node >> extent
-- JSStream >> nextPutStatement:with:
-- Smalltalk.installSuperclass()
-- ClassReferenceNode class (now handled via VariableNode)
-
-
-0.11.0:
-
-* AnnouncementSubscription use #valuable: instead of #block: (deprecated)
-* AbstractCodeGenerator inherits from Object, not NodeVisitor
-* Object>>printString
-* replace >>printString with >>printOn:
-* replace >>storeString with >>printString
-* PackageLoader is now PackageHandler (>>commit: >>setupPackagenamed:prefix: >>ajaxPutAt:data:
-* Package>>fetch: is now Package>>load:
-* Package>>fetch:prefix: is now Package>>load:prefix:
-* Queue>>front replaced by Queue>>next
-* Queue>>frontIfAbsent: replaced by Queue>>nextIfAbsent:
-* Queue>>back: replaced by Queue>>nextPut:
-* smalltalk.addMethod() does not use explicit JS selector
-* JSObjectProxy>>canForwardMessage: replaced by use of JSObjectProxy>>lookupProperty: with asJavaScriptSelector
-* JSObjectProxy>>forwardMessage: replaced by explicit JSObjectProxy>>forwardMessage:withArguments:
-* String>>asJavaScriptSelector moved to Kernel-Objects package
-
-+ Object>>asString
-+ Object>>putOn:
-+ String>>isVowel
-+ Collection>>putOn:
-+ CharacterArray>>putOn:
-+ Stream>><<
-+ Stream>>write
-+ SequenceableCollection>>newStream
-+ SequenceableCollection>>readStream
-+ SequenceableCollection>>stream
-+ SequenceableCollection>>streamClass
-+ SequenceableCollection>>writeStream
-+ Collection>>isImmutable
-+ Stream>>nextPutString:
-+ StringStream>>nextPutString:
-+ JSStream>>nextPutClassRefFunction:
-+ String>>crlfSanitized
-+ inlined Block now also responds to >>value:
-+ Parser: split literal into runtimeLiteral and parseTimeLiteral
-+ Parser: write #(4 #(5 6 #()) 7) as #(4 (5 6 ()) 7)
-+ Parser: write #(#on:do: #Object) as #(on:do: Object)
-+ Parser: Symbols for binarie selectores
-+ Package>>commit
-+ AIContext>>initializeLocals
-+ ASTInterpreter>>withBlockContext:
-+ smalltalk.allSelectors()
-+ Object>>isCompiledMethod
-+ Object>>isPackage
-+ Object>>isBehavior
-+ ClassMoved Announcemen class
-+ Behavior>>includesBehavior:
-+ Environment>>classes
-+ Environment>>allSelectors
-+ Environment>>removeProtocol:
-+ Environment>>renameProtocol:to:in:
-+ CompiledMethod>>protocol:
-+ Smalltalk>>globalJsVariables
-+ Smalltalk>>addGlobalJsVariable:
-+ Smalltalk>>deleteGlobalJsVariable:
-
-
-- Object>>storeOn:
-- Object>>log:block:
-- Object>>printNl
-- Compiler-IR.st >>javascriptSelector
-- Compiler-IR.st >>nextPutVar:
-- Kernel-Collections.st >>asSuperSelector
-- Collection>>readStream
-- Collection>>stream
-- Collection>>streamClass
-- Collection>>writeStream
-- Symbol class (replaced with String)
-- IRInlinedNonLocalReturn class
-- IRInlinedSend>>nonLocalReturnInliner
-- IRNonLocalReturnInliner class
-- Package>>dependencies
-- Package>>dependencies:
-- Package>>properties
-- Package>>jsProperties
-- Package>>jsProperties:
-- Package>>propertiesAsJSON
-- Package>>propertyAt:
-- Package>>propertyAt:ifAbsent:
-- Package>>propertyAt:put:
-- Browser>>ajaxPutAt:data:

CHANGELOG

@@ -1,314 +1,22 @@
-11th April 2014 - Release 0.12.4
+XXth XXX 2014 - Release 0.1.0
 ===================================
 
 Highlights:
 
-* Fixed backward compatibility for pre-0.12.3 loader syntax.
-* `namespace/_source` is not needed to map and is recommended
-  not to use; `.st` files are by default committed to the `.js` location.
-* All sources, including js files into the src/ directory
-* Many improvements in Helios, especially in its debugger and
-  inspector, as well as UI-related improvements
-* New Helios dark theme by @BenjaminVanRyseghem
+* Package is polished.
+* `amber-cli` is now official package to install globally.
 
-Commits: https://github.com/amber-smalltalk/amber/compare/0.12.3...0.12.4
-Issues:  https://github.com/amber-smalltalk/amber/issues?milestone=12&state=closed
+Commits: https://github.com/amber-smalltalk/amber-cli/compare/0.0.4...0.1.0
+Issues:  https://github.com/amber-smalltalk/amber-cli/issues?milestone=2&state=closed
 
-For the most important API related changes see the file API-CHANGES.txt.
 
-
-22nd Jan 2014 - Release 0.12.3
-===================================
-
-Highlights:
-
-* JQuery updated to ~1.10.2; jquery-ui updated to match
-* Subclasses of `nil` can be created
-* Several fixes for IE8
-* amber.js can be loaded asynchronously (it must
-  have an id 'amber-path-mapper' in that case)
-* CodeMirror updated to ~3.20.0
-
-Commits: https://github.com/amber-smalltalk/amber/compare/0.12.2...0.12.3
-Issues:  https://github.com/amber-smalltalk/amber/issues?milestone=11&state=closed
-
-For the most important API related changes see the file API-CHANGES.txt.
-
-
-03rd December 2013 - Release 0.12.2
+14th April 2014 - Release 0.0.4
 ===================================
 
 Highlights:
 
-* Loading Amber in nested pages now possible (via additional `data-libs` attribute of the `<script>` tag which loads `amber.js`)
-* IDE related fixes
-* Contributions Guide
-* Improved Collections
-* Amber Server responds with `not found` instead of `internal server error` if `index.html` could not be found
-
-Commits: https://github.com/amber-smalltalk/amber/compare/0.12.1...0.12.2
-Issues:  https://github.com/amber-smalltalk/amber/issues?milestone=10&state=closed
-
-For the most important API related changes see the file API-CHANGES.txt.
-
-
-14th November 2013 - Release 0.12.1
-===================================
-
-Fixes a bug in Helios preventing class definitions from being compiled
-
-Commits: https://github.com/amber-smalltalk/amber/compare/0.12.0...0.12.1
-Issues:  https://github.com/amber-smalltalk/amber/issues?milestone=9&state=closed
-
-
-11th November 2013 - Release 0.12.0
-===================================
-
-After 3 months of work we are pleased to announce the 0.12.0 release of Amber.
-
-Besides the usual bug fixes a lot of new features have emerged.
-
-The biggest change is the switch to RequireJS to specify Amber package dependencies
-and for loading the packages as AMD modules.
-Amber is now additionally available as Bower [2] component.
-Bower is also used to manage required JavaScript libraries which don't have to be kept
-around in the repository anymore.
-
-The repository layout was restructured to provide a cleaner separation of different Amber parts:
-* Smalltalk code is located in 'st'
-* Compiled Amber packages are located in 'js'
-* Supporting JavaScript code is located in 'support'
-
-Together with the RequireJS changes the specifying their dependencies the Brickz [3]
-reconfigurable micro composition system was introduced.
-This is used for
-
-On the Smalltalk side support has been added for writing exponential numbers of the form 2e5.
-
-Helios (the new IDE) is progressing nicely and has seen a lot of improvements.
-One of the great parts is the new stepping debugger which is also making progress.
-To try Helios, open the helios.html page or
-evaluate in any other amber page `require('amber/helpers').popupHelios()`.
-
-The last enhancements target the commandline compiler which can be used as
-`amberc` (an executable script) or as a Grunt task.
-The following features have been added:
- * generation of shebang line (#!/usr/bin/env node)
- * specification of target namespace (`-n` flag; `amd_namespace` option in Grunt)
- * specification of additional library directories (`-L` flag; `library_dirs` option in Grunt)
-The following features have been removed:
- * creation of *.deploy.js files (`-d` flag; `deploy` option in Grunt)
- * optimization passes via Closure compiler (`-o`/`-O` flags; `closure_jar` option in Grunt)
-   The same behavior can be achieved by using specific Grunt tasks
-
-Additionally, the Grunt task now handles the -v/--verbose flag which triggers the same behavior
-as the `verbose` option which can be specified in the Gruntfile.
-
-
-Some numbers about this release (starting from 0.11.0):
-
-* 660 commits
-* 10 committers
-* 66 unit tests added
-* 152 issues were closed
-* 379 unit tests in total
-
-
-Commits: https://github.com/amber-smalltalk/amber/compare/0.11.0...0.12.0
-Issues: https://github.com/amber-smalltalk/amber/issues?direction=desc&milestone=8&page=1&sort=updated&state=closed
-
-For the most important API related changes see the file API-CHANGES.txt.
-
-
-* Installing Amber from NPM
-
-To install Amber from NPM, run
-
-    npm install amber
-
-* Installing Amber from Bower
-
-To install Amber from Bower, run
-
-    bower install amber
-
-* Migration from Amber 0.11.0
-
-First, the loading of JavaScript files must be adapted. The custom loader has been replaced with
-requirejs for loading files in the browser. New loader code is thouroughly
-explained in [4].
-
-After updating the loader part, `.st` files need to be recompiled
-into new AMD `.js` files. During loader changes, a namespace was choosen and will be needed for recompilation.
-
-Go to your directory with `.st` files and issue this from the shell:
-
-```sh
-<path-to-amber>/bin/amberc -l SUnit,Canvas -n <chosen-namespace> -D <path-for-compiled-js-files> *.st
-```
-
-In windows, use `\` as path separator, the rest is identical.
-
-The `-l SUnit,Canvas` is just a general guess, if your code depends on more (or less) non-kernel packages from amber, list them here accordingly.
-
-This migrate scenario only covers simple deployments with your project's code and amber.
-If your project is more complicated, using libraries and packages from multiple sources,
-it is hard to give general advices to migrate - you must do it library by library,
-giving each location its own namespace, and `-L` option of `amberc`
-comes handy when integrating; ask on the mailing list if problems arise.
-
-[1] http://requirejs.org/
-[2] http://bower.io/
-[3] https://github.com/amber-smalltalk/brikz
-[4] https://github.com/amber-smalltalk/amber/wiki/How-to-load-amber
-
-
-09th July 2013 - Release 0.11.0
-===============================
-
-Three months have passed and we are happy to announce the release
-of Amber 0.11.0!
-
-Some numbers about this release:
-
-* 494 commits
-* 13 committers
-* increasing the number of core committers to 25
-* 50 unit tests added to the kernel
-* 313 unit tests in total
-
-Since the last release 60 issues were closed, bringing us to 499
-issues closed.
-
-This release includes a lot of bug fixes, improvements to the
-CLI, as well as a preview of the next IDE, named Helios. Amber
-now also uses a CI server [1].
-
-To try the Helios, the new IDE, open the helios.html page, or
-evaluate in any other amber page `amber.loadHelios()`.
-
-The compiler also received some improvements, especially
-regarding message send optimisations and super sends.
-
-Here's the list of commits and closed issues:
-https://github.com/amber-smalltalk/amber/compare/0.10.0...0.11.0
-https://github.com/amber-smalltalk/amber/issues?direction=desc&milestone=6&page=1&sort=updated&state=closed
-
-There is a lot more to come with Helios, a stepping debugger
-based on the AST is in progress and currently in the 'debugger'
-branch on GitHub.
-
-* Installing Amber from NPM
-
-To install amber from NPM, run
-
-    npm install amber
-
-
-* Migration from Amber 0.10.0
-
-Amber compiled code should be compatible with Amber 0.10.0, but
-recompiling is needed in order to get contexts working:
-
-    Compiler new recompile: (Package named: 'MyPackage') classes.
-    (Package named: 'MyPackage') commit
-
-For API related changes see the file API-CHANGES.txt.
-
-
-13th March 2013 - Release 0.10.0
-================================
-
-Here's a summary of change since the 0.9.1 release:
-
-- Travis CI jobs
-- Almost 300 issues closed
-- 150 new unit tests written
-- All classes in the Kernel are documented
-
-- New and much improved compiler toolchain, providing:
-  - Semantic analysis
-  - AST Node annotation
-  - Intermediate representation (easier to optimize)
-  - Better inlining
-  - an AST interpreter
-  - support for blocks contexts
-
-- New build system based on grunt.js, replacing the old makefiles
-- New bin/amberc compiler written in Amber/Node.js
-- SUnit improvements and cleanup, with support for async assertions
-- Improved ClassBuilder with better class migration support
-- Improved loader for third party packages
-- New: Announcements
-- Classes can be augmented by light-weight methods created from blocks
-- Snippets of HTML can be marked to become virtual tags in HTMLCanvas
-- Amber server supports Basic HTTP authentication (not recommended for production environments/unencrypted connections)
-- New IDE on it's way for Amber 1.0
-
-
-
-16th January 2012 - Release 0.9.1
-=================================
-
-Here's a summary of changes since the 0.9 release:
-
-- 80 new unit tests written
-- 52 issues fixed
-- All classes in Kernel-Objects, Kernel-Classes and Kernel-Methods has been documented
-- New documentation framework (see http://amber-lang.net/documentation.html)
-- Better class organisations, "Kernel" package split into several packages
-- First class packages have replaced class categories
-- Internet Explorer 7+ compatibility
-- New Announcement framework ported from Pharo
-- New console-based REPL written in Amber using node.js
-- Symbol class implemented together with object identity and #==
-- New OrderedCollection and Set implementation
-- Dictionary can now have any kind of object as keys. String-key dictionary has been renamed HashedCollection
-- New TwitterWall example
-- Improved HTML Canvas, now compatible with IE7
-- Improved JSObjectProxy for seamless JavaScript objects access from Amber
-- No more jQuery binding. Amber is fully capable of sending messages to JavaScript objects
-
-13th September 2011 - Release 0.9
-=================================
-Amber has been evolving furiously since the presentation at ESUG 2011 in Edinburgh less than 3 weeks ago.
-
-This is a summary:
-
-Language, compiler and runtime
-
-- New 100x faster parser built using PEGjs instead of the old parser built using PetitParser.
-- New much faster ChunkParser implementation in handwritten Amber instead of using PetitParser.
-- Improved parsing error report with quoted source code plus marker pinpointing parsing error.
-- Removed PetitParser since it is no longer needed by Amber itself.
-- Added compiler optimizations in the form of speculative inlining of specific messages and control structures.
-- Added support for dynamic Arrays, just like in Squeak/Pharo.
-- Added support for similar dynamic Dictionaries, not seen in other Smalltalks.
-- Added & and | as allowed binary selectors and implemented them in Boolean.
-- Added a Set implementation.
-- Added first basic support for real Packages with dependency information.
-
-...and various extensions, enhancements and bug fixes to the library classes.
-
-
-Development environment
-
-- A working Debugger with integrated inspector, proceed etc.
-- A new structure with
-- A working amberc command line compiler including a Makefile for recompiling the whole Amber.
-- Enabled TestRunner in the IDE for running unit tests based on SUnit.
-- Added "File in" button in Workspace to easily paste and filein source code in chunk format in the IDE.
-
-
-Example code and ports
-
-- Ported ProfStef interactive tutorial, available on Amber homepage but also in examples directory.
-- Included the ESUG presentation as an example also in the examples directory.
-- Several new examples running on Node.js and webOS included, all with Makefiles.
-
-
-Various other things
+* Amber tooling is now in its own package.
 
-- Issue tracker on github now used as primary source, closed a bunch of reported issues.
-- Wiki pages on github with information on how to port code from other Smalltalks, lists of articles, tutorials, roadmap and more.
+Commits: https://github.com/amber-smalltalk/amber-cli/compare/cc2a163...0.0.4
+Issues:  https://github.com/amber-smalltalk/amber-cli/issues?milestone=1&state=closed
 

CONTRIBUTING.md

@@ -10,7 +10,7 @@ Start Contributing by talking about Amber
 Filing Issues
 =============
 
-If you think Amber is not working as expected, You can start by asking on IRC or the Mailinglist.
+If you think Amber CLI is not working as expected, You can start by asking on IRC or the Mailinglist.
 Please make sure that you have first checked the following guides:
 
 * [Getting Started](https://github.com/amber-smalltalk/amber/wiki/Getting-started)
@@ -27,65 +27,25 @@ Additionally, you should give us enough information to reproduce the issue.
 Therefore, include versions of your OS, Amber, Node.js, Grunt, and possibly used libraries as well as sample code.
 If you don't list the exact steps required to reproduce the issue we won't be able to fix it.
 
-Afterwards, report the issue on one of the following trackers:
-
-* [Amber Issues](https://github.com/amber-smalltalk/amber/issues)
-* [Amber Examples Issues](https://github.com/amber-smalltalk/amber-examples/issues)
-* [Amber Website Issues](https://github.com/amber-smalltalk/amber-website/issues)
-
-
-Developing Amber
-================
-
-If you want to get started developing Amber itself there are a few links to get you started
-
-* [The Roadmap](https://github.com/amber-smalltalk/amber/wiki/Roadmap) gives a rough idea about where Amber is heading towards
-* [The Contributions Page](https://github.com/amber-smalltalk/amber/wiki/Contributions) contains some ideas which we would love to integrate into Amber
-* [The Amber FAQ](https://github.com/amber-smalltalk/amber/wiki/FAQ) contains Answers to commonly arising questions
-* [The Amber CookBook](https://github.com/amber-smalltalk/amber/wiki/Amber-cookbook) contains recipies about working with Amber and its IDE
-* [The Amber Porting Guide](https://github.com/amber-smalltalk/amber/wiki/Porting-code-from-other-Smalltalk-dialects) contains information about porting code from other Smalltalk dialects
-* [The Amber JavaScript Guide](https://github.com/amber-smalltalk/amber/wiki/From-smalltalk-to-javascript-and-back) contains information about how Amber and JavaScript are mapped to each other
-
-If you want to get serious with Amber development you should read the [Coding Conventions](https://github.com/amber-smalltalk/amber/wiki/Coding-conventions)
-and check if you have all development dependencies installed (as indicated in [Getting Started](https://github.com/amber-smalltalk/amber/wiki/Getting-started)):
-
-* Git (to get a clone of the repository)
-* Node.js (to run the Amber development server)
-* NPM (to install required Node.js packages)
-* Bower (to install required client side libraries)
-* Grunt-Cli (to compile Amber on the commandline)
-
- 
-Setup your Amber clone
-----------------------
-
-1. Create a fork of the repository on GitHub
-2. Clone the repository
-3. Run ```npm install```
-4. Run ```bower install``` (requires bower to be installed via ```npm install -g bower```)
-5. Run ```${Amber_DIR}/bin/amber serve```
-
-Now you should be able to commit changes to your computer.
-
 
 Creating a Pull Request
 -----------------------
 
 The Amber development model currently revolves around Pull Requests which are created through GitHub
 
-1. Update to latest Amber master (```git pull```)
+1. Update to latest Amber CLI master (```git pull```)
 2. Develop your feature or bugfix in a local branch (not in ```master```)
 3. Create unittest for your feature or bugfix (your feature/fix will be integrated a lot faster if unittests are present)
 4. Enhance/fix Amber
 5. Run the unittests
 6. Commit your changes to disk if all tests are green
 7. Try to split your fix into small Git commits if multiple changes are involved (this makes it easier for us to review the changes)
-8. If you created / deleted / moved API, update API-CHANGES.txt appropriately and commit.
+8. If you created / deleted / moved something significant, update CHANGELOG appropriately and commit.
 8. Push the changes to your fork on GitHub ```git push <your repo> <your branchname>```
-9. Submit Pull Request (usually for the Amber master branch)
+9. Submit Pull Request (usually for the Amber CLI master branch)
 
 
-Compiling Amber with Grunt
+Compiling Amber CLI with Grunt
 --------------------------
 
 Amber uses [Grunt.js](http://gruntjs.com/) as build system since version `0.10.0`.
@@ -95,9 +55,9 @@ To install Grunt.js v0.4.x on the commandline execute the following commands:
     npm install -g grunt-cli
 
 Make sure that you have installed all required dependencies via `npm` and `bower`.
-Then you can finally compile Amber using the following command:
+Then you can finally compile Amber CLI using the following command:
 
     cd ${Amber_DIR}
-    grunt
+    grunt amberc:amber_cli
 
 For Windows support check the [Grunt.js on Windows](http://gruntjs.com/frequently-asked-questions#does-grunt-work-on-windows) page.

RELEASING.md

@@ -3,16 +3,13 @@ Release Guide for Amber
 
 The following steps are required to make a release of Amber:
 
-1. check that all tests are green
-2. check that the examples are up-to-date
-3. check that `API-CHANGES.txt` is up-to-date; remove the 'work in progress' from version
-4. check the `CHANGELOG` file and update the release notes, check the milestone index in issues link
-5. log in to npm with write access for the Amber package
-6. execute `cli/support/release.sh`
-7. answer the question about the version number used for the release
-8. answer the question about the version number for the upcoming release
-9. merge the created tag into the `stable` branch
-10. update the homepage to point to the latest tag on GitHub
-11. send announcement to mailinglists (Amber, Pharo, what else?)
-12. send announcement on Twitter
-13. send announcement on G+
+1. (not yet) check that all tests are green
+1. check the `CHANGELOG` file and update the release notes, check the milestone index in issues link
+1. bump version and git repo tag in `package.json`
+1. Create a tag for bumped version:`git tag -a 1.2.3 -m "Version 1.2.3`
+1. `git commit -a -m "Release 1.2.3" && git push && git push --tags`
+1. log in to npm with write access for the Amber package
+1. update the homepage to point to the latest tag on GitHub
+1. send announcement to mailinglists (Amber, Pharo, what else?)
+1. send announcement on Twitter
+1. send announcement on G+