[gatein-dev] GIT migration

[Ken Finnigan]

Would need to add:

.settings
.project
.classpath


On Wed, Mar 14, 2012 at 1:37 PM, Julien Viet <julien at julienviet.com> wrote:

> For eclipse users : anything you want to add in .gitignore for Eclipse ?
>
> On Mar 13, 2012, at 11:30 PM, Julien Viet wrote:
>
> > Hi,
> >
> > we are going to migrate the GateIn Portal repository to GIT soon
> (hopefully by next week) and here is the process we should follow:
> >
> > 1/ provide an initial repository (by me) as preview to play with it and
> check things are OK (identities, tags).
> > 2/ stop SVN commits by the end of this week (which means that people
> having pending commits will have to flush them before the end of this week).
> > 3/ the new repository should be available in GitHub early next week,
> ready to be used in the GateIn organization in a repository named
> "gatein-portal".
> >
> > We want to use GIT in order to keep a trunk as stable as possible and
> the main motivation is to never have "unfinished" work in the master of the
> repository:
> > - a long feature does not have to be entirely finished of course to go
> in master but it should reach a certain milestone in its implementation.
> > - a small feature should be finished and then merged in the master.
> > - bug fixes can go directly in the master as they are independant.
> >
> > Git provides a huge benefit over SVN : it allows to schedule when
> commits are merged in the master without blocking other people to work. We
> will use this
> > feature to "implement" the behavior explained before.
> >
> > After the 3.2 release, we want to increase our release rate with GateIn
> 3.3, 3.4, etc.. We think we should be able to make up to 4 releases a year
> (as opposed to
> > a single release in almost 2 years which means an x8 factor). We also
> think that using correctly Git will help us to do that (also with a proper
> management of
> > the roadmap and dependencies between features of course). The idea is to
> focus on a few selected features in the master at a time for the next
> release and
> > keep the other in other branches (TBD).
> >
> > We will clarify how people can work with this repository soon, but in
> short at the beginning only a few persons will interact directly with the
> repository. We will
> > use the "pull request" mechanism of Git to notify when a merge should be
> done (to be clarified by Bolek soon). Also here the idea is that we will
> schedule
> > pull request at the appropriate time.
> >
> > So this is valid at the moment for the portal project, other project
> will be migrated later (during March/April), at the moment we focus on the
> portal because it's
> > the place where the main activity is done at the moment. Other project
> will have likely similar rules but it will be less strict since it's
> usually used by less people
> > than the portal.
> >
> > So tonight I'm providing a repository preview
> https://github.com/vietj/gatein-portal-preview for the portal that
> contains the SVN history and the released tags
> >
> > - it does not contain branch information (since we don't use them for
> the community versions).
> > - you should check the repository (like using a tag and building it).
> > - you must check your identity was correctly migrated (based on the
> information you provided) : if it is not tell me what is your Git identity.
> > - the .gitignore file was not added yet, I will add it later (likely
> like this one https://github.com/juzu/juzu/blob/master/.gitignore) : if
> you have specific desire tell me
> > - the maven release plugin is not yet updated to use Git and it will be
> done later (and actually it should be updated to release things more
> correctly).
> >
> > if you feel something is missing or have question, don't hesitate to
> raise the concern.
> >
> > cheers
> >
> > Julien
> >
>
>
> _______________________________________________
> gatein-dev mailing list
> gatein-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/gatein-dev/attachments/20120314/6fbabc2e/attachment.html