Dev Snapshot release

Printer-friendlySend via EmailPDF Convert

I've been working on a plan for splitting dev from production all week. I have everything figured out. I've branched off the 1.2.rc4 branch as the production release, while everything that was released as 1.2.rc5 will be re-released as a "development" snapshot, with all the latest and greatest fixes and improvements.

I am almost ready to make the dev snapshot, with the fixes to Http protocol and analyzer. Just wanted to throw this out there, that this will be the first release coming, using the new development/release model. I'm also putting up some documentation on goals, schedule and milestones. The analyzer is really a major feature that is also a milestone in jNetPcap's evolution and this next release, with the fixes, will be released as a "dev" milestone release. Something like:

Updated: changed the dev snapshot name convention. Checkout the docs on how the name is built

jnetpcap-1.3.b0001-milestone1

As to the production release. The 1.2.rc4 extraction is a bit tricky because some of the bug fixes happened after the analyzer part was added in, and even newer bugs were fixed after release of 1.2.rc5. It may actually be easier to base this on rc5 and remove the analyzer portions. I'm trying to figure exactly how to do it now. As a recap the production release will revert back to "alpha" status:

jnetpcap-1.2.alpha1

The currently released packages on SF.net distribution server will be deprecated and archived away (not removed). While the newly released packages will be released under "jNetPcap->Version 1.2 - Preview" release group and dev release will be under "Dev Snapshot->Q1 2009" package and the SF.net release group.

In the alpha1 release, only very minor changes will be allowed and once all of the bugs are fixed and tested, we will advance to jnetpcap-1.2.beta1 and eventually to "stable" jnetpcap-1.2. I suspect that we will be in alpha mode for a while, as still large portions of the decoder haven't been thoroughly tested yet, although obviously its working and pretty stable. In order to advance it to "stable" state, it will take a lot more than just "working" and "pretty stable".