You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Stefano Bagnara (JIRA)" <se...@james.apache.org> on 2007/09/03 01:51:19 UTC
[jira] Created: (JAMES-812) Fix JIRA versions. next-minor and
next-major do not have anymore meaning.
Fix JIRA versions. next-minor and next-major do not have anymore meaning.
-------------------------------------------------------------------------
Key: JAMES-812
URL: https://issues.apache.org/jira/browse/JAMES-812
Project: James
Issue Type: Task
Affects Versions: Next Minor, Next Major, Trunk
Reporter: Stefano Bagnara
Fix For: Next Minor, Next Major, Trunk
Since we voted to rename the version from next-major to 3.0-SNAPSHOT the JIRA version should be updated according to that vote.
next-minor and next-major should be removed forever as the vote where they was introduced has been "invalidated".
Please fix this: mixing old and new names is even worse than not having a name/version at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (JAMES-812) Fix JIRA versions. next-minor and
next-major do not have anymore meaning.
Posted by "Danny Angus (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Danny Angus resolved JAMES-812.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: Trunk)
Merged next-minor with 2.3.2
> Fix JIRA versions. next-minor and next-major do not have anymore meaning.
> -------------------------------------------------------------------------
>
> Key: JAMES-812
> URL: https://issues.apache.org/jira/browse/JAMES-812
> Project: James
> Issue Type: Task
> Affects Versions: 2.3.2, 3.0, Trunk
> Reporter: Stefano Bagnara
> Assignee: Danny Angus
> Fix For: 2.3.2, 3.0
>
>
> Since we voted to rename the version from next-major to 3.0-SNAPSHOT the JIRA version should be updated according to that vote.
> next-minor and next-major should be removed forever as the vote where they was introduced has been "invalidated".
> Please fix this: mixing old and new names is even worse than not having a name/version at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JAMES-812) Fix JIRA versions. next-minor
and next-major do not have anymore meaning.
Posted by Norman Maurer <no...@apache.org>.
This makes sense to me...
+1
Norman
Am Dienstag, den 20.11.2007, 16:12 +0100 schrieb Stefano Bagnara:
> Danny Angus (JIRA) ha scritto:
> > [ https://issues.apache.org/jira/browse/JAMES-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543887 ]
> >
> > Danny Angus commented on JAMES-812:
> > -----------------------------------
> >
> > Should the version in JIRA be 3.0 or 3.0-SNAPSHOT ?
> >
> > if the major version is 3.0, then subsequent minor versions will be 3.0.x
> >
> > If it is 3.0-SNAPSHOT then presumably that would cover any unreleased version of 3.0?
> >
> > Comments?
>
>
> IMHO it depends on how we intend to use JIRA.
>
> I'm used to use real product release versions as labels.
>
> So, I'd name it "3.0". When we'll be ready for 3.0b1 (or something
> similar) we rename 3.0 to 3.0b1 and then we create a new 3.0 where we
> move evey issue we don't plan to fix for 3.0b1.
>
> Stefano
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JAMES-812) Fix JIRA versions. next-minor and next-major do not have anymore meaning.
Posted by Danny Angus <da...@apache.org>.
That makes sense to me. I'll make the changes.
d.
On 20/11/2007, Stefano Bagnara <ap...@bago.org> wrote:
> Danny Angus (JIRA) ha scritto:
> > [ https://issues.apache.org/jira/browse/JAMES-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543887 ]
> >
> > Danny Angus commented on JAMES-812:
> > -----------------------------------
> >
> > Should the version in JIRA be 3.0 or 3.0-SNAPSHOT ?
> >
> > if the major version is 3.0, then subsequent minor versions will be 3.0.x
> >
> > If it is 3.0-SNAPSHOT then presumably that would cover any unreleased version of 3.0?
> >
> > Comments?
>
>
> IMHO it depends on how we intend to use JIRA.
>
> I'm used to use real product release versions as labels.
>
> So, I'd name it "3.0". When we'll be ready for 3.0b1 (or something
> similar) we rename 3.0 to 3.0b1 and then we create a new 3.0 where we
> move evey issue we don't plan to fix for 3.0b1.
>
> Stefano
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Commented: (JAMES-812) Fix JIRA versions. next-minor and
next-major do not have anymore meaning.
Posted by Stefano Bagnara <ap...@bago.org>.
Danny Angus (JIRA) ha scritto:
> [ https://issues.apache.org/jira/browse/JAMES-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543887 ]
>
> Danny Angus commented on JAMES-812:
> -----------------------------------
>
> Should the version in JIRA be 3.0 or 3.0-SNAPSHOT ?
>
> if the major version is 3.0, then subsequent minor versions will be 3.0.x
>
> If it is 3.0-SNAPSHOT then presumably that would cover any unreleased version of 3.0?
>
> Comments?
IMHO it depends on how we intend to use JIRA.
I'm used to use real product release versions as labels.
So, I'd name it "3.0". When we'll be ready for 3.0b1 (or something
similar) we rename 3.0 to 3.0b1 and then we create a new 3.0 where we
move evey issue we don't plan to fix for 3.0b1.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-812) Fix JIRA versions. next-minor and
next-major do not have anymore meaning.
Posted by "Danny Angus (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543887 ]
Danny Angus commented on JAMES-812:
-----------------------------------
Should the version in JIRA be 3.0 or 3.0-SNAPSHOT ?
if the major version is 3.0, then subsequent minor versions will be 3.0.x
If it is 3.0-SNAPSHOT then presumably that would cover any unreleased version of 3.0?
Comments?
> Fix JIRA versions. next-minor and next-major do not have anymore meaning.
> -------------------------------------------------------------------------
>
> Key: JAMES-812
> URL: https://issues.apache.org/jira/browse/JAMES-812
> Project: James
> Issue Type: Task
> Affects Versions: Next Minor, Next Major, Trunk
> Reporter: Stefano Bagnara
> Fix For: Next Minor, Next Major, Trunk
>
>
> Since we voted to rename the version from next-major to 3.0-SNAPSHOT the JIRA version should be updated according to that vote.
> next-minor and next-major should be removed forever as the vote where they was introduced has been "invalidated".
> Please fix this: mixing old and new names is even worse than not having a name/version at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Assigned: (JAMES-812) Fix JIRA versions. next-minor and
next-major do not have anymore meaning.
Posted by "Danny Angus (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Danny Angus reassigned JAMES-812:
---------------------------------
Assignee: Danny Angus
> Fix JIRA versions. next-minor and next-major do not have anymore meaning.
> -------------------------------------------------------------------------
>
> Key: JAMES-812
> URL: https://issues.apache.org/jira/browse/JAMES-812
> Project: James
> Issue Type: Task
> Affects Versions: Next Minor, Next Major, Trunk
> Reporter: Stefano Bagnara
> Assignee: Danny Angus
> Fix For: Next Minor, Next Major, Trunk
>
>
> Since we voted to rename the version from next-major to 3.0-SNAPSHOT the JIRA version should be updated according to that vote.
> next-minor and next-major should be removed forever as the vote where they was introduced has been "invalidated".
> Please fix this: mixing old and new names is even worse than not having a name/version at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org