Cascading 1.1 User Guide Draft

2 views
Skip to first unread message

Chris K Wensel

unread,
Mar 8, 2010, 12:05:09 PM3/8/10
to cascadi...@googlegroups.com
Hey all

Uploaded a draft of the 1.1 user guide last night. It can be found here:
http://www.cascading.org/documentation/userguide.html

Please take a look and send me comments.

Also WIP 1.1 is roughly feature complete. Still some logistic and packaging issues before I issue a Release Candidate.
http://www.cascading.org/downloads.html

cheers,
chris

--
Chris K Wensel
ch...@concurrentinc.com
http://www.concurrentinc.com

Ken Krugler

unread,
Mar 11, 2010, 1:51:17 PM3/11/10
to cascadi...@googlegroups.com

On Mar 8, 2010, at 9:05am, Chris K Wensel wrote:

> Hey all
>
> Uploaded a draft of the 1.1 user guide last night. It can be found
> here:
> http://www.cascading.org/documentation/userguide.html
>
> Please take a look and send me comments.

I'll spend some time today reading through the User Guide.

> Also WIP 1.1 is roughly feature complete. Still some logistic and
> packaging issues before I issue a Release Candidate.
> http://www.cascading.org/downloads.html

It would be nice if the naming convention for the jars could be
changed to be Maven-compatible, ie

cascading-(core|test)-<version>[-<build>].jar

e.g.

cascading-core-1.1-WIP-116.jar

Thanks,

-- Ken

--------------------------------------------
Ken Krugler
+1 530-210-6378
http://bixolabs.com
e l a s t i c w e b m i n i n g


Chris K Wensel

unread,
Mar 12, 2010, 1:34:44 PM3/12/10
to cascadi...@googlegroups.com
Sounds good. Will work on that this weekend.

ckw

> --
> You received this message because you are subscribed to the Google Groups "cascading-user" group.
> To post to this group, send email to cascadi...@googlegroups.com.
> To unsubscribe from this group, send email to cascading-use...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cascading-user?hl=en.

Chris K Wensel

unread,
Mar 12, 2010, 4:02:01 PM3/12/10
to cascadi...@googlegroups.com

ok, how's this?

for major version pre-release builds
> cascading-core-1.2-wip-<build-num>.jar

for pre-release maintenance builds
> cascading-core-1.1.0-wip-12345.jar

for final maintenance builds
> cascading-core-1.1.0.jar

ckw

On Mar 11, 2010, at 10:51 AM, Ken Krugler wrote:

> --
> You received this message because you are subscribed to the Google Groups "cascading-user" group.
> To post to this group, send email to cascadi...@googlegroups.com.
> To unsubscribe from this group, send email to cascading-use...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cascading-user?hl=en.
>

--

Nick Dimiduk

unread,
Mar 12, 2010, 4:07:19 PM3/12/10
to cascadi...@googlegroups.com
I think you want your build numbers to be consistent between all types of releases - always have the full x.y.z in cascading-[component]-x.y.z.

Check out http://semver.org/ for "the right way".

Chris K Wensel

unread,
Mar 12, 2010, 4:21:52 PM3/12/10
to cascadi...@googlegroups.com
well, wips aren't releases. but alpha/beta works in progress (think of them as nightlies)  and won't be available from the community site directly to prevent confusion.

some projects may need to rely on the wip, but it makes sense they are clearly marked as such (wip-bbbb).

only public releases avail via the community site will have x.y.z versioning at the package and jar levels.

should that work?

ckw
Reply all
Reply to author
Forward
0 new messages