I added "First stable release" in JIRA as a version identifier a while back, to avoid any prejudice what that version might be called. I think it makes sense to resolve (newly fixed) issues against that version. Once we finalize the name of that release, we can easily rename it to either "1.0.0" or "2.0.0".
I'd probably suggest to keep the 0.7.0-SNAPSHOT in the code until it is completely clear that the next release is 1.0.0 or 2.0.0. It is easy to bump the version upward -- typically things continue working well. If the version has to be adjusted downward for some reason, it gets tricky since Maven version ordering breaks for the nightly build. This is a good change, just no reason to rush it in, I think. On Thu, Mar 9, 2017 at 8:39 AM, Amit Sela <amitsel...@gmail.com> wrote: > Well, for now at least. We have to use something for fixed issues.. > > On Thu, Mar 9, 2017 at 6:32 PM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > By the way, waiting the end of this discussion, we can use "First stable > > release" as version in Jira. > > > > Regards > > JB > > > > On 03/09/2017 07:21 AM, Jean-Baptiste Onofré wrote: > > > Hi all, > > > > > > Release branch for 0.6.0 has been created but the next cycle version > has > > > not been created in Jira. > > > > > > I propose to create 2.0.0 version in Jira (it's always possible to > > > rename the version later). > > > > > > No objection ? > > > > > > Thanks > > > Regards > > > JB > > > > -- > > Jean-Baptiste Onofré > > jbono...@apache.org > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > >
