Moreover, rock-core has not seen much progress since rock1408. This is a discussion that I wanted to have (within the "how to release" discussion): why not find a way to separate rock-core and other package's release schedule. As Rock matures, the need for full-fledged rock-core releases should get lower and lower, while packages (hopefully) will see a lot of progression.
Sylvain On Thu, Jan 15, 2015 at 1:46 PM, Jakob Schwendner <[email protected]> wrote: > I would prefer to wait with the releases until we have the way we do the > releases ironed out. > Its still in the process of being implemented. > > Cheers, > > jakob > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On >> Behalf Of Matthias Goldhoorn >> Sent: Donnerstag, 15. Januar 2015 15:59 >> To: [email protected] >> Subject: [Rock-dev] Release cycle triggern before orogen_loader merge? >> >> Dear dev's, >> In general i would really like to have a merge of orogen_loader, but do we >> want to make a release before this merge? >> Our last release was 1408, i would really like to have a release 'now' >> before the merge. >> >> Suggestions? >> >> Best, >> Matthias >> >> P.S. is rock-simulation already part of the release cycles? > > > _______________________________________________ > Rock-dev mailing list > [email protected] > http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev _______________________________________________ Rock-dev mailing list [email protected] http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
