Michael Blow created ASTERIXDB-2359:
---------------------------------------
Summary: Need releases defined in jira for next release, backlogs
Key: ASTERIXDB-2359
URL: https://issues.apache.org/jira/browse/ASTERIXDB-2359
Project: Apache AsterixDB
Issue Type: Task
Reporter: Michael Blow
Assignee: Till
Currently only 0.9.3 and 0.9.4 releases are defined in jira. We need some way
of targeting fixes for the backlog, as well as to future releases.
We could use _.next_ as a placeholder version, if we don't want to preallocate
version numbers. We could bulk update all .next targeted issues after each
release.
An orthogonal thought, should we use a scheme like <asterix version>/<hyracks
version> (e.g. 0.9.4/0.3.4) to make the *DB -> Hyracks version mapping less
magical?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
