That sounds very reasonable... Thanks, Pei -----Original Message----- From: Jörn Kottmann [mailto:[email protected]] Sent: Wednesday, July 25, 2012 5:49 PM To: [email protected] Subject: Re: podling release managment
You have to add the incubating flag to the version, so the release version could be 2.6-incubating. If you reset you version number and start at 0.0.1 many people would be confused. Which is newer 2.5 or 0.0.1? Jörn On 07/25/2012 11:35 PM, Chen, Pei wrote: > Thanks. > While we wait for infra to import the svn dump file > (https://issues.apache.org/jira/browse/INFRA-5079), > what would you suggest we call this upcoming release (aka. what would > have been called 2.6 in sourceforge [with old package names and structure, > etc].) Should we start using standard release names such as: > apache-ctakes-0.1.0-incubating? > > > > -----Original Message----- > From: Jörn Kottmann [mailto:[email protected]] > Sent: Wednesday, July 25, 2012 5:24 PM > To: [email protected] > Subject: Re: podling release managment > > On 07/25/2012 11:17 PM, Chen, Pei wrote: >> I just stumbled across this and thought it may be a good read for those >> involved... >> http://incubator.apache.org/guides/releasemanagement.html >> > This is an important part of the release to get right: > http://incubator.apache.org/guides/releasemanagement.html#best-practic > e-license > > The LICENSE and NOTICE files must contain information about the 3rd party > stuff you ship with your release, if something is missing there you will > likely not get the release through the Incubator vote. > > Jörn
