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. There should be no need for a "personal" road map. Am I getting something wrong again? [JH>] Ok, sometimes using german in english is not a good idea ;). What I was trying to say is, that by using the label form him, you and others, it is now possible without voting, to assign this label to things which one wants to do whilst working on next-major. When everyone is finished with it, it is possible to have the feature list, which has to be voted for (before branching) ready at a mouse click. This should really make voting and things easier, because the assignment of a label to a certain issue can be discussed beforehand, and prevents multiple threads when it comes to voting time. This has happened too many times in the past (at least while I am monitoring this list). The Discussions at the time of the vote tended to be drifting off topic, and to get personal. For me they became very hard to follow. Who said what, and the whole deal. This project has so many committers and people doing good things. Quite opposite to the project I am working on. And there is so much time spent on writing long E-Mails. I am not saying that they are useless, but most are off-topic and written to no consent. The Label really helps the guys in looking into Jira, and find an issue they want to work on, and assign it a label "next-major". There is no timeframe or Version Number or anything else so far. Just this label, which enables you all to say "I want to work on this feature". So what I wanted to say, is that is not one persons roadmap, but this projects possible roadmap for the next release. This Roadmap is changeable by all of you, and displays where this project is heading. If you disagree, you can start a discussion right away (but I think I said that before). Kind regards Juergen > > -----Ursprüngliche Nachricht----- > Von: Bernd Fondermann [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 22. November 2006 13:16 > An: James Developers List > Betreff: Re: Next-Major and trunk: AGAIN (Was: [jira] Updated: (JAMES-663)) > > On 11/22/06, Jürgen Hoffmann <[EMAIL PROTECTED]> wrote: > > 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. > > "for himself"? > > > > > And if trunk == next-major, where is the difference? > > The difference is, that TRUNK is existing in subversion and is the > place where all the commits go ATM. "Next-major" is a JIRA label and > if somebody looks at a JIRA item fixed for "next-major", people could > get confused (especially I get confused very easily) where to look at > (right answer would be: trunk). > Some issues where moved from trunk to next-major, some from next-major > to trunk, and so on. this seemed arbitrary to me. and this raised my > concerns. > > Bernd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > !EXCUBATOR:1,45643fbc53079559943052! > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !EXCUBATOR:1,45645cd653074584710222! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
