I would like to second what Eugene said about the New and Noteworthy Features page -- many of us are looking to this web page to learn of both new releases (and dev releases) as well as new features:
<http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy> It would be fairly difficult to glean the same information from the JIRA for m2eclipse. Thanks for all of the great efforts in producing m2eclipse! Eugene Kuleshov wrote: > > Jason van Zyl wrote: >>> I haven't been involved with the recent changes in m2eclipse code. It >>> would be great to inform m2eclipse community with an overview of the >>> changes and major fixes included in this dev build. >>> Also, it seems like the following checklist haven't been done for >>> this dev build: >>> >>> * the wiki page is not updated with build id >>> http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy >> I will start using JIRA to create the reports for the releases. We're >> going to start doing what we do for Nexus. > In the past people been asking what is the latest version published, > so we started to keep track of this on that wiki page (at very top). > That wiki page alsos help to match the published builds with the > visuals and important changes described in the New and Noteworthy. I > don't believe jira would be good for such purpose. >>> * there is no tag in svn for this build >> For non release dev builds my tools actually copies out the binaries >> that are produced so they are in effect kept forever. I will turn on >> directory listings so that people can grab them individually. What I >> will add is either a tag or a revision so that folks can build from >> source if they choose. I'll do that for the 0.9.7. > Sorry, I am not following. We still need a tag in version control for > every published build in order to be able to identify which source code > corresponds to any given build. Also builds been archived on Hudson so > we had the binaries and the tags intact. >>> https://svn.sonatype.org/m2eclipse/tags >>> * ci job on hudson is not marked to be kept forever and don't have >>> corresponding build id in description >>> https://ci.sonatype.org/job/m2eclipse-with-e33/622/ >>> >>> Can you please arrange required corrections to address these issues >>> before code in trunk is changed? That would allow us to have a good >>> tracking record. > regards, > Eugene > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://www.nabble.com/Dev-Build-Release-tp21841983p21890712.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
