There are several config change requests which are usually merged within few hours. The current process is that someone submit a patch which is directly merged to production, ignoring any staging platform at all.
What we can do now, is to copy paste the diff and merge it by hand into wmf-config files in labs, just to test if configuration change is ok. What I want to do: Making a new branch would allow us to use gerrit to do this hand work for us. We would approve the change to production config on test branch, so that gerrit would merge it. Then we would checkout on labs and we could test the configuration change there, before putting it to production. In case it is ok, then we could give it green on gerrit and merge it on production. On Sat, Jun 30, 2012 at 1:51 AM, Antoine Musso <[email protected]> wrote: > Le 29/06/12 18:36, Petr Bena wrote: >> But that's a lot of hand work, if we really do this, we won't use >> gerrit at all, we just copy paste code from diffs by hand and insert >> it to some extra files. I would rather volunteer to sync branches >> rather than this creep work. > > What hand work are you referring to? copy/paste in git world is > something like: > > # Copy: > git fetch <repo> <ref> > # Paste: > git merge FETCH_HEAD > > Anyway, anyone can clone the repository and do their stuff on their own. > That is defacto a branch (your master is not the WMF master, it is a > copy). A local commit can be distributed to over people via Gerrit. > > -- > Antoine "hashar" Musso > > > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
