Re: Releases, Continuous Delivery and the Future
On 15 December 2014 at 01:29, Jason van Zyl ja...@takari.io wrote: Hi, The discussion keeps resurfacing about how we deal with failed releases so I'll summarize how I think it should ultimately be done as a starting point. I'll go over the cases we've encountered thus far: 1) The user case prefers non-disjunct sets of releases, or from our PoV re-used versions. I believe people are confused by missing versions and will always result in questions like What happened to version X?, where X is a non-viable build. Not many people read release notes, will not self-serve and it will just be a lot of questions and confusion. The typical user doesn't care about the question of whether a particular build is viable or not. I think they naturally expect contiguous, increasing versions when they update to new versions of a product. I have not seen anyone asking what happened to 3.2.0 Similarly I have not seen anyone asking what happened to 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.1.7, 3.1.8 or 3.1.9 And also nobody was visible to me about what exactly happened to 3.0.6-3.0.9 inclusive or the vast range of continuous numbers we skipped before 3.0.0 I seem to recall a few questions about what da f*ck exactly was 2.0.10 and was it newer than 2.0.4 but, you know what, our users are by and large reasonably smart people, they can read an answer if we provide one, and the user community itself can probably sort out explaining where any missing versions went, especially if we put the explanation on a page on our website... So this use case is, to my mind, not really relevant. I think we can divide our users into two large groups: a. Those users who have a mandated version of maven that they must use b. Those users who are happy to use the latest version of maven whatever that is There are other groups out there, but I believe that the above two groups covers at least 80% of our users A final point on the user community... if we treat our users like idiots, then that's the kind of users we will get. I don't know how the rest of you feel about our users, but I know that our users are by and large a reasonably smart group of people. I just plain do not buy this argument about users expecting contiguous increasing versions. I think users expect us to actually cut releases on a reasonably frequent basis and to fix things and generally not make things worse... and that we will have a page somewhere that is easy to find (probably called release history) that will let them track down when the thing they care about right now changed so that they can either fix or roll-back to Get Things Done™ 2) The tester case prefers new versions but has tolerated re-used versions. Testers for core only really have to deal with the binary distribution and if it gets thrown away there's not much chance of local repository inconsistency because the typical tester, who is not an integrator, isn't going to depend on the new core release for anything. Running 3.2.4 doesn't put anything related to 3.2.4 in your local repository. This applies to core... but not so for testing plugins. We are not just a project about core. If we decide on a policy it should be a policy that works for both core and plugins. One thing we always complain about is the lack of testing in areas where our automated tests are weak. To combat that we need to grow our pool of testers to include people from the user community right now. Those users may not be as comfortable ensuring that they have cleared out their local repo of any side artifacts pulled in when testing a staged release... If they know that the artifact version number will never be re-used it gives them a bit more confidence. And this is not just about testing on your local machine, you might push the changes to your CI server via a pull request and a pull request builder to get even better test coverage. Then you have to worry that the CI server will have some build slaves with old pre-release versions. If we want to grow testing then I see re-use of versions a complete no-no. 3) The integrator case prefers new versions. Different content with the same version is a violation of our immutability philosophy and can cause issues. Even though this is very much contained at the moment let's be optimistic and believe we will have many integrators that will test pre-released versions. Igor is right in that it's not fun to keep track of this and why should the burden be placed on the integrator. The answer is it shouldn't. Again, from this use case I see re-use of versions as a complete no-no also. 4) The release manager case prefers new versions. When something is found wrong in 3.2.4 during voting, a user will create an issue in JIRA... found in 3.2.4... so we go and fix it... in 3.2.4... that just feels messy to me. I much rather say that an issue found in 3.2.4 is fixed in a later version... And before anyone asks, if the regression/issue was found in
Re: [VOTE] Run-off for mascot's name
This poll is now closed. I will now proceed to count the votes and votes received after this mail is sent will be excluded from the final count On 9 December 2014 at 10:52, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This is a run-off vote to select the top two options for our new mascot's name. The entries with the highest number of votes will be selected for the final round. If there is only one entry with the highest number of votes then the entries with the second highest number of votes will also be included in the final round. The vote will be open for 72 hours. The entries are as follows: A. Abraham B. Boo C. Darth Mowl D. Jacob E. Kaboom F. Moses G. Rap H. Shotgun K. The Maven Owl L. Ty It is not clear whether all of the above suggestions were completely serious, but I have included them anyway for this first round. Please respond with at most your top three in order of preference. I may not use second or third preferences if we get a sufficient number of votes, but in the case of a small poll the additional preferences will help. In the event of repeated votes from an individual, only the last cast vote as determined by me will count. Any other discussion should happen in a separate thread. Thanks -Stephen
Re: [VOTE] Run-off for mascot's name
After counting the 21 votes cast. I am eliminating C, F, G, and L as there is less than 3 votes between them and redistributing those votes would not affect the position of any of C, F, G or L Round 2 of the count will now proceed On 15 December 2014 at 10:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This poll is now closed. I will now proceed to count the votes and votes received after this mail is sent will be excluded from the final count On 9 December 2014 at 10:52, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This is a run-off vote to select the top two options for our new mascot's name. The entries with the highest number of votes will be selected for the final round. If there is only one entry with the highest number of votes then the entries with the second highest number of votes will also be included in the final round. The vote will be open for 72 hours. The entries are as follows: A. Abraham B. Boo C. Darth Mowl D. Jacob E. Kaboom F. Moses G. Rap H. Shotgun K. The Maven Owl L. Ty It is not clear whether all of the above suggestions were completely serious, but I have included them anyway for this first round. Please respond with at most your top three in order of preference. I may not use second or third preferences if we get a sufficient number of votes, but in the case of a small poll the additional preferences will help. In the event of repeated votes from an individual, only the last cast vote as determined by me will count. Any other discussion should happen in a separate thread. Thanks -Stephen
Re: [VOTE] Run-off for mascot's name
D has less second preferences that the other elimination candidate: A (based on votes of any preference) so eliminating D and promoting it's preferences accordingly (IOW Michael O's 2nd pref for A now becomes a 1st pref for A in round 3) On 15 December 2014 at 10:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After counting the 21 votes cast. I am eliminating C, F, G, and L as there is less than 3 votes between them and redistributing those votes would not affect the position of any of C, F, G or L Round 2 of the count will now proceed On 15 December 2014 at 10:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This poll is now closed. I will now proceed to count the votes and votes received after this mail is sent will be excluded from the final count On 9 December 2014 at 10:52, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This is a run-off vote to select the top two options for our new mascot's name. The entries with the highest number of votes will be selected for the final round. If there is only one entry with the highest number of votes then the entries with the second highest number of votes will also be included in the final round. The vote will be open for 72 hours. The entries are as follows: A. Abraham B. Boo C. Darth Mowl D. Jacob E. Kaboom F. Moses G. Rap H. Shotgun K. The Maven Owl L. Ty It is not clear whether all of the above suggestions were completely serious, but I have included them anyway for this first round. Please respond with at most your top three in order of preference. I may not use second or third preferences if we get a sufficient number of votes, but in the case of a small poll the additional preferences will help. In the event of repeated votes from an individual, only the last cast vote as determined by me will count. Any other discussion should happen in a separate thread. Thanks -Stephen
Re: [VOTE] Run-off for mascot's name
In Round 3, E only has 2nd preference votes (I could have eliminated E earlier, but given the transfers it makes no difference to the result...) I will now eliminate E and promote its preferences (which all go to K by the way) On 15 December 2014 at 10:21, Stephen Connolly stephen.alan.conno...@gmail.com wrote: D has less second preferences that the other elimination candidate: A (based on votes of any preference) so eliminating D and promoting it's preferences accordingly (IOW Michael O's 2nd pref for A now becomes a 1st pref for A in round 3) On 15 December 2014 at 10:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After counting the 21 votes cast. I am eliminating C, F, G, and L as there is less than 3 votes between them and redistributing those votes would not affect the position of any of C, F, G or L Round 2 of the count will now proceed On 15 December 2014 at 10:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This poll is now closed. I will now proceed to count the votes and votes received after this mail is sent will be excluded from the final count On 9 December 2014 at 10:52, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This is a run-off vote to select the top two options for our new mascot's name. The entries with the highest number of votes will be selected for the final round. If there is only one entry with the highest number of votes then the entries with the second highest number of votes will also be included in the final round. The vote will be open for 72 hours. The entries are as follows: A. Abraham B. Boo C. Darth Mowl D. Jacob E. Kaboom F. Moses G. Rap H. Shotgun K. The Maven Owl L. Ty It is not clear whether all of the above suggestions were completely serious, but I have included them anyway for this first round. Please respond with at most your top three in order of preference. I may not use second or third preferences if we get a sufficient number of votes, but in the case of a small poll the additional preferences will help. In the event of repeated votes from an individual, only the last cast vote as determined by me will count. Any other discussion should happen in a separate thread. Thanks -Stephen
Re: [VOTE] Run-off for mascot's name
A had no transfers to promote On 15 December 2014 at 10:28, Stephen Connolly stephen.alan.conno...@gmail.com wrote: At this point we have: A with 2x1st pref, 1x2nd pref (or 3 any pref votes) B with 5x1st pref, 1x2nd pref (or 6 any pref votes) H with 10x1st pref, 2x2nd pref (or 12 any pref votes) K with 4x1st pref, 5x2nd pref, 1x3rd pref (or 10 any pref votes) The lowest by any measure is A, so I will eliminate A and proceed to produce a count On 15 December 2014 at 10:24, Stephen Connolly stephen.alan.conno...@gmail.com wrote: In Round 3, E only has 2nd preference votes (I could have eliminated E earlier, but given the transfers it makes no difference to the result...) I will now eliminate E and promote its preferences (which all go to K by the way) On 15 December 2014 at 10:21, Stephen Connolly stephen.alan.conno...@gmail.com wrote: D has less second preferences that the other elimination candidate: A (based on votes of any preference) so eliminating D and promoting it's preferences accordingly (IOW Michael O's 2nd pref for A now becomes a 1st pref for A in round 3) On 15 December 2014 at 10:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After counting the 21 votes cast. I am eliminating C, F, G, and L as there is less than 3 votes between them and redistributing those votes would not affect the position of any of C, F, G or L Round 2 of the count will now proceed On 15 December 2014 at 10:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This poll is now closed. I will now proceed to count the votes and votes received after this mail is sent will be excluded from the final count On 9 December 2014 at 10:52, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This is a run-off vote to select the top two options for our new mascot's name. The entries with the highest number of votes will be selected for the final round. If there is only one entry with the highest number of votes then the entries with the second highest number of votes will also be included in the final round. The vote will be open for 72 hours. The entries are as follows: A. Abraham B. Boo C. Darth Mowl D. Jacob E. Kaboom F. Moses G. Rap H. Shotgun K. The Maven Owl L. Ty It is not clear whether all of the above suggestions were completely serious, but I have included them anyway for this first round. Please respond with at most your top three in order of preference. I may not use second or third preferences if we get a sufficient number of votes, but in the case of a small poll the additional preferences will help. In the event of repeated votes from an individual, only the last cast vote as determined by me will count. Any other discussion should happen in a separate thread. Thanks -Stephen
Re: [VOTE] Run-off for mascot's name
At this point we have: A with 2x1st pref, 1x2nd pref (or 3 any pref votes) B with 5x1st pref, 1x2nd pref (or 6 any pref votes) H with 10x1st pref, 2x2nd pref (or 12 any pref votes) K with 4x1st pref, 5x2nd pref, 1x3rd pref (or 10 any pref votes) The lowest by any measure is A, so I will eliminate A and proceed to produce a count On 15 December 2014 at 10:24, Stephen Connolly stephen.alan.conno...@gmail.com wrote: In Round 3, E only has 2nd preference votes (I could have eliminated E earlier, but given the transfers it makes no difference to the result...) I will now eliminate E and promote its preferences (which all go to K by the way) On 15 December 2014 at 10:21, Stephen Connolly stephen.alan.conno...@gmail.com wrote: D has less second preferences that the other elimination candidate: A (based on votes of any preference) so eliminating D and promoting it's preferences accordingly (IOW Michael O's 2nd pref for A now becomes a 1st pref for A in round 3) On 15 December 2014 at 10:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After counting the 21 votes cast. I am eliminating C, F, G, and L as there is less than 3 votes between them and redistributing those votes would not affect the position of any of C, F, G or L Round 2 of the count will now proceed On 15 December 2014 at 10:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This poll is now closed. I will now proceed to count the votes and votes received after this mail is sent will be excluded from the final count On 9 December 2014 at 10:52, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This is a run-off vote to select the top two options for our new mascot's name. The entries with the highest number of votes will be selected for the final round. If there is only one entry with the highest number of votes then the entries with the second highest number of votes will also be included in the final round. The vote will be open for 72 hours. The entries are as follows: A. Abraham B. Boo C. Darth Mowl D. Jacob E. Kaboom F. Moses G. Rap H. Shotgun K. The Maven Owl L. Ty It is not clear whether all of the above suggestions were completely serious, but I have included them anyway for this first round. Please respond with at most your top three in order of preference. I may not use second or third preferences if we get a sufficient number of votes, but in the case of a small poll the additional preferences will help. In the event of repeated votes from an individual, only the last cast vote as determined by me will count. Any other discussion should happen in a separate thread. Thanks -Stephen
[RESULT] [VOTE] Run-off for mascot's name
On the basis of any preference expressed: H: has 12 preferences expressed K: has 10 preferences expressed B: has 6 preferences expressed I declare the winners of the run-off to be H and K (i.e. Shotgun and The Maven Owl) I will now start a vote thread to decide the overall winner (And hopefully fend off Kristian and any attempts to run a stalking horse 3rd candidate of Shotgun, the Maven Owl ;-) ) -Stephen On 15 December 2014 at 10:29, Stephen Connolly stephen.alan.conno...@gmail.com wrote: A had no transfers to promote On 15 December 2014 at 10:28, Stephen Connolly stephen.alan.conno...@gmail.com wrote: At this point we have: A with 2x1st pref, 1x2nd pref (or 3 any pref votes) B with 5x1st pref, 1x2nd pref (or 6 any pref votes) H with 10x1st pref, 2x2nd pref (or 12 any pref votes) K with 4x1st pref, 5x2nd pref, 1x3rd pref (or 10 any pref votes) The lowest by any measure is A, so I will eliminate A and proceed to produce a count On 15 December 2014 at 10:24, Stephen Connolly stephen.alan.conno...@gmail.com wrote: In Round 3, E only has 2nd preference votes (I could have eliminated E earlier, but given the transfers it makes no difference to the result...) I will now eliminate E and promote its preferences (which all go to K by the way) On 15 December 2014 at 10:21, Stephen Connolly stephen.alan.conno...@gmail.com wrote: D has less second preferences that the other elimination candidate: A (based on votes of any preference) so eliminating D and promoting it's preferences accordingly (IOW Michael O's 2nd pref for A now becomes a 1st pref for A in round 3) On 15 December 2014 at 10:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After counting the 21 votes cast. I am eliminating C, F, G, and L as there is less than 3 votes between them and redistributing those votes would not affect the position of any of C, F, G or L Round 2 of the count will now proceed On 15 December 2014 at 10:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This poll is now closed. I will now proceed to count the votes and votes received after this mail is sent will be excluded from the final count On 9 December 2014 at 10:52, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This is a run-off vote to select the top two options for our new mascot's name. The entries with the highest number of votes will be selected for the final round. If there is only one entry with the highest number of votes then the entries with the second highest number of votes will also be included in the final round. The vote will be open for 72 hours. The entries are as follows: A. Abraham B. Boo C. Darth Mowl D. Jacob E. Kaboom F. Moses G. Rap H. Shotgun K. The Maven Owl L. Ty It is not clear whether all of the above suggestions were completely serious, but I have included them anyway for this first round. Please respond with at most your top three in order of preference. I may not use second or third preferences if we get a sufficient number of votes, but in the case of a small poll the additional preferences will help. In the event of repeated votes from an individual, only the last cast vote as determined by me will count. Any other discussion should happen in a separate thread. Thanks -Stephen
[VOTE] Name our mascot: Shotgun vs The Maven Owl
After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
A On 15 December 2014 at 10:39, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B /Anders On Mon, Dec 15, 2014 at 11:39 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen
AW: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Montag, 15. Dezember 2014 11:39 An: Maven Users List; Maven Developers List Betreff: [VOTE] Name our mascot: Shotgun vs The Maven Owl After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Dec 15, 2014 at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: A On 15 December 2014 at 10:39, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen
Re: Releases, Continuous Delivery and the Future
Sorry for the noise and maybe I am just being stupid but... This is a constant source of pain for us as Maven users when we do not use snapshots. The real problem is that once you go down his path, Maven seems to really only have two choices when you set your dependency version to 2.5.3: 1.) it only matches exactly with version 2.5.3 2.) it matches with any version that starts with 2.5.3 and picks the newest. Currently, #2 isn't possible without the use of version ranges, which are particularly painful with a large development team where I end up downloading the POM for every version of the artifact listed in maven-metadata.xml (in our case, hundreds per artifact) that is not currently cached in my .m2/repository directory. It seems like the current state of the art is to use the versions plugin to constant update your POM's dependency versions, which works ok but requires extra effort/discipline. Moving Maven core to use #2 seems like it removes the ability (or at least makes it much more difficult) to get repeatable builds. What am I missing? Robert Patrick robert.patr...@oracle.com VP, FMW Platform Engineering Oracle Mobile: +1 469 556 9450 Sent from my iPad On Dec 15, 2014, at 12:49 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: I somehow think we need to decide if we want to change anything :) Without changing anything there seem to be only so many approaches out there, this is well known territory. While initially confusing, jetty's 9.2.3.v20140905 approach is quite good. I assume they might have had a failing 9.2.3.v20140902 a few days before that we never got to see. It still gives the silly suffix on the name, and I think we might do one better. We change something in maven core, introduce a clearer separation of dependency-version (as-referenced version ) and artifact version: (Using the currently staged assembly-plugin 2.5.3 at https://repository.apache.org/content/repositories/maven-1103 as en example) The artifact is *always* called 2.5.3 in the pom version (what we all know as artifact-version). It's even deployed to these GAV coordinates in staging nexus. The signature signs a 2.5.3. version. In the vote mail we refer to the version as 2.5.3.v2014-12-13. Seeing this version number, maven 3.3+ writes download the artifacts to the folder ~/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.5.3.v2014-12-13 The tester tests a version named 2.5.3.v2014-12-13. If I re-roll the version will be 2.5.3.v2014-12-15. The payload is always version 2.5.3. If the 2.5.3.v2014-12-13 is broken, the stage at https://repository.apache.org/content/repositories/maven-1103 is dropped and all the testers/integrators are left with a broken ~/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.5.3.v2014-12-13 artifact, waiting for a replacement. Testers with pervious maven versions would have to follow the old rules. Does this blend ? (I have not entirely sorted out how this differs from fixing problems with snapshots and using numbered snapshots instead. ) Kristian Sat Dec 13 08:35:33 2014-12-15 2:29 GMT+01:00 Jason van Zyl ja...@takari.io: Hi, The discussion keeps resurfacing about how we deal with failed releases so I'll summarize how I think it should ultimately be done as a starting point. I'll go over the cases we've encountered thus far: 1) The user case prefers non-disjunct sets of releases, or from our PoV re-used versions. I believe people are confused by missing versions and will always result in questions like What happened to version X?, where X is a non-viable build. Not many people read release notes, will not self-serve and it will just be a lot of questions and confusion. The typical user doesn't care about the question of whether a particular build is viable or not. I think they naturally expect contiguous, increasing versions when they update to new versions of a product. 2) The tester case prefers new versions but has tolerated re-used versions. Testers for core only really have to deal with the binary distribution and if it gets thrown away there's not much chance of local repository inconsistency because the typical tester, who is not an integrator, isn't going to depend on the new core release for anything. Running 3.2.4 doesn't put anything related to 3.2.4 in your local repository. 3) The integrator case prefers new versions. Different content with the same version is a violation of our immutability philosophy and can cause issues. Even though this is very much contained at the moment let's be optimistic and believe we will have many integrators that will test pre-released versions. Igor is right in that it's not fun to keep track of this and why should the burden be placed on the integrator. The answer is it shouldn't. 4) The release manager case prefers new versions. I have typically reused versions
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
On 15 Dec 2014, at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time B. Regards, Graham — - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
A 2014-12-15 13:34 GMT+01:00 Graham Leggett minf...@sharp.fm: On 15 Dec 2014, at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time B. Regards, Graham — - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
On Mon, 15 Dec 2014 10:39:27 + Stephen Connolly stephen.alan.conno...@gmail.com wrote: A thanks, tony. After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
As cute as Shutgun might seem, for some unspecified definition of cute, I am sick of hearing about any kind of gun... http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html Gary On Mon, Dec 15, 2014 at 7:30 AM, Jeroen Hoek jer...@lable.org wrote: B 2014-12-15 12:41 GMT+01:00 Martin Grigorov mgrigo...@apache.org: B Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Dec 15, 2014 at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: A On 15 December 2014 at 10:39, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Vriendelijke groeten, Jeroen Hoek Lable ✉ jer...@lable.org ℡ 088 44 20 202 http://lable.org KvK № 55984037 BTW № NL8519.32.411.B.01 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
Re: Releases, Continuous Delivery and the Future
On Dec 15, 2014, at 1:49 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: I somehow think we need to decide if we want to change anything :) We certainly don't have to. I'm describing a system that's been implemented and it's working but I'm not expecting as a certainty that it's integrated here. I believe it's necessary which is why we built it for a customer. Without changing anything there seem to be only so many approaches out there, this is well known territory. While initially confusing, jetty's 9.2.3.v20140905 approach is quite good. I assume they might have had a failing 9.2.3.v20140902 a few days before that we never got to see. It still gives the silly suffix on the name, and I think we might do one better. The qualifier usually incorporates some temporal aspect and you just pick a build along the continuum that is deemed fit for release. We change something in maven core, introduce a clearer separation of dependency-version (as-referenced version ) and artifact version: (Using the currently staged assembly-plugin 2.5.3 at https://repository.apache.org/content/repositories/maven-1103 as en example) The artifact is *always* called 2.5.3 in the pom version (what we all know as artifact-version). It's even deployed to these GAV coordinates in staging nexus. The signature signs a 2.5.3. version. In the vote mail we refer to the version as 2.5.3.v2014-12-13. Seeing this version number, maven 3.3+ writes download the artifacts to the folder ~/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.5.3.v2014-12-13 The tester tests a version named 2.5.3.v2014-12-13. If I re-roll the version will be 2.5.3.v2014-12-15. The payload is always version 2.5.3. No, the 2.5.3 version in your case is only the marketing version in what I described. All artifacts that are part of the deployment are fully qualified and have the full version contained within them. This is for a simple deployment. It's get more complicated when you are trying to release a graph of related projects. If the 2.5.3.v2014-12-13 is broken, the stage at https://repository.apache.org/content/repositories/maven-1103 is dropped and all the testers/integrators are left with a broken ~/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.5.3.v2014-12-13 artifact, waiting for a replacement. Sure, it's broken but I am assuming all references to its use are versioned and they will just have to move ahead to try it which means specifying an exact version. Testers with pervious maven versions would have to follow the old rules. Not sure what you mean by the old rules. The failed version is just discarded, testers use a new version and carry on. Though there is a distinction between using something like a Maven distribution vs a library. If a library build failed then a tester is going to have to update the version they are using. I don't think there is any magic that is sufficient, or desirable, that lets people reuse a version in any form. Does this blend ? I think the only point I can see where I don't agree is that the payload always gets the marketing version. I don't think that works. (I have not entirely sorted out how this differs from fixing problems with snapshots and using numbered snapshots instead. ) Kristian Sat Dec 13 08:35:33 2014-12-15 2:29 GMT+01:00 Jason van Zyl ja...@takari.io: Hi, The discussion keeps resurfacing about how we deal with failed releases so I'll summarize how I think it should ultimately be done as a starting point. I'll go over the cases we've encountered thus far: 1) The user case prefers non-disjunct sets of releases, or from our PoV re-used versions. I believe people are confused by missing versions and will always result in questions like What happened to version X?, where X is a non-viable build. Not many people read release notes, will not self-serve and it will just be a lot of questions and confusion. The typical user doesn't care about the question of whether a particular build is viable or not. I think they naturally expect contiguous, increasing versions when they update to new versions of a product. 2) The tester case prefers new versions but has tolerated re-used versions. Testers for core only really have to deal with the binary distribution and if it gets thrown away there's not much chance of local repository inconsistency because the typical tester, who is not an integrator, isn't going to depend on the new core release for anything. Running 3.2.4 doesn't put anything related to 3.2.4 in your local repository. 3) The integrator case prefers new versions. Different content with the same version is a violation of our immutability philosophy and can cause issues. Even though this is very much contained at the moment let's be optimistic and believe we will have many integrators that will test pre-released versions. Igor is right in
Re: Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
As cute as Shutgun might seem, for some unspecified definition of cute, I am sick of hearing about any kind of gun... http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html Thank you so much for bringing this up. I am personally disgusted about the stupid names proposed like: Boom, Shotgun and anything else related to a rifle or arming. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B Martijn On Mon, Dec 15, 2014 at 2:27 PM, David Hoffer dhoff...@gmail.com wrote: B -Dave On Mon, Dec 15, 2014 at 6:22 AM, cody.a.fy...@wellsfargo.com wrote: B Cody Fyler Lending Grid Build Team G=Lending Grid Builds (515) – 441 - 0814 -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Monday, December 15, 2014 4:39 AM To: Maven Users List; Maven Developers List Subject: [VOTE] Name our mascot: Shotgun vs The Maven Owl After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.5
At first glance that does not look like a valid OSGi version: http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/Version.html In Tycho something like: 1.0-SNAPSHOT in the POM and 1.0.qualifier in the MANIFEST.MF would turn into something like: 1.0.497f8c4709bea5e3656572cf52462c1b259c But I'm not sure how you're getting that qualifier or what your versions are like. If the project is somewhere we can look at I'm sure Igor/Jan can point out what's wrong if there is anything. On Dec 14, 2014, at 10:17 PM, Mark Derricutt m...@talios.com wrote: On 15 Dec 2014, at 7:00, Jason van Zyl wrote: Time to release Maven 3.2.5! Just hit an interesting problem (that may not actually be a problem): [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException Deploying 1.0.6-SNAPSHOT to staging with version 1.0-497f8c4709bea5e3656572cf52462c1b259c [ERROR] Internal error: java.lang.IllegalArgumentException: Format format(n[.n=0;[.n=0;[-S]]]) was unable to parse 1.0-497f8c4709bea5e3656572cf52462c1b259c - [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.IllegalArgumentException: Format format(n[.n=0;[.n=0;[-S]]]) was unable to parse 1.0-497f8c4709bea5e3656572cf52462c1b259c at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: java.lang.IllegalArgumentException: Format format(n[.n=0;[.n=0;[-S]]]) was unable to parse 1.0-497f8c4709bea5e3656572cf52462c1b259c at org.eclipse.equinox.internal.p2.metadata.VersionFormat.parse(VersionFormat.java:275) at org.eclipse.equinox.internal.p2.metadata.VersionParser.parse(VersionParser.java:177) at org.eclipse.equinox.p2.metadata.Version.create(Version.java:79) at org.eclipse.tycho.p2.impl.publisher.AbstractSiteDependenciesAction.createSiteVersion(AbstractSiteDependenciesAction.java:77) at org.eclipse.tycho.p2.impl.publisher.AbstractSiteDependenciesAction.getVersion(AbstractSiteDependenciesAction.java:68) at org.eclipse.tycho.p2.impl.publisher.AbstractDependenciesAction.perform(AbstractDependenciesAction.java:79) at org.eclipse.equinox.p2.publisher.Publisher$ArtifactProcess.run(Publisher.java:207) at org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:237) at org.eclipse.tycho.p2.impl.publisher.AbstractMetadataGenerator.publish(AbstractMetadataGenerator.java:118) at org.eclipse.tycho.p2.impl.publisher.AbstractMetadataGenerator.generateMetadata(AbstractMetadataGenerator.java:58) at org.eclipse.tycho.p2.impl.publisher.DefaultDependencyMetadataGenerator.generateMetadata(DefaultDependencyMetadataGenerator.java:30) at org.eclipse.tycho.p2.impl.publisher.DefaultDependencyMetadataGenerator.generateMetadata(DefaultDependencyMetadataGenerator.java:1) at org.eclipse.tycho.p2.resolver.P2DependencyResolver.getDependencyMetadata(P2DependencyResolver.java:143) at org.eclipse.tycho.p2.resolver.P2DependencyResolver.setupProjects(P2DependencyResolver.java:126) at org.eclipse.tycho.core.resolver.DefaultTychoResolver.setupProject(DefaultTychoResolver.java:87) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:70) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:318) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) ... 11 more I have a script I use occasionally to stage binaries to an internal staging repository using the following: VERSION=`xml sel -N x=http://maven.apache.org/POM/4.0.0; -t -v /x:project/x:version pom.xml` BASEVERSION=`echo $VERSION | sed -E s/\.[0-9]+-SNAPSHOT//g` ARTIFACTID=`xml sel -N x=http://maven.apache.org/POM/4.0.0; -t -v /x:project/x:artifactId pom.xml` SHA1=`git rev-parse HEAD` STAGEVERSION=$BASEVERSION-$SHA1 mvn -q -o versions:set -DnewVersion=$STAGEVERSION echo Building $ARTIFACTID $VERSION for staging with version $STAGEVERSION mvn -q -o clean install echo Deploying $ARTIFACTID $VERSION to staging with version $STAGEVERSION mvn -q install deploy:deploy
Re: Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
I don't imagine this is an open vote, but I lurk and agree: shotgun is very off putting. B On 15 December 2014 at 13:33, Michael Osipov 1983-01...@gmx.net wrote: As cute as Shutgun might seem, for some unspecified definition of cute, I am sick of hearing about any kind of gun... http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html Thank you so much for bringing this up. I am personally disgusted about the stupid names proposed like: Boom, Shotgun and anything else related to a rifle or arming. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tim Pizey http://pizey.net/~timp - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B as in Dont care Kristian shotgun owl for president 2014-12-15 13:42 GMT+01:00 Kristian Rosenvold kristian.rosenv...@gmail.com: A 2014-12-15 13:34 GMT+01:00 Graham Leggett minf...@sharp.fm: On 15 Dec 2014, at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time B. Regards, Graham — - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: dev Digest 15 Dec 2014 13:39:16 -0000 Issue 5782
A -Dan On Dec 15, 2014, at 8:39 AM, dev-digest-h...@maven.apache.org wrote: From: Martijn Dashorst martijn.dasho...@gmail.com mailto:martijn.dasho...@gmail.com Date: December 15, 2014 at 8:34:04 AM EST Subject: Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl To: Maven Users List us...@maven.apache.org mailto:us...@maven.apache.org Cc: Maven Developers List dev@maven.apache.org mailto:dev@maven.apache.org B Martijn On Mon, Dec 15, 2014 at 2:27 PM, David Hoffer dhoff...@gmail.com mailto:dhoff...@gmail.com wrote: B -Dave On Mon, Dec 15, 2014 at 6:22 AM, cody.a.fy...@wellsfargo.com mailto:cody.a.fy...@wellsfargo.com wrote: B Cody Fyler Lending Grid Build Team G=Lending Grid Builds (515) – 441 - 0814 -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com mailto:stephen.alan.conno...@gmail.com] Sent: Monday, December 15, 2014 4:39 AM To: Maven Users List; Maven Developers List Subject: [VOTE] Name our mascot: Shotgun vs The Maven Owl After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org mailto:users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org mailto:users-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
A - Shotgun Stephen Connolly wrote on 15.12.2014 02:39: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: dev Digest 15 Dec 2014 13:39:16 -0000 Issue 5782
Dan, can you please vote on the actual thread and not the digest? On 15 December 2014 at 14:59, Dan Rollo danro...@gmail.com wrote: A -Dan On Dec 15, 2014, at 8:39 AM, dev-digest-h...@maven.apache.org wrote: From: Martijn Dashorst martijn.dasho...@gmail.com mailto: martijn.dasho...@gmail.com Date: December 15, 2014 at 8:34:04 AM EST Subject: Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl To: Maven Users List us...@maven.apache.org mailto: us...@maven.apache.org Cc: Maven Developers List dev@maven.apache.org mailto: dev@maven.apache.org B Martijn On Mon, Dec 15, 2014 at 2:27 PM, David Hoffer dhoff...@gmail.com mailto:dhoff...@gmail.com wrote: B -Dave On Mon, Dec 15, 2014 at 6:22 AM, cody.a.fy...@wellsfargo.com mailto: cody.a.fy...@wellsfargo.com wrote: B Cody Fyler Lending Grid Build Team G=Lending Grid Builds (515) – 441 - 0814 -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com mailto:stephen.alan.conno...@gmail.com] Sent: Monday, December 15, 2014 4:39 AM To: Maven Users List; Maven Developers List Subject: [VOTE] Name our mascot: Shotgun vs The Maven Owl After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org mailto: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org mailto: users-h...@maven.apache.org
Re: Releases, Continuous Delivery and the Future
You're not missing anything. The integration we've written essentially replaces much of the internal resolution mechanism with support on the repository side. We currently do not use SNAPSHOTs and we do use ranges for a team of 1500+ developers. It will all be open source but we're not ready to open it yet. We have made all sorts of assumptions in general but some have been shaped by the requirements of the organization we're working for. We're not exactly sure what the POMs should look like but we're moving toward having no versions anywhere in the POMs and using tooling to generated the required POMs on deployment. At some point, likely in January, I'll try to have a little meetup in the Bay Area to try and shape some of the final requirements. Our target is making it work for our customer but our hope is that this will be a generally applicable model for continuous delivery. I'm also testing this with Facebook's Presto project which is interesting because we basically have the requirement to work with a graph of related projects and release the graph of projects at the same time. We have the additional requirement that ultimately it needs to be consumable by users from Maven Central. We certainly haven't figured everything out but we're getting there and it's been working in production for 6 months. On Dec 15, 2014, at 7:06 AM, Robert Patrick robert.patr...@oracle.com wrote: Sorry for the noise and maybe I am just being stupid but... This is a constant source of pain for us as Maven users when we do not use snapshots. The real problem is that once you go down his path, Maven seems to really only have two choices when you set your dependency version to 2.5.3: 1.) it only matches exactly with version 2.5.3 2.) it matches with any version that starts with 2.5.3 and picks the newest. Currently, #2 isn't possible without the use of version ranges, which are particularly painful with a large development team where I end up downloading the POM for every version of the artifact listed in maven-metadata.xml (in our case, hundreds per artifact) that is not currently cached in my .m2/repository directory. It seems like the current state of the art is to use the versions plugin to constant update your POM's dependency versions, which works ok but requires extra effort/discipline. Moving Maven core to use #2 seems like it removes the ability (or at least makes it much more difficult) to get repeatable builds. What am I missing? Robert Patrick robert.patr...@oracle.com VP, FMW Platform Engineering Oracle Mobile: +1 469 556 9450 Sent from my iPad On Dec 15, 2014, at 12:49 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: I somehow think we need to decide if we want to change anything :) Without changing anything there seem to be only so many approaches out there, this is well known territory. While initially confusing, jetty's 9.2.3.v20140905 approach is quite good. I assume they might have had a failing 9.2.3.v20140902 a few days before that we never got to see. It still gives the silly suffix on the name, and I think we might do one better. We change something in maven core, introduce a clearer separation of dependency-version (as-referenced version ) and artifact version: (Using the currently staged assembly-plugin 2.5.3 at https://repository.apache.org/content/repositories/maven-1103 as en example) The artifact is *always* called 2.5.3 in the pom version (what we all know as artifact-version). It's even deployed to these GAV coordinates in staging nexus. The signature signs a 2.5.3. version. In the vote mail we refer to the version as 2.5.3.v2014-12-13. Seeing this version number, maven 3.3+ writes download the artifacts to the folder ~/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.5.3.v2014-12-13 The tester tests a version named 2.5.3.v2014-12-13. If I re-roll the version will be 2.5.3.v2014-12-15. The payload is always version 2.5.3. If the 2.5.3.v2014-12-13 is broken, the stage at https://repository.apache.org/content/repositories/maven-1103 is dropped and all the testers/integrators are left with a broken ~/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.5.3.v2014-12-13 artifact, waiting for a replacement. Testers with pervious maven versions would have to follow the old rules. Does this blend ? (I have not entirely sorted out how this differs from fixing problems with snapshots and using numbered snapshots instead. ) Kristian Sat Dec 13 08:35:33 2014-12-15 2:29 GMT+01:00 Jason van Zyl ja...@takari.io: Hi, The discussion keeps resurfacing about how we deal with failed releases so I'll summarize how I think it should ultimately be done as a starting point. I'll go over the cases we've encountered thus far: 1) The user case prefers non-disjunct sets of releases, or from our PoV re-used versions. I believe people are
RE: Releases, Continuous Delivery and the Future
If you need outside opinions, I would be happy to participate in that meeting... :-) -- Robert Patrick robert.patr...@oracle.com VP, FMW Platform Engineering, Oracle Corporation 7460 Warren Pkwy, Ste. 300 Office: +1.972.963.2872 Frisco, TX 75034, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -Original Message- From: Jason van Zyl [mailto:ja...@takari.io] Sent: Monday, December 15, 2014 11:08 AM To: Maven Developers List Subject: Re: Releases, Continuous Delivery and the Future You're not missing anything. The integration we've written essentially replaces much of the internal resolution mechanism with support on the repository side. We currently do not use SNAPSHOTs and we do use ranges for a team of 1500+ developers. It will all be open source but we're not ready to open it yet. We have made all sorts of assumptions in general but some have been shaped by the requirements of the organization we're working for. We're not exactly sure what the POMs should look like but we're moving toward having no versions anywhere in the POMs and using tooling to generated the required POMs on deployment. At some point, likely in January, I'll try to have a little meetup in the Bay Area to try and shape some of the final requirements. Our target is making it work for our customer but our hope is that this will be a generally applicable model for continuous delivery. I'm also testing this with Facebook's Presto project which is interesting because we basically have the requirement to work with a graph of related projects and release the graph of projects at the same time. We have the additional requirement that ultimately it needs to be consumable by users from Maven Central. We certainly haven't figured everything out but we're getting there and it's been working in production for 6 months. On Dec 15, 2014, at 7:06 AM, Robert Patrick robert.patr...@oracle.com wrote: Sorry for the noise and maybe I am just being stupid but... This is a constant source of pain for us as Maven users when we do not use snapshots. The real problem is that once you go down his path, Maven seems to really only have two choices when you set your dependency version to 2.5.3: 1.) it only matches exactly with version 2.5.3 2.) it matches with any version that starts with 2.5.3 and picks the newest. Currently, #2 isn't possible without the use of version ranges, which are particularly painful with a large development team where I end up downloading the POM for every version of the artifact listed in maven-metadata.xml (in our case, hundreds per artifact) that is not currently cached in my .m2/repository directory. It seems like the current state of the art is to use the versions plugin to constant update your POM's dependency versions, which works ok but requires extra effort/discipline. Moving Maven core to use #2 seems like it removes the ability (or at least makes it much more difficult) to get repeatable builds. What am I missing? Robert Patrick robert.patr...@oracle.com VP, FMW Platform Engineering Oracle Mobile: +1 469 556 9450 Sent from my iPad On Dec 15, 2014, at 12:49 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: I somehow think we need to decide if we want to change anything :) Without changing anything there seem to be only so many approaches out there, this is well known territory. While initially confusing, jetty's 9.2.3.v20140905 approach is quite good. I assume they might have had a failing 9.2.3.v20140902 a few days before that we never got to see. It still gives the silly suffix on the name, and I think we might do one better. We change something in maven core, introduce a clearer separation of dependency-version (as-referenced version ) and artifact version: (Using the currently staged assembly-plugin 2.5.3 at https://repository.apache.org/content/repositories/maven-1103 as en example) The artifact is *always* called 2.5.3 in the pom version (what we all know as artifact-version). It's even deployed to these GAV coordinates in staging nexus. The signature signs a 2.5.3. version. In the vote mail we refer to the version as 2.5.3.v2014-12-13. Seeing this version number, maven 3.3+ writes download the artifacts to the folder ~/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.5.3 .v2014-12-13 The tester tests a version named 2.5.3.v2014-12-13. If I re-roll the version will be 2.5.3.v2014-12-15. The payload is always version 2.5.3. If the 2.5.3.v2014-12-13 is broken, the stage at https://repository.apache.org/content/repositories/maven-1103 is dropped and all the testers/integrators are left with a broken ~/.m2/repository/org/apache/maven/plugins/maven-assembly-plugin/2.5.3
Infrastructure Information
Hi to all, on Wednesday 21:00 UTC Erebus Server will be taken down which results in downtime (estimated for around 45 minutes) for several services... * Confluence Wiki * repository.apache.org and other services as well... So don't be astonished.. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
A Sent from my iPhone On 15/12/2014, at 9:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.2.5
Hi, +1 from me... Kind regards Karl Heinz Marbaise On 12/14/14 7:00 PM, Jason van Zyl wrote: Hi, Time to release Maven 3.2.5! Here is a link to Jira with 22 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=20819 Staging repo: https://repository.apache.org/content/repositories/maven-1104/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-1104/org/apache/maven/apache-maven/3.2.5/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-1104/org/apache/maven/apache-maven/3.2.5/apache-maven-3.2.5-bin.zip https://repository.apache.org/content/repositories/maven-1104/org/apache/maven/apache-maven/3.2.5/apache-maven-3.2.5-bin.tar.gz https://repository.apache.org/content/repositories/maven-1104/org/apache/maven/apache-maven/3.2.5/apache-maven-3.2.5-src.zip https://repository.apache.org/content/repositories/maven-1104/org/apache/maven/apache-maven/3.2.5/apache-maven-3.2.5-src.tar.gz Source release checksum(s): apache-maven-3.2.5-src.zip sha1: 305f539af0e4e48c37e6a406712ad1fb7bc16d79 Staging site: http://takari.io/maven-3.2.5/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
A -Dan On 15/12/2014, at 9:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen
Re: Releases, Continuous Delivery and the Future
Jason, thanks for taking the time to write this up. It is a good read. One extra tidbit I'd like to discussion is this. When I recommended we burn the version when the vote/build fails, I wasn't expecting we would move the fixed issues to the new version. Let's not do that. I find that confusing because it's impossible to keep track which issues are tied to what vote. For example, when 3.2.4 failed with 20 fixed issues, I want to see the 3.2.4 issues stay as-is and 3.2.5 to have new issues. We don't need the extra JIRA maintenance of moving issues when a version is burned, and, overall, it is a better historical record of the facts. WDYT? Cheers, Paul On Sun, Dec 14, 2014 at 7:29 PM, Jason van Zyl ja...@takari.io wrote: Hi, The discussion keeps resurfacing about how we deal with failed releases so I'll summarize how I think it should ultimately be done as a starting point. I'll go over the cases we've encountered thus far: 1) The user case prefers non-disjunct sets of releases, or from our PoV re-used versions. I believe people are confused by missing versions and will always result in questions like What happened to version X?, where X is a non-viable build. Not many people read release notes, will not self-serve and it will just be a lot of questions and confusion. The typical user doesn't care about the question of whether a particular build is viable or not. I think they naturally expect contiguous, increasing versions when they update to new versions of a product. 2) The tester case prefers new versions but has tolerated re-used versions. Testers for core only really have to deal with the binary distribution and if it gets thrown away there's not much chance of local repository inconsistency because the typical tester, who is not an integrator, isn't going to depend on the new core release for anything. Running 3.2.4 doesn't put anything related to 3.2.4 in your local repository. 3) The integrator case prefers new versions. Different content with the same version is a violation of our immutability philosophy and can cause issues. Even though this is very much contained at the moment let's be optimistic and believe we will have many integrators that will test pre-released versions. Igor is right in that it's not fun to keep track of this and why should the burden be placed on the integrator. The answer is it shouldn't. 4) The release manager case prefers new versions. I have typically reused versions because I believe 1) is true. It's a PITA to erase tags, shuffle issues around in JIRA, and reset the POMs. I would prefer to just move forward, but I have done it because the user confusion is not worth the small effort it takes me to clean up a few resources. One hour for me versus thousands of hours of confusion for all users. It's an easy calculation. Taking all these cases into consideration so that all participants are satisfied I think we ultimately want increasing and contiguous versions for users, testers and integrators while the release manager does not have to shuffle a bunch of resources around in the event of a non-viable build. What we want is a form of continuous delivery where a version like 3.2.4 is the version that we call it to the outside world (some refer to it as the marketing version) and the qualifier changes from build to build so we have: 3.2.4-qualifier And for simplicity's sake let's just say the qualifier is a build number so we end up with: 3.2.4-01 3.2.4-02 ... 3.2.4-NN Every build is a complete build that can be released, and in the stream of builds that are produced we decide that one is good enough for public consumption. Nothing in the issue tracking or documentation needs to change as it's still referred to as 3.2.4. People who download the distribution aren't going to care what the exact versions say on the JARs but some education might be required to tell people that something like 3.2.4 is actually 3.2.4-05 if they want to refer to an artifact from 3.2.4. I don't think making aliases to the marketing versions are a good idea and wouldn't want to duplicate artifacts so that they can be referred to by the marketing version. People will just become accustom to knowing a qualifier is necessary to find the actual version. This is more how things work at Eclipse where if you look at something from Jetty: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.eclipse.jetty%22%20AND%20a%3A%22jetty-servlet%22 You'll see that something like jetty-servlet 9.2.3 is actually referred to as 9.2.3.v20140905. Jetty seems somewhat inconsistent with respect to milestones but you get the idea. I think this works for all parties but especially users where say we all happen to write blog entries about 3.2.4 and it fails twice and we actually release 3.2.6. This is just so confusing as anything that referred to 3.2.4 now really means 3.2.6 which is totally inconsistent. I think skipping failed
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B Arnaud On Mon, Dec 15, 2014 at 10:12 PM, Dan Rollo danro...@gmail.com wrote: A -Dan On 15/12/2014, at 9:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
You raise a fair point, and for that reason I am changing my vote to B On 15 December 2014 at 13:15, Gary Gregory garydgreg...@gmail.com wrote: As cute as Shutgun might seem, for some unspecified definition of cute, I am sick of hearing about any kind of gun... http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html Gary On Mon, Dec 15, 2014 at 7:30 AM, Jeroen Hoek jer...@lable.org wrote: B 2014-12-15 12:41 GMT+01:00 Martin Grigorov mgrigo...@apache.org: B Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Dec 15, 2014 at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: A On 15 December 2014 at 10:39, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Vriendelijke groeten, Jeroen Hoek Lable ✉ jer...@lable.org ℡ 088 44 20 202 http://lable.org KvK № 55984037 BTW № NL8519.32.411.B.01 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B 2014-12-16 0:26 GMT+02:00 Stephen Connolly stephen.alan.conno...@gmail.com : You raise a fair point, and for that reason I am changing my vote to B On 15 December 2014 at 13:15, Gary Gregory garydgreg...@gmail.com wrote: As cute as Shutgun might seem, for some unspecified definition of cute, I am sick of hearing about any kind of gun... http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html Gary On Mon, Dec 15, 2014 at 7:30 AM, Jeroen Hoek jer...@lable.org wrote: B 2014-12-15 12:41 GMT+01:00 Martin Grigorov mgrigo...@apache.org: B Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Dec 15, 2014 at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: A On 15 December 2014 at 10:39, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Vriendelijke groeten, Jeroen Hoek Lable ✉ jer...@lable.org ℡ 088 44 20 202 http://lable.org KvK № 55984037 BTW № NL8519.32.411.B.01 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory -- Regards, Petar! Karlovo, Bulgaria. --- Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
[VOTE] Release Apache Maven Ant Plugin version 2.4
Hi, We solved 10 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11124version=15977 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MANT%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1105/ http://repository.apache.org/content/repositories/maven-1105/org/apache/maven/plugins/maven-ant-plugin/2.4/maven-ant-plugin-2.4-source-release.zip Source release checksum(s): maven-ant-plugin-2.4-source-release.zip sha1: e3a40eb756c3e585fa5c7fa375d3e1834ba0e104 Staging site: http://maven.apache.org/plugins-archives/maven-ant-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
I guess I should VOTE B, but I am not on the PMC so I am not sure which votes count. Gary On Mon, Dec 15, 2014 at 5:26 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: You raise a fair point, and for that reason I am changing my vote to B On 15 December 2014 at 13:15, Gary Gregory garydgreg...@gmail.com wrote: As cute as Shutgun might seem, for some unspecified definition of cute, I am sick of hearing about any kind of gun... http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html Gary On Mon, Dec 15, 2014 at 7:30 AM, Jeroen Hoek jer...@lable.org wrote: B 2014-12-15 12:41 GMT+01:00 Martin Grigorov mgrigo...@apache.org: B Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Dec 15, 2014 at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: A On 15 December 2014 at 10:39, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Vriendelijke groeten, Jeroen Hoek Lable ✉ jer...@lable.org ℡ 088 44 20 202 http://lable.org KvK № 55984037 BTW № NL8519.32.411.B.01 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B On 15 December 2014 at 21:39, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Maven Assembly Plugin version 2.5.3
+1 Regards, Hervé Le samedi 13 décembre 2014 10:33:24 Kristian Rosenvold a écrit : Hi, We solved 21 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20790styleName=Htm lprojectId=11126 This release is mostly focused on regressions and minor issues in the 2.5.X range. There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20statu s%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1103 https://repository.apache.org/content/repositories/maven-1103/org/apache/mav en/plugins/maven-assembly-plugin/2.5.3/maven-assembly-plugin-2.5.3-source-re lease.zip Source release checksum(s): maven-assembly-plugin-2.5.3-source-release.zip sha1: 9d676829ab791e13d4ebca20f4e77c8e6109c72f Staging site: http://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
All votes count. PMC votes are special for binary releases due to legal requirements. This is a community issue, so everyone is welcome On Tuesday, December 16, 2014, Gary Gregory garydgreg...@gmail.com wrote: I guess I should VOTE B, but I am not on the PMC so I am not sure which votes count. Gary On Mon, Dec 15, 2014 at 5:26 PM, Stephen Connolly stephen.alan.conno...@gmail.com javascript:; wrote: You raise a fair point, and for that reason I am changing my vote to B On 15 December 2014 at 13:15, Gary Gregory garydgreg...@gmail.com javascript:; wrote: As cute as Shutgun might seem, for some unspecified definition of cute, I am sick of hearing about any kind of gun... http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html Gary On Mon, Dec 15, 2014 at 7:30 AM, Jeroen Hoek jer...@lable.org javascript:; wrote: B 2014-12-15 12:41 GMT+01:00 Martin Grigorov mgrigo...@apache.org javascript:;: B Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Dec 15, 2014 at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com javascript:; wrote: A On 15 December 2014 at 10:39, Stephen Connolly stephen.alan.conno...@gmail.com javascript:; wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Vriendelijke groeten, Jeroen Hoek Lable ✉ jer...@lable.org javascript:; ℡ 088 44 20 202 http://lable.org KvK № 55984037 BTW № NL8519.32.411.B.01 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: users-h...@maven.apache.org javascript:; -- E-Mail: garydgreg...@gmail.com javascript:; | ggreg...@apache.org javascript:; Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory -- E-Mail: garydgreg...@gmail.com javascript:; | ggreg...@apache.org javascript:; Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory -- Sent from my phone
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B On 12/15/2014 11:39 AM, Stephen Connolly wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Mikolaj Izdebski Software Engineer, Red Hat - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
On Mon, Dec 15, 2014 at 2:15 PM, Gary Gregory garydgreg...@gmail.com wrote: As cute as Shutgun might seem, for some unspecified definition of cute, I am sick of hearing about any kind of gun... http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html Same here. B Gary On Mon, Dec 15, 2014 at 7:30 AM, Jeroen Hoek jer...@lable.org wrote: B 2014-12-15 12:41 GMT+01:00 Martin Grigorov mgrigo...@apache.org: B Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Mon, Dec 15, 2014 at 12:39 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: A On 15 December 2014 at 10:39, Stephen Connolly stephen.alan.conno...@gmail.com wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Vriendelijke groeten, Jeroen Hoek Lable ✉ jer...@lable.org ℡ 088 44 20 202 http://lable.org KvK № 55984037 BTW № NL8519.32.411.B.01 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action http://www.manning.com/templier/ Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
Re: [VOTE] Name our mascot: Shotgun vs The Maven Owl
B On 16.12.2014, at 08:41, Mikolaj Izdebski mizde...@redhat.com wrote: B On 12/15/2014 11:39 AM, Stephen Connolly wrote: After the run-off round, we are left with two names standing. This second vote will be a straight and simple majority wins. The vote will be open for at least 72 hours (with the potential of an extension until I send a message saying that the polls are closed) There will be no discussion in this thread, we have talked it all enough already. If you want to discuss something, please use a different thread. Vote: [A]: Shotgun [B]: The Maven Owl Thank you very much for your time -Stephen -- Mikolaj Izdebski Software Engineer, Red Hat - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
