On Wed, Jan 29, 2020 at 4:00 PM Zoran Regvart <zo...@regvart.com> wrote: > > +1 > > On Wed, Jan 29, 2020 at 10:42 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > > It will also have us to update the examples to run individually and > > use Camel BOM instead of being tied to Camel source. Which means the > > examples would be better practice. > > Would we keep branches with examples corresponding to Camel version? > How would this affect the release process? >
IMHO we would not do releases of the examples as a binary or to maven central etc. We can instead just branch and tag in git, and then people can checkout what version they want to play/use. So there is a 3.1.0 tag, and 3.1.x branch. > > So to get this started before Camel 3.1 release then I think we should > > have INFRA setup the git repo, and then we can start moving the code > > over, and migrate them. We can get help from people in the community > > etc for some of the migration effort etc. > > We can self-provision git repositories, I don't think there's a need > for an INFRA ticket. > > > I suggest the repo name is camel-examples > > eg ending with an s (to indicate we have many examples). As singular > > like camel-example seems wrong and imply its just a single example of > > some sorts. > > +1 > > zoran > -- > Zoran Regvart -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
