You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Till (JIRA)" <ji...@apache.org> on 2019/04/10 18:35:00 UTC
[jira] [Resolved] (ASTERIXDB-2359) Need releases defined in jira
for next release, backlogs
[ https://issues.apache.org/jira/browse/ASTERIXDB-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till resolved ASTERIXDB-2359.
-----------------------------
Resolution: Done
> 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
> Priority: Major
>
> 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)