james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Hoffmann ...@byteaction.de>
Subject AW: Next-Major and trunk: AGAIN (Was: [jira] Updated: (JAMES-663))
Date Thu, 23 Nov 2006 00:06:38 GMT
Hi guys,

sorry if my last 2 E-Mails were shot before reading all Mails, but I am on a
GPRS Link at the moment, and using it is really a PITA.

Anyways, just to sum it up. It seems we all have the same view now, and can
agree with consent. Everyone is fine with what Stefano is doing, if he labels
issues both with "next-major" AND "trunk" correct?

Kind regards

Juergen

-----Ursprüngliche Nachricht-----
Von: Jürgen Hoffmann [mailto:jh@byteaction.de] 
Gesendet: Donnerstag, 23. November 2006 00:55
An: 'James Developers List'
Betreff: AW: Next-Major and trunk: AGAIN (Was: [jira] Updated: (JAMES-663))

Hi Noel,

you do not get the point. All he is doing is summing up things he wants to be
seen within next-major. It is a Summary of Features, which anyone with jira
access can and should change. Then after time, a discussion is started
probably sounding like this...

Guys, there is a feature-set that would be great to have in next-major. Please
look at it, and say what you think. Then another feature might be added or
dropped. I think this is a good thing. The leaves room for discussion before
the vote for the next release, to have a group of people vote about a feature
set, and once settled, branch and do release preparing from then on. Don't you
think?

Kind regards

Juergen

-----Ursprüngliche Nachricht-----
Von: Noel J. Bergman [mailto:noel@devtech.com] 
Gesendet: Mittwoch, 22. November 2006 16:41
An: James Developers List
Betreff: RE: Next-Major and trunk: AGAIN (Was: [jira] Updated: (JAMES-663))

Jürgen Hoffmann wrote:

> All he is doing is that he is tagging certain jira-issues,
> that they are fixed in the next-major

Well, that is the thing.  They may or may not be.  What there ARE closed in
is trunk.  I don't really care if they are listed against next-major, but
when we actually have code for next-major (remember: trunk is copied, then
PRUNED to become next-major), it may turn out that they are not resolved in
next-major at all.

All that I asked him to do was stop removing trunk as a label, since that IS
where the issue is resolved.

	--- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

!EXCUBATOR:1,45646fc353071734920388!



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

!EXCUBATOR:1,4564e37053071653268718!



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message