diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-webteam/2011-January/000105.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-webteam/2011-January/000105.html')
| -rw-r--r-- | zarb-ml/mageia-webteam/2011-January/000105.html | 117 |
1 files changed, 117 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000105.html b/zarb-ml/mageia-webteam/2011-January/000105.html new file mode 100644 index 000000000..0fce14360 --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-January/000105.html @@ -0,0 +1,117 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-webteam] Webteam peers, bootstrapping + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Webteam%20peers%2C%20bootstrapping&In-Reply-To=%3CAANLkTinO8hSNSp6weq-cT4FX2i4rgcOWRhnGYzEV66VN%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000102.html"> + <LINK REL="Next" HREF="000098.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-webteam] Webteam peers, bootstrapping</H1> + <B>Romain d'Alverny</B> + <A HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Webteam%20peers%2C%20bootstrapping&In-Reply-To=%3CAANLkTinO8hSNSp6weq-cT4FX2i4rgcOWRhnGYzEV66VN%40mail.gmail.com%3E" + TITLE="[Mageia-webteam] Webteam peers, bootstrapping">rdalverny at gmail.com + </A><BR> + <I>Thu Jan 6 19:06:47 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000102.html">[Mageia-webteam] Webteam peers, bootstrapping +</A></li> + <LI>Next message: <A HREF="000098.html">[Mageia-webteam] Webteam peers, bootstrapping +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#105">[ date ]</a> + <a href="thread.html#105">[ thread ]</a> + <a href="subject.html#105">[ subject ]</a> + <a href="author.html#105">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, Jan 6, 2011 at 18:23, Maât <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-webteam">maat-ml at vilarem.net</A>> wrote: +>>><i> for example : forums we'll be deploying forums versions with git +</I>>><i> Ok, but that does not necessarily mean access to the server (this can +</I>>><i> be triggered indirectly). +</I>><i> Yup but this means coding yet an other specific wrapper ? +</I> +Hmm yes. That's maybe too soon. But that would allow to integrate with +a test suite on the test server (+ reporting + blocking production +push in case of tests failures). + +>>>><i>  * server deployment: +</I>>>>><i>    - staging from a branch available to all peers +</I>>><i> That is, ability to sync trunk (or whatever branch) to staging server. +</I>>><i> That's an option that allows everyone to see up-to-date working apps +</I>>><i> (and to quickly acknolewge broken ones). Or we can have a cron from +</I>>><i> VCS to staging. +</I>><i> +</I>><i> This imply limiting ourselves to one trunk and limiting our capacity to thread features developement nope ? +</I> +Somehow, yes. :-/ + +><i> I'd rather see a model with many trunks/tags/branches available for (one for each active dev) and ~user dirs allowing people to switch their personnal instance to the trunk/tag/branch they want to play with... +</I>><i> +</I>><i> for a given project we would have a SVN repos organization like that : +</I>><i> [...] +</I> +Well, that makes a lot of branches to create for each project and for +each new peer in a team. + +That's where I like git and even more tools such as gitorious/github +(everyone gets his own branches on his own public space and can push +their changes back). It automates some tedious parts. + +><i> Then for apache testing organization we could have : +</I>><i> <A HREF="http://thesdeverver.mageia.org/manager">http://thesdeverver.mageia.org/manager</A> => where $nickname can log on and click to switch it's own instance to what he wants (application,repository,tag or branch or trunk) +</I>><i> +</I>><i> <A HREF="http://the-dev-server.mageia.org/testing/~$nickname/">http://the-dev-server.mageia.org/testing/~$nickname/</A> => where he tests the application he just switched to +</I>><i> +</I>><i> what do you think ? +</I> +Hmmm why not. Will need some work for the testing deployment +(especially for db-based apps). + +As for the workflow, if it's not too inconsistent/repetitive (?): + * a dev (team peer or not) works on her platform, tests there; keeps +a branch on mageia.org; + * pushes changes for code review and merge into trunk (by any +available peer) from her branch; + * tests/staging are done with the trunk - if it breaks, it depends: +fix it easily/quickly or reverse the merge; + * the trunk is merged/branched in a production branch before being +moved to production server; + * production fixes are merged back into the trunk; + * and so on. + +This in the perspective of encouraging small features increments to be +pushed to production as soon as possible (instead of waiting of having +all pieces fall together). That's not a general rule of course but... +a preference. + + +Romain +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000102.html">[Mageia-webteam] Webteam peers, bootstrapping +</A></li> + <LI>Next message: <A HREF="000098.html">[Mageia-webteam] Webteam peers, bootstrapping +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#105">[ date ]</a> + <a href="thread.html#105">[ thread ]</a> + <a href="subject.html#105">[ subject ]</a> + <a href="author.html#105">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-webteam">More information about the Mageia-webteam +mailing list</a><br> +</body></html> |