GA release for April 2013

[sskhiri]

Objective

We have been incubating RoQ for a little bit more than 1 year, it is time now to have our first 1.0 GA version.
This version will be just a subset of the core stable features.

Features of the GA

• Static event message queue: a user can manually add host and exchanges and the system will use them to balance the load, but this will not be automatic in the 1.0 GA?
• No management console, just the script released for testing and perhaps the CLI developed by Jehan (TBD).

Actions to be taken

1. Testing static behavior as described in task Checking the static behavior #117 @sskhiri
2. Adding a job on the CI for the master branch (not need to have a nightly build just a manual one) @jbruggem
3. Updating the GimmeRoQ.sh for integrating the Release build from the CI (2)
4. Re-Write a simplified version of the Readme.MD and adding the documentation on the CLI that can be found on the back-end @sskhiri
5. Packaging the CLI with the backend in nice way @jbruggem
6. Find an agreement on the release process: tag? branch?

Finally, if we can go forward with the management console it would be great. We need to take technology decision asap on that point.

[jbruggem]

Additional note: Rather than removing what's in README.md, we should move README.md to INSTALL.md, write a simpler README.md and reference INSTALL.md in README.md (as "manual install" link).

[cduverne]

Release name proposal : Marina !!!!!!

[sskhiri]

@jbruggem as soon as the issue #122 is finished @cduverne will be able to update and test its issue #121. Thank you !!

[sskhiri]

@jbruggem do you want to include the roq-backend in the first release ?

[jbruggem]

Yes, I think it's worth it. The CLI works pretty well and the REST API is clean.

[sskhiri]

OK good! Can you check if you it is well updated with the ZMQ 3.X and that the GimmeRoQ.sh will well install it. @cduverne were mentioning issues whith NPM. Can you check and confirm ?

Then, the only thing I will do is writing a short wiki page about launching and usage of the backend CLI. Therefore, I can officially close the ticket.

[sskhiri]

OK good! Can you check if you it is well updated with the ZMQ 3.X and that the GimmeRoQ.sh will well install it. @cduverne were mentioning issues whith NPM. Can you check and confirm ?

Then, the only thing I will do is writing a short wiki page about launching and usage of the backend CLI. Therefore, I can officially close the ticket.

[Majea]

This week I've put my hands on backbone.js. It's pretty nice for organizing
your code but it won't help for having a UI that looks nice. Like all
frameworks I've seen until now, it doesn't support complex models with
multiple references to a single object. But I don't think it's a common
use-case for management UIs. So I guess we don't need that feature here and
we can adopt backbone for MVC implementation.
Still, other UI libs have to be investigated to improve the look of the
console.

Max

On Thu, Mar 28, 2013 at 2:40 PM, Sabri Skhiri notifications@github.comwrote:

OK good! Can you check if you it is well updated with the ZMQ 3.X and that
the GimmeRoQ.sh will well install it. @cduvernehttps://github.com/cduvernewere mentioning issues whith NPM. Can you check and confirm ?

Then, the only thing I will do is writing a short wiki page about
launching and usage of the backend CLI. Therefore, I can officially close
the ticket.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/119#issuecomment-15588717
.

[jbruggem]

@Majea, you're a bit out of topic there :).

@sskhiri indeed, the backend should be updated to fix dependency problems. it's in my TODO.

@sskhiri may I remind you that the doc exists, now :)
See:
main page
CLI manual
API manual
Internal architecture

[sskhiri]

Status of this task

DONE

1. Testing static behavior as described in task Checking the static behavior #117. This has shown few important bugs that made the exchange static wrong and the re-location fail. Now that's working fine!
2. Adding a job on the CI for the master branch
3. Updating the GimmeRoQ.sh for integrating the Release build from the CI (2)
4. Re-Write a simplified version of the Readme.MD and adding the documentation on the CLI that can be found on the back-end

Still TODO or need to be closed

1. The tagging policy on developer handbook
2. Issues Update GimmeRoQ.sh with stable build #121 Contact BeJuG for RoQ Presentation #124 Update Developer Handbook: Release on master #125
3. Update of the Backend and CLI + Validation for ZMQ 3.0 @jbruggem
4. The new management console in JAVA @Majea

[sskhiri]

@jbruggem still working on #125.

[sskhiri]

New GA objective

Date: March 1 2014
Content:
We need to provide:

• The new chef recipe installation with its guide @jbruggem
• The upgrade of the CLI with ZMQ 3.X @jbruggem
• Global validation of the installation @sskhiri