ASF releases must include source Sent from my mobile device (so please excuse typos)
On 19 May 2011, at 08:13, Chapuis Bertil <[email protected]> wrote: > Sorry for such a question, but I'm not sure to understand why we need a zip > for the source release, since we already have the jars generated by the > maven source plugin. > > About the site, the trunk contains the forrest documentation and the > foundation for using the maven site plugin (src/site). It seems that storing > the site in the src folder is a common practice but if the source archive is > required, having two sites in it is not good. > > > On 18 May 2011 22:54, Richard Frovarp <[email protected]> wrote: > >> On 05/18/2011 03:44 PM, Eugen Paraschiv wrote: >> >>> I've been using the new incubator code for this past few days, without any >>> discernible *functional *problems for me. The 7 days voting period is >>> getting close to the end, what is the next step from here? >>> Thanks for moving this forward. >>> Eugen. >>> >>> >> Glad to hear. Personally, I'm not happy with the actual release artifacts. >> I should have paid closer attention when generating them. If anyone has >> feedback on what needs to change in the release artifacts, that would be >> great. >> >> I've already fixed the missing license headers in trunk. >> >> I've moved the code modules out of trunk that aren't referenced in the root >> pom. >> >> I will do a clean checkout so there isn't extra SVN crap in the source >> file. >> >> The one piece that is still missing is moving the website out of trunk. If >> this isn't done, we're shipping our website in the source archives that are >> made available for download. >> >> > > > -- > Bertil Chapuis > Agimem Sàrl > http://www.agimem.com
