On 1 July 2011 12:21, Andy Green <andy.gr...@linaro.org> wrote: > On 07/01/2011 08:14 PM, Somebody in the thread at some point said: > >> What I'd like to see is a a separate set of official trees that only >> get updated with bits that >> we are ready for non-Linaro developers to use, do not get rebased, and >> get tagged at the >> end of each monthly cycle. My proposal: >> >> kernel/linux-linaro-$version with tags for each monthly release: >> v$version-$milestone-$buildcount >> kernel/linux-linaro-android-$version with tags for each monthly >> release: android-v$version-$milestone-$buildcount >> kernel/$soc/linux-linaro-$version with tags for each monthly release: >> $bsp-v$version-$milestone-$buildcount >> kernel/$soc/linux-linaro-android-$version with tags for each monthly >> release: $bsp-android-v$version-$milestone-$buildcount >> >> Comments? > > It would be less ridiculous than issuing monthly tarballs for the kernel > case.
We'd still release tarballs with this naming scheme, it would just be that the git tree locations would be consistent across all LTs. ~Deepak _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
