On Nov 2, 2014, at 4:18 PM, Carsten Haitzler (The Rasterman) <[email protected]> wrote:
> On Sat, 1 Nov 2014 23:03:59 -0700 Nex6|Bill <[email protected]> said: > >> I see, E17 still used, i places like FreeBSD, OpenBSD and Bodhi but E19 is >> in “released” mode. so, what would be the the stable, unstable and dev >> branches? > > master == development and what becomes the next stable release. > > tags == a bunch of tags indicating that revision number was used for that > release. > > branches == each stable release gets a branch - eg like enlightenment-0.17 , > enlightenment-0.18, enlightenment-0.19 ... same for efl, elementary etc. > (efl-1.8, efl-1.9, efl-1.10, efl-1.11). these branches accumulate patches > (mostly cherrypicked from mater commits) and then get releases like 1.11.2, > 0.19.1, etc. etc. > > it's a pretty simple system. master is the new hotness. branches are where > stable releases live. tags are us ... tagging things that are released. > > we have a schedule for releases for efl (not e): > > https://phab.enlightenment.org/w/release_roadmap/ > > 12 week cycle. > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) [email protected] > so; each “branch” E17, E18, E19 would be considered “stable” but the verious OS teams and packaging teams are just being very conservative in staying with E17. since its the sort of proven stable, and the dependancies may be easier to target. -Nex6
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
