+1
Vincenzo
Jürgen Hoffmann wrote:
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
Hi Bernd,
From my viewpoint, all he is trying to do is to define a rough road map for
himself with the tools he has at hand.
And if trunk == next-major, where is the difference? Why is everyone so touchy
about the term?
I think what he is doing is fine, you guys voted about what you would like
Hi everybody,
Juergen said it exactly: what Stefano and Norman are doing is just proactively judging
what they think could and should be fixed/developed for next-major, and
documenting it through jira labels, without any change to our subversion repository. All
the committers are free to have
Hi Danny,
you contradict yourself. You say the term next-major has no meaning, but
there has been a vote to see on what people are willing to work on. Wihtin
this E-Mail/Vote I was able to read the term next-major a couple of times.
So this has a meaning to me and should have a meaning to you
Hi Bernd,
no offense at the moment, but knowing that Jira offers saveable search
queries, I am really puzzled by such a statement. You select Search Issues,
select Next Major and Trunk (You can select multiple entries by holding down
the CTRL-Key) and save your search. It is afterwards right
Hi Bernd,
cool. that is fabulous. problem solved... thanks! ;-)
[JH] anytime :)
Now as we have this yet overdiscussed jira label thingy resolved...
I still don't get this roadmap for himself statement you made. For
me, the current road map is to put all things in trunk until the
branching.
Hi Noel,
Noel J. Bergman [mailto:[EMAIL PROTECTED] wrote:
Now, let's consider next-major. As far as I know, we agree that the code in
trunk will branch to be next-major. BUT, we also agree that there is code in
trunk that may not survive the pruning. For example, perhaps none of the IMAP
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
issues both with next-major AND trunk correct?
Kind regards
Juergen
-Ursprüngliche Nachricht-
Von: Jürgen Hoffmann [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 23. November 2006 00:55
An: 'James Developers List'
Betreff: AW: Next-Major and trunk: AGAIN (Was: [jira] Updated: (JAMES-663
