Hi Martin; Am Donnerstag, 29. Dezember 2016, 22:39:56 schrieb Martin Hejl: > Hi kp, > > >> In short, replace "0.1.0" with "0.2.0": > >> (...) > > > > fixed in git. > > From what I can see, only in "maint", but not in "master" (unless git > handles that automagically - which I wouldn't know about, since I'm > totally clueless when it comes to git...). Just to be sure that doesn't > come up again in the next release.
The maint repo holds the latest stable major version (6.0.x) currently. It should be the place for mostly bugfixes, security fixes and other maintenance tasks. The master repository is our development area for next major version. Here we place major/core updates. >From time to time we do a merge from maint to master to make shure fixes (like the one for libmnl) will be available in master as well. The next stable release will be based on maint; a release from master (which will be 6.1.0 then) happens every 12 to 13 month, if I look back into the history since 4.0. > >> P.S. Is it correct that none of the packages for 6.0.1 are in the > >> packages repository so far? Or am I just looking in the wrong spot? > > > > You haven't looked int the wrong spot; I hesitated to provide the packages > > yet, minor issue is time, major issue is that the packages repository is > > the base if running upgrade from the router and 5.2.8 releases will fail > > to load after upgrade, if the user does not take of the changes in > > syslinux.cfg. > > > > And most important, it is a good time to rethink the repository layout. > > It occured that adding new directories might not the way to go with git - > > it will probably easier to have a more flat one and use tags etc... > > I also feel the need to provide packages in the packages repository, so > > rework the repo layout should be moved until 6.1.x is going live > > > > No decision made yet.... > > Ah, ok - thanks for clarifying. It's a bit confusing for somebody coming > back after several years of not touching the bering uClibc installs > (since they just worked flawlessly), so I wanted to be sure I didn't > miss anything. > > One more thing - maybe the landing page on http://leaf.sf.net/ should be > updated to contain a link to > > http://leaf.zetam.org/bering-uclibc/ > and > https://bering-uclibc.zetam.org/wiki/Main_Page > > since the project looks a bit abandoned to anybody just looking at the > SourceForge site (https://sourceforge.net/projects/leaf/ links to the > proper sites, but http://leaf.sf.net doesn't) Unfortunately the landing site out of reach for us. Mike Noys is the only one with access right AFAIK. kp > Martin > > ---------------------------------------------------------------------------- > -- Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > ------------------------------------------------------------------------ > leaf-user mailing list: leaf-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
