-
-
Notifications
You must be signed in to change notification settings - Fork 748
For Committers
Jeanfrancois Arcand edited this page Mar 9, 2015
·
11 revisions
- 2.0.x: JeanFrançois Arcand
- 2.1.x: Sebastian Lövdahl
- 2.2.x: Aki Yoshida
- 2.3.x: JeanFrançois Arcand
First, send an email to the mailing list asking the community to test current SNAPSHOT if it's a dot dot release (2.2.x), or an RC if it's a major release (2.x). Give the community 24 hours.
If you release atmosphere-runtime
, please make sure you also release atmosphere-samples
with this new version.
Send an email to the mailing list describing which module/project has been released: Atmosphere, NettoSphere, atmosphere-samples, etc with their respective changelog. The changelog can be generated using the issues labelled for that release.
- Each README.md of each project needs to be updated, including the changelog section.
-
script/javadoc.sh
must be run to update the Javadoc
- All commits on dot dot branches MUST have an associated issue.
- Consider starting the commit message with an applicable emoji:
- 💄
:lipstick:
when improving the format/structure of the code - 🐎
:racehorse:
when improving performance - 🚱
:non-potable_water:
when plugging memory leaks - 📝
:memo:
when writing docs - 🐧
:penguin:
when fixing something on Linux - 🍎
:apple:
when fixing something on Mac OS - 🏁
:checkered_flag:
when fixing something on Windows - 🐛
:bug:
when fixing a bug - 🔥
:fire:
when removing code or files - 💚
:green_heart:
when fixing the CI build - ✅
:white_check_mark:
when adding tests - 🔒
:lock:
when dealing with security - ⬆️
:arrow_up:
when upgrading dependencies - ⬇️
:arrow_down:
when downgrading dependencies
- 💄
- Understanding Atmosphere
- Understanding @ManagedService
- Using javax.inject.Inject and javax.inject.PostConstruct annotation
- Understanding Atmosphere's Annotation
- Understanding AtmosphereResource
- Understanding AtmosphereHandler
- Understanding WebSocketHandler
- Understanding Broadcaster
- Understanding BroadcasterCache
- Understanding Meteor
- Understanding BroadcastFilter
- Understanding Atmosphere's Events Listeners
- Understanding AtmosphereInterceptor
- Configuring Atmosphere for Performance
- Understanding JavaScript functions
- Understanding AtmosphereResourceSession
- Improving Performance by using the PoolableBroadcasterFactory
- Using Atmosphere Jersey API
- Using Meteor API
- Using AtmosphereHandler API
- Using Socket.IO
- Using GWT
- Writing HTML5 Server-Sent Events
- Using STOMP protocol
- Streaming WebSocket messages
- Configuring Atmosphere's Classes Creation and Injection
- Using AtmosphereInterceptor to customize Atmosphere Framework
- Writing WebSocket sub protocol
- Configuring Atmosphere for the Cloud
- Injecting Atmosphere's Components in Jersey
- Sharing connection between Browser's windows and tabs
- Understanding AtmosphereResourceSession
- Manage installed services
- Server Side: javadoc API
- Server Side: atmosphere.xml and web.xml configuration
- Client Side: atmosphere.js API