The name "trunk" for the part that's synchronized with Git was extremely bad, don't think that was a mandatory requirement or seriously INFRA's recommendation to do that, but let's hope these things can get untangled soon[?]
I recall DeltaSpike has quite a few Git repos. Same for PhoneGap/Cordova from what I've seen. Cheers, Werner On Thu, Jul 17, 2014 at 3:25 PM, Radu Cotescu <[email protected]> wrote: > Hi Werner, > > As discussed before [0], we need that structure for the TravisCI > integration [1]. If the project graduates we could ask for multiple > repositories (I'm thinking of a main GitHub repo with several repos hosting > sub-modules like browsermap, for example) in order to get rid of the > sub-tree you don't like that much. > > However, until then, following INFRA's recommendation is the way to go for > now. Tagging browsermap milestones under the browsermap/tags structure also > provides us with automatically imported tags on GitHub [2]. > > Also, now there's a README.md [3] file in the repo that tries to clarify > the ambiguities of that sub-tree. > > Cheers, > Radu > > [0] - http://markmail.org/message/wraggdgsab2utkl7 > [1] - https://travis-ci.org/apache/devicemap-browsermap/builds > [2] - https://github.com/apache/devicemap-browsermap/releases > [3] - > http://svn.apache.org/viewvc/incubator/devicemap/trunk/browsermap/README.md?view=markup > > > On Thu, Jul 17, 2014 at 1:00 PM, Werner Keil <[email protected]> > wrote: > >> Assuming this happens >> >> Once the release is approved we have to: >> 1. bump the version to 1.4.1 in the module's package.json file >> *2. tag the release >> under https://svn.apache.org/viewvc/incubator/devicemap/tags/releases/ >> <https://svn.apache.org/viewvc/incubator/devicemap/tags/releases/>browsermap-1.4.1* >> >> (the /trunk/trunk is highly disturbing, but /trunk/tags is even worse, it >> creates a "parallel universe" for BrowserMap that's confusing to any >> potential adopter who checks out all or most of the SVN codebase[?]) >> >> I am fine to stick to my +1. >> >> I haven't studied a graduation path upfront, but assuming the >> /incubator/devicemap may be replaced by something without /incubator if >> graduation was successful, please let's clean this mess no later than >> graduation for browsermap[?] >> >> Thanks, >> Werner >> >> >> On Wed, Jul 16, 2014 at 4:33 PM, Kevan Miller <[email protected]> >> wrote: >> >>> Looks good. Thanks Radu! >>> >>> +1 >>> >>> --kevan >>> >>> >>> On Wed, Jul 16, 2014 at 5:16 AM, Radu Cotescu <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I've staged another set of release artifacts. @Kevan, @Bertrand, could >>>> you please check that everything's ok this time? >>>> >>>> Staging URL: https://people.apache.org/~radu/browsermap/ >>>> >>>> The project's keys file is available at: >>>> https://people.apache.org/keys/group/devicemap.asc >>>> >>>> In case you need to import the keys, after downloading the keys file, >>>> run the following command: >>>> gpg --import devicemap.asc >>>> >>>> You can use this UNIX script to download the release and verify the >>>> signatures: >>>> http://svn.apache.org/repos/asf/incubator/devicemap/trunk/check_staged_release.sh >>>> >>>> Usage: >>>> sh check_staged_release.sh https://people.apache.org/~radu/browsermap/ >>>> >>>> An Apache Creadur Rat exclude file is provided at >>>> http://svn.apache.org/repos/asf/incubator/devicemap/trunk/browsermap/trunk/rat.exclude >>>> . >>>> >>>> To check the licensing compliance you could run the following command >>>> after expanding the browsermap-1.4.1-rc1-incubating.tar.gz archive: >>>> java -jar apache-rat.jar -E browsermap-1.4.1-rc1-incubating/rat.exclude >>>> -d browsermap-1.4.1-rc1-incubating >>>> >>>> The current artifacts correspond to tag >>>> http://svn.apache.org/viewvc/incubator/devicemap/trunk/browsermap/tags/browsermap-1.4.1-rc1/ >>>> . >>>> >>>> Once the release is approved we have to: >>>> 1. bump the version to 1.4.1 in the module's package.json file >>>> 2. tag the release under >>>> https://svn.apache.org/viewvc/incubator/devicemap/tags/releases/ >>>> browsermap-1.4.1 >>>> 3. upload the new artifacts to the dist location >>>> >>>> Please vote to approve this release: >>>> [ ] +1 Approve the release >>>> [ ] 0 Don't care >>>> [ ] -1 Don't release, because ... >>>> >>>> Regards, >>>> Radu >>>> >>>> >>>> On Wed, Jul 16, 2014 at 12:42 PM, Werner Keil <[email protected]> >>>> wrote: >>>> >>>>> Thanks for bringing that up here. >>>>> >>>>> RAT among other plugins is in those top level POMs, so projects that >>>>> wish to do can run such screenings on a regular basis[?] >>>>> >>>>> As the W3C library is now used in binary form (JAR) I don't expect >>>>> issues in any of the Java components including those using W3C right now. >>>>> >>>>> Werner >>>>> >>>>> On Wed, Jul 16, 2014 at 8:58 AM, Bertrand Delacretaz < >>>>> [email protected]> wrote: >>>>> >>>>>> On Tue, Jul 15, 2014 at 11:19 PM, Radu Cotescu <[email protected]> >>>>>> wrote: >>>>>> > Please vote to approve this release... >>>>>> >>>>>> So -1 for now, until we clarify the RAT issue and whether we can >>>>>> remove "derived" files from the release. >>>>>> >>>>>> -Bertrand >>>>>> >>>>> >>>>> >>>> >>> >> >
