The simplest thing for the community is to have a single branch of
development that is being supported/maintained.  Otherwise we're always
forward/backporting new features that apply to both versions which is a
pain.  I do think we should push a 3.x branch so we can always do a future
3.2.13 release if requested by the community.  Then someone should bump
master to 4.0.0-SNAPSHOT, and then we should pull in PR 245.

There have been a couple commits on master since the 3.2.12 release.  Do we
want to cut a 3.2.13 release with just those remaining commits, or should
they all get rolled into the 4.0.0 release?



On Mon, Apr 9, 2018 at 12:30 PM, Chilton, Kevin <[email protected]>
wrote:

> Hey Rya devs,
>
> I'd like to get PR #245 (RYA-405) pulled in.  This is a pretty big
> dependency change, and should probably involve a major version increment to
> 4.0.0.  Could we get a discussion going on the devlist about if we want to
> support a 3.x branch and a 4.x branch going forward, or just update master
> to 4.x.
>
> Thanks,
> Kevin
>
> NOTICE: This email message and all attachments transmitted with it may
> contain privileged and confidential information, and information that is
> protected by, and proprietary to, Parsons Corporation, and is intended
> solely for the use of the addressee for the specific purpose set forth in
> this communication. If the reader of this message is not the intended
> recipient, you are hereby notified that any reading, dissemination,
> distribution, copying, or other use of this message or its attachments is
> strictly prohibited, and you should delete this message and all copies and
> backups thereof. The recipient may not further distribute or use any of the
> information contained herein without the express written authorization of
> the sender. If you have received this message in error, or if you have any
> questions regarding the use of the proprietary information contained
> therein, please contact the sender of this message immediately, and the
> sender will provide you with further instructions.
>

Reply via email to