Heh. Val, couple cases in point:
1. That process you mention below is precisely the process, save, making an *extra* tag of e.g., 1.0-rc3 as 1.0. We only release bits that we have all VOTEd on and those bits must map to a tag in SVN. Whether I call the tag foo-bar-12, or 1.0-rc3, and/or 1.0, we do have an ASF foundation “best practice” I’ll call it to make sure the emails/VOTEs that are done formally by PMC members map to something that we can dig up and that still exists, so having tags that map to RCs, which when there are more +1s than -1s, and when the RM’s specified time elapses (72 hours or later is a good default) is something that the RM must do. Here’s our fun release process: https://cwiki.apache.org/confluence/display/OODT/Release+Process You can see what steps we’ve gone through. 13 sort of “leaves it up to the RM” when it comes to naming the actual SVN tag which is part of what’s being VOTE’d on in the RC email. However, later in step 27 looking at the VOTE email, it implies we have a <version>, which if you look at the history of our tags http://svn.apache.org/repos/asf/oodt/tags/ Has besides 0.8.1 and 0.9 mostly just been the actual version # that’s part of Maven, you’ll see it’s been pretty consistent. The last two releases, I wanted to throw the rc1 in there to make it obvious that this was an RC #1. (since I realized we weren’t doing a good job of making that part explicit). In doing so, though, I’ve created some confusion for you, so sorry about that. It’s easy enough to simply type: [mattmann-0420740:~] mattmann% svn -m "0.9 version tag - without RC" copy https://svn.apache.org/repos/asf/oodt/tags/0.9-rc1 https://svn.apache.org/repos/asf/oodt/tags/0.9 Committed revision 1684486. [mattmann-0420740:~] mattmann% svn -m "0.8.1 version tag - without RC" copy https://svn.apache.org/repos/asf/oodt/tags/0.8.1-rc1 https://svn.apache.org/repos/asf/oodt/tags/0.8.1 Committed revision 1684487. And then create those :) Any PMC member has the ability to do this. Sorry to create confusion but hopefully you understand the rationale. Now we’re both happy. Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: <Mallder>, Valerie <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, June 9, 2015 at 10:21 AM To: "[email protected]" <[email protected]> Subject: RE: 0.9-rc1 tag name >Here's the visual ... my jaw in totally on the floor. It never occurred >to me that something named 'release candidate' would be an 'official' >release. So, this explains why I spent a good two weeks trying to get >0.8.1 to work, couldn't get it working, and ended up backing out all of >my stuff and going back to 0.8 because I knew how to get that version >working. I had absolutely no idea that 0.8.1-rc1 was the REAL release of >0.8.1. The release was called '0.8.1' so I checked everything out from >the 0.8.1 tag. > >I would hate for someone to make the same mistake I did. I get that svn >tags are separate from maven version numbers. But, being consistent with >things like this is rarely a 'bad' thing to do, and often times, it >really helps. Especially for new people who are not familiar with the >system and just trying to understand it. If I could make a >recommendation to the next RM it would be to do something like: > >Make a 1.0-rc1 - does everyone like it? No >Make a 1.0-rc2 - does everyone like it? No >Make a 1.0-rc3 - does everyone like it? Yes >Make a 1.0 (this is just a copy of 1.0-rc3, but it is absolutely clear >what release it really is) > >This would address the desire to save a history of all the release >candidates (not sure why you need that, but ok), and provide the user >with a release that is clearly not a 'candidate' for release, but >something that has actually 'been' released. > >Nonetheless, Thanks for letting me know. I will never again assume that >the svn tag matches the release name. How silly of me! > > > > >Valerie A. Mallder >New Horizons Deputy Mission System Engineer >Johns Hopkins University/Applied Physics Laboratory > > >> -----Original Message----- >> From: Chris Mattmann [mailto:[email protected]] >> Sent: Tuesday, June 09, 2015 11:51 AM >> To: [email protected] >> Subject: Re: 0.9-rc1 tag name >> >> Ahh, yeah it’s b/c the tag doesn’t necessarily have to match the >>version # - Maven >> versions are separate from SVN tag #s are separate from..well you get >>it :) >> >> I think while it may be divorced from the actual build system in some >>minor way, >> one thing that it does provide is provenance of how many RCs we’ve had >>to do >> and in the past it’s usually 1, but we’ve had cases, where it’s been 2 >>or 3 and we’ve >> lost the provenance if it’s just <X.Y> version (but what RC?) >> >> Anyhoo, I digress - hopefully 0.10 is just, well, 0.10. The next RM if >>it’s not me, is >> welcome to decide. ^_^ >> >> Cheers >> Chris >> >> >> >> >> -----Original Message----- >> From: "Mallder, Valerie" <[email protected]> >> Reply-To: <[email protected]> >> Date: Tuesday, June 9, 2015 at 8:23 AM >> To: "[email protected]" <[email protected]> >> Subject: RE: 0.9-rc1 tag name >> >> >Ok, it's just inconsistent with the release number that is on all the >> >jar files, etc. So it has the potential to cause confusion. It >> >confused me because when I went to run the radix script just now, (not >> >knowing entirely how everything works) I wasn't sure if I needed to >> >change the version that is specified in the script to be 0.9-rc1 >>instead of 0.9. >> >Just sayin ... :) >> > >> > >> > >> >Valerie A. Mallder >> >New Horizons Deputy Mission System Engineer Johns Hopkins >> >University/Applied Physics Laboratory >> > >> > >> >> -----Original Message----- >> >> From: Mattmann, Chris A (3980) [mailto:[email protected]] >> >> Sent: Tuesday, June 09, 2015 10:38 AM >> >> To: [email protected] >> >> Subject: Re: 0.9-rc1 tag name >> >> >> >> Hi Val, >> >> >> >> Nope, tags are immutable, so keeping it that way. I decided to >> >>include the RC this time (have done so in some prior releases). >> >> >> >> Cheers, >> >> Chris >> >> >> >> >> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> +++++ >> >> Chris Mattmann, Ph.D. >> >> Chief Architect >> >> Instrument Software and Science Data Systems Section (398) NASA Jet >> >> Propulsion Laboratory Pasadena, CA 91109 USA >> >> Office: 168-519, Mailstop: 168-527 >> >> Email: [email protected] >> >> WWW: http://sunset.usc.edu/~mattmann/ >> >> >> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> +++++ >> >> Adjunct Associate Professor, Computer Science Department University >> >> of Southern California, Los Angeles, CA 90089 USA >> >> >> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> +++++ >> >> >> >> >> >> >> >> >> >> -----Original Message----- >> >> From: <Mallder>, Valerie <[email protected]> >> >> Reply-To: "[email protected]" <[email protected]> >> >> Date: Tuesday, June 9, 2015 at 7:31 AM >> >> To: "[email protected]" <[email protected]> >> >> Subject: 0.9-rc1 tag name >> >> >> >> >Hi Chris, >> >> > >> >> >Is the current tag '0.9-rc1' going to change to '0.9'? >> >> > >> >> >Val >> >> > >> >> > >> >> > >> >> > >> >> >Valerie A. Mallder >> >> >New Horizons Deputy Mission System Engineer Johns Hopkins >> >> >University/Applied Physics Laboratory >> >> > >> >> > >> >> >> -----Original Message----- >> >> >> From: Mattmann, Chris A (3980) >> >> >>[mailto:[email protected]] >> >> >> Sent: Tuesday, June 09, 2015 10:06 AM >> >> >> To: Mallder, Valerie; [email protected] >> >> >> Cc: Wyngaard, Jane R (3980-Affiliate); Starch, Michael D (398M); >> >> >>Kristian ZARB ADAMI; Ramirez, Paul M (398M); Alessio Magro >> >> >> Subject: Re: OODT Documentation >> >> >> >> >> >> Sigh, sorry Val: >> >> >> >> >> >> [chipotle:~/tmp/oodt0.9] mattmann% svn commit -m "Finally fully >> >> >>implement >> >> >> OODT-785 and get the batch stub legacy mode props in there. Thanks >> >> >>to Val." >> >> >> Sending >> >> >> >> >> >>mvn/archetypes/radix/src/main/resources/archetype-resources/resmgr/ >> >> >>src >> >> >>/ma >> >> >>in >> >> >> /resources/bin/batch_stub >> >> >> Transmitting file data . >> >> >> Committed revision 1684425. >> >> >> [chipotle:~/tmp/oodt0.9] mattmann% >> >> >> >> >> >> >> >> >> Looking at: >> >> >> http://svn.apache.org/viewvc?view=revision&revision=1637785 >> >> >> >> >> >> >> >> >> I see that this was only done and committed in the resmgr code for >> >> >>trunk and not in OODT RADIX. Anyways, above I just committed it in >> >> >>RADIX. Ugh, sorry for that. >> >> >> Happy to make a point release if needed for an 0.9.1. >> >> >> >> >> >> Cheers, >> >> >> Chris >> >> >> >> >> >> >> >> >> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> +++++ >> >> >> Chris Mattmann, Ph.D. >> >> >> Chief Architect >> >> >> Instrument Software and Science Data Systems Section (398) NASA >> >> >> Jet Propulsion Laboratory Pasadena, CA 91109 USA >> >> >> Office: 168-519, Mailstop: 168-527 >> >> >> Email: [email protected] >> >> >> WWW: http://sunset.usc.edu/~mattmann/ >> >> >> >> >> >> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> +++++ >> >> >> Adjunct Associate Professor, Computer Science Department >> >> >> University of Southern California, Los Angeles, CA 90089 USA >> >> >> >> >> >> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> +++++ >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -----Original Message----- >> >> >> From: <Mallder>, Valerie <[email protected]> >> >> >> Date: Tuesday, June 9, 2015 at 6:59 AM >> >> >> To: "[email protected]" <[email protected]>, jpluser >> >> >><[email protected]> >> >> >> Cc: "Wyngaard, Jane R (3980-Affiliate)" >> >> >><[email protected]>, "Starch, Michael D (398M)" >> >> >><[email protected]>, Kristian ZARB ADAMI >> >> >><[email protected]>, "Ramirez, Paul M (398M)" >> >> >> <[email protected]>, Alessio Magro <[email protected]> >> >> >> Subject: RE: OODT Documentation >> >> >> >> >> >> >If you are using the RADiX archetype, make sure the following two >> >> >> >lines are in the batch_stub script The batch_stub script is >> >> >> >located >> >>at: >> >> >> >oodt/resmgr/bin. >> >> >> > >> >> >> >-Dorg.apache.oodt.cas.pge.task.metkeys.legacyMode="true" \ >> >> >> >-Dorg.apache.oodt.cas.pge.task.status.legacyMode="true" \ >> >> >> > >> >> >> >I just checked here >> >> >> > >> >> >> >http://svn.apache.org/viewvc/oodt/tags/0.9-rc1/mvn/archetypes/rad >> >> >> >ix/ >> >> >> >src >> >> >> >/ma >> >> >> >> >> >>>in/resources/archetype-resources/resmgr/src/main/resources/bin/bat >> >> >>>ch_ >> >> >>>stu >> >> >>>b? >> >> >> >view=markup >> >> >> > >> >> >> >and see that it batch_stub in the RADiX archetype is still >> >> >> >missing those two lines. JIRA issue OODT-785 is marked fixed in >> >> >> >0.8, but it was never been implemented in the RADiX archetype. >> >> >> > >> >> >> >Val >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> >Valerie A. Mallder >> >> >> >New Horizons Deputy Mission System Engineer Johns Hopkins >> >> >> >University/Applied Physics Laboratory >> >> >> > >> >> >> >> -----Original Message----- >> >> >> >> From: Andrea DeMarco [mailto:[email protected]] >> >> >> >> Sent: Tuesday, June 09, 2015 9:44 AM >> >> >> >> To: Mattmann, Chris A (3980) >> >> >> >> Cc: Wyngaard, Jane R (3980-Affiliate); Starch, Michael D >> >> >> >>(398M); Kristian ZARB ADAMI; Ramirez, Paul M (398M); Alessio >> >> >> >>Magro; [email protected] >> >> >> >> Subject: Re: OODT Documentation >> >> >> >> >> >> >> >> Hi Chris, >> >> >> >> >> >> >> >> Yup, the jar file is present in both resmgr/lib and >>workflow/lib. >> >> >> >>You can have a look at my JAR contents at: >> >> >> >> >> >> >> >>>>https://www.dropbox.com/s/1h0siibxf8sv5ut/fileconcatenator-pge-1.0. >> >> >> >>jar >> >> >> >>?dl >> >> >> >>=0 >> >> >> >> - perhaps something's off there? >> >> >> >> >> >> >> >> Cheers, >> >> >> >> Andrea >> >> > >> > >> >
