search

WASdev / standards.jsr352.jbatch

Home of 'jbatch', a compatible implementation of the Jakarta Batch specification (and the former Reference Implementation for the JSR 352, Batch Applications for the Java Platform specification).
Other
21 stars 18 forks source link

Branch for next version of spec #22

Closed scottkurz closed 9 years ago

scottkurz commented 9 years ago

@BrentDouglas @smillidge @kmukherjee

Soliciting opinions here..

As we kick off the next version of the spec (1.1?), I was planning on branching off the 1.0 work.

Since it's only me directly pushing, I was thinking of something extremely simple.. just branching off a new '1.0' branch (or '1.0.x' perhaps) for the ongoing 1.0 work and declaring that 'master' will be used for the next spec version.

Any comments?

I tried to find some real simple precedent but most articles deal with much more complicated scenarios with many people contributing and I couldn't see what we'd gain from that.

Thanks

BrentDouglas commented 9 years ago

I like it. A 1.0.X branch after the 1.0 tag is a pretty common way to manage things. e.g. https://github.com/infinispan/infinispan/branches

smillidge commented 9 years ago

If I've got this right. Master will host development on the next spec release and a 1.0.tag + a 1.0.1 branch for maintenance releases?

+1 for that.

We do that for Payara and we also don't allow any direct pushing to master. All developers must fork onto their local github account, do development there and then raise pull requests to update master.

scottkurz commented 9 years ago

OK, since the project holds the RI and TCK and since in this case I'm working on updating the impl-side of the RI (to 1.0.1) separately from the API (I recall these are just Javadoc).

So I just pushed two tags: api-1.0, impl-1.0.

And probably will wait to start the 1.0.x branch until the GF testing of 1.0.1 is complete.

Thanks for the feedback,