We're preparing for the first final release of Arquillian, 1.0.0.Final! (Hmm, perhaps I should have warned you to sit down first if that caused you to faint). This release showcases the dedicated work of many people and we want to be sure you're all a part of it.

We're also planning to have an after release party. We've been having a lot of fun lately with Google Hangout (and it's open source equivalent BigBlueButton). We need to decide when and where, make sure you have the food or drink you enjoy most in hand and we can have fun chatting about the past, present and future of Arqullian.

Yep, that just keeps hitting us. There is possibility of daisy chaining the hangouts...I might give that a few minutes of trail and error this weekend. Another approach is to get the BigBlueButton virtual machine running somewhere we can all connect to. If the VM really does run out of the box, then anyone with a decent network connection should be able to host it for the event. Again, something to play with, but not spend too much time on.

Quick update. I have reached out to all the contacts on the media list and heard back. All positive. The ball is now in our court to get them an announcement to post. I'll be working on that with Sarah. They are also interested in links to any and all blogs releated to the release, so start thinking about what you want to write.

That came up during my review of the docs yesterday. Currently the section is just a pointer to somewhere else. I'm inclined to remove the section--perhaps make it an FAQ--until it has worthwhile content (so as not to mislead the reader). I don't think it's a blocker for the release, but something we should have within a week or two after. The first step is to create an issue if there isn't already one, then try to get volunteers to write it up.

Of course, it can build on what I put together in the showcase. But there are also reports in the forums of people getting it working that might want to write it up:

My overall goal is to trim, trim, trim. There is a lot of non-normative (background) documentation that is aging, repeated elsewhere and not needed in the reference guide. I plan to save the good bits for the website or a consolidated section, and nuke the rest. The sections that will remain mostly intact are those that begin with "Complete " ...since they are the actual reference.

Here's the outline I'm shooting for:

Introduction

Super brief intro statement

Integration testing in Java EE (motivation)

How it works?

Architecture

Getting Started

One sentence explanation and link to guides on arquillian.org (the menu item is there to draw attention to the existence of the guides)

Containers

Super brief intro of what we mean by containers & the role they play

Container selection

Container configuration

Supported containers

Additional features (currently "Advance use cases")

Method injection (new)

Run modes

Descriptor deployment

ArquillianResource injection

Multiple deployments

Multiple containers

Protocol selection

Extensions

Drone

Seam 2

Performance

Appendix

Test enrichers (the purpose of this section is just some "important things to know about a few test enrichers)

EJB

CDI

Scopes

Containers

(current list as is)

Protocols

(current list as is)

Build integration

Maven (mostly just a statement that it's the preferred approach)

Ant+Ivy <- only if it's ready in time

Gradle

No dep management <- only if it's ready in time

I don't plan to write much new material...only revise and cut.

The "test execution" section I'm going to remove and turn into a guide for the website. The JSFUnit section just needs to be killed because it's misleading and sends the user on a wild goose chase. When I'm done, it should be much easier to manage and also more clear how we can automate most of it in the not to distant future.