Re: [gatein-dev] GIT migration

Thanks on the migration ! Was it tweeted already ? :) On 03/19/2012 11:49 AM, Boleslaw Dawidowicz wrote: > I think this translates to: Fell free to fork, clone, commit and issue > pull requests! :) > > Here is the basic doc about how we should proceed with Git for trunk: > > https://community.jboss.org/wiki/GateInPortalGitContributionGuide > > We are still missing some stuff like mailing list for pull requests > (working on it…) and we will probably need to adjust the whole process > over time as we learn about limitations. Fell free to comment and add > suggestions. > > As a side note - at the moment only 4 persons have permissions to push > into gatein-portal repo - me, Julien, Thomas and Trong. This is mainly > for the start and ideally over time we add more people as a > gatekeepers when we feel safer of not nuking up the repo by accident… > > We will try to follow with migration of other components shortly. > Schedule to be defined. > > I would like to thank Julien for leading this part of the migration, > investing his time and sharing expertise to drive it. > > Bolek > > On Mar 18, 2012, at 10:46 PM, Julien Viet wrote: > >> I've updated the repository with a new migration which is better >> because empty commits are removed (mostly svn:ignore commits) and >> more important the .gitignore file is added through the whole history >> (which means doing a checkout of an earlier version will have the >> .gitignore). >> >> it means that any fork of the previous version are not valid anymore >> and should be refreshed as history had to be rewritten (specially for >> putting .gitignore everywhere). >> >> Beside that, I've been able to capture the steps for migrating the >> repository and will provide them soon, they are fairly easy to use >> and actually I've been using them to make a prototype of portlet >> container migration here : https://github.com/vietj/pc-preview . >> >> >> >> On Mar 16, 2012, at 2:18 PM, Nick Scavelli wrote: >> >>> "cloning now"...can't wait until it's official ! Thanks Julien ! >>> >>> On 03/16/2012 04:46 AM, Julien Viet wrote: >>>> I created the repository as "candidate for release" : >>>> https://github.com/gatein/gatein-portal >>>> >>>> it will be officially the gatein portal repository monday. >>>> >>>> at the moment you can clone it (via git clone) but you should avoid >>>> to "fork" it the "github way" (if we need to recreate it for some >>>> reason, your fork will be lost). >>>> >>>> please have a look, clone it, play with it, build it, etc... >>>> >>>> thanks for your feedback. >>>> >>>> On Mar 15, 2012, at 3:12 PM, Boleslaw Dawidowicz wrote: >>>> >>>>> I cut off write access to: >>>>> >>>>> https://svn.jboss.org/repos/gatein/portal/trunk >>>>> >>>>> Julien will be starting migration process to github. This should >>>>> hopefully take us around 2 days to test everything properly. We >>>>> aim to be able to continue with access to the new repo on github >>>>> around Monday morning. >>>>> >>>>> I will try to provide basic documentation covering source code >>>>> contribution to the project by then. >>>>> >>>>> Please tell me if you have any serious reasons to re-enable svn >>>>> access to gatein/portal/trunk. >>>>> >>>>> Bolek >>>>> >>>>> On Mar 15, 2012, at 9:51 AM, Julien Viet wrote: >>>>> >>>>>> portal vn team is fine. >>>>>> >>>>>> On Mar 15, 2012, at 9:46 AM, Boleslaw Dawidowicz wrote: >>>>>> >>>>>>> Does anyone have any pending work for portal/trunk? If now i >>>>>>> would like to turn it into readOnly mode today. Please let me know. >>>>>>> >>>>>>> Bolek >>>>>>> >>>>>>> On Mar 14, 2012, at 6:48 PM, Ken Finnigan wrote: >>>>>>> >>>>>>>> Would need to add: >>>>>>>> >>>>>>>> .settings >>>>>>>> .project >>>>>>>> .classpath >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Mar 14, 2012 at 1:37 PM, Julien Viet >>>>>>>> <julien@julienviet.com<mailto:julien@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@lists.jboss.org<mailto:gatein-dev@lists.jboss.org> >>>>>>>> https://lists.jboss.org/mailman/listinfo/gatein-dev >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> gatein-dev mailing list >>>>>>>> gatein-dev@lists.jboss.org<mailto:gatein-dev@lists.jboss.org> >>>>>>>> https://lists.jboss.org/mailman/listinfo/gatein-dev >>>> >>>> >>>> _______________________________________________ >>>> gatein-dev mailing list >>>> gatein-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/gatein-dev > > > _______________________________________________ > gatein-dev mailing list > gatein-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/gatein-dev _______________________________________________ gatein-dev mailing list gatein-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/gatein-dev