You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Hadrian Zbarcea <hz...@gmail.com> on 2015/11/20 17:02:30 UTC
[QUESTION] Rewriting history
Probably a bad subject in the context of other things going on :).
Apache Brooklyn is faced with the tasks of migrating it's repo(s) post
graduation and there are some very large *pre-incubation* artifacts in
the git repo that we would like removed.
The question was asked on general@ [1] many moons ago, but received no
answer (the original thread [1] indicates the offenders). We'd like to
use this occasion to split the git repo into multiple smaller once (more
naturally tailored to the project), so one idea would be, I think, to
leave incubator-brooklyn.git as is and just extract what we need
(everything except the large binaries) in new repos. Note: afaiui, those
artifacts we're never part of an ASF release.
I am not sure what would be acceptable per ASF (intensely debated) policies.
Thoughts?
Hadrain
[1]
https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201506.mbox/%3C556F0973.7030504@CloudsoftCorp.com%3E
Re: [QUESTION] Rewriting history
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
To me, binaries not released by the ASF should not be necessary to keep
in multiple repos so this is a project PMC decision.
On 11/20/2015 11:02 AM, Hadrian Zbarcea wrote:
> Probably a bad subject in the context of other things going on :).
>
> Apache Brooklyn is faced with the tasks of migrating it's repo(s) post
> graduation and there are some very large *pre-incubation* artifacts in
> the git repo that we would like removed.
>
> The question was asked on general@ [1] many moons ago, but received no
> answer (the original thread [1] indicates the offenders). We'd like to
> use this occasion to split the git repo into multiple smaller once
> (more naturally tailored to the project), so one idea would be, I
> think, to leave incubator-brooklyn.git as is and just extract what we
> need (everything except the large binaries) in new repos. Note:
> afaiui, those artifacts we're never part of an ASF release.
>
> I am not sure what would be acceptable per ASF (intensely debated)
> policies.
>
> Thoughts?
> Hadrain
>
>
> [1]
> https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201506.mbox/%3C556F0973.7030504@CloudsoftCorp.com%3E
Re: [QUESTION] Rewriting history
Posted by Svetoslav Neykov <sv...@cloudsoftcorp.com>.
//dev@apache only
The script I used for generating the original list is from: https://stubbisms.wordpress.com/2009/07/10/git-script-to-show-largest-pack-objects-and-trim-your-waist-line/. Seems to have problems on OS X out of the box.
Here it is re-genarated with more entries. Definitely some more candidates for removal.
Svet.
All sizes are in kB's. The pack column is the size of the object, compressed, inside the pack file.
size pack SHA location
57722 57718 01760133fa9dedc811762019a2aaa691bbe61988 monterey-example/src/main/resources/booking-mvc.war
23917 23905 d0b52371d4ba447ee9b0f882854b4b5d4d39147f monterey-example/src/main/resources/jboss-booking.war
23915 23903 4f6c7f01e0f49c5e3574d648bcab991f7cab5236 monterey-example/src/main/resources/monterey-booking-as7.war
21737 20984 ab9740889e11e06df060595684c2bd803c1baac1 examples/simple-nosql-cluster/src/main/resources/cumulusrdf-0.6.1-pre.jar
20988 20993 04a0a6fd94873543cfec769b5a272bbe36f0a914 examples/simple-nosql-cluster/src/main/resources/cumulusrdf.war
12124 12119 7ccd0ef45879c78941575d47a8521eef49b0b704 sandbox/examples/src/main/resources/swf-booking-mvc.war
7642 7063 0249fd11430b461f918e2b95adb52425caf81230 gemfire/lib/gemfire-6.5.1.4.jar
7217 7219 9d384383e5542b04ca2b6332aedba92bc92bc5bb examples/simple-nosql-cluster/src/main/resources/cumulusrdf.war
2431 2428 5d7d1216a4276d82c3fabdfa25852e527e1bf78e monterey-example/src/main/resources/booking-mvc.war
2430 2427 9fc9f74223ed9704e91810d5dd9fe79d41ff4b84 com.cloudsoftcorp.monterey.brooklyn/src/main/resources/booking-mvc.war
2352 2194 d45b76da6a46f943e0f98db423c452a54de6b5ef examples/simple-messaging-pubsub/src/main/resources/je-5.0.34.jar
1609 1431 c8c8d5dd6f5bd5b0abf33f5b0203bdc8334e2cbf examples/simple-messaging-pubsub/resources/lib/guava-11.0.2.jar
1272 1094 31febd6ac1cf05b4d8efa4bd8fb11922291f68b7 examples/simple-messaging-pubsub/resources/lib/qpid-common-0.14.jar
938 189 f76b1e280921114cba6d35d14a0faf962591c428 usage/jsgui/src/build/requirejs-maven-plugin/r.js
854 839 0a943f721c500a508f03e27b2e19a3c87d38d6ae docs/start/walkthrough/walkthrough-webconsole-map.png
844 58 814636a66bcf1bb2c871eb66e7694c8b0d92460c docs/website/learnmore/catalog/items.js
844 58 8d29f322676998cba6f3fe7ce75138742441bd24 docs/style/js/catalog/items.json
751 187 50a0512701cdfee7ec981481a6ab7ee8980435a6 sandbox/mobile-app/src/main/webapp/assets/mobile/libs/angular-1.2.19/angular.js
702 663 d107c0f3b0cde13bd25eddae94beede969227b0d gemfire/lib/guava-10.0.1.jar
688 687 855fbf6ccd75fd4e994af0039a68fe1081cbb120 sandbox/examples/src/main/resources/gemfire/springtravel-datamodel.jar
686 650 2f8253a312371de00eafda012394b81dcba3d0ab examples/webapps/hello-world-sql/src/main/webapp/images/BrooklynBridge3Large.png
650 637 27f7c021926b3daf1dbcea035c50e174bdc34490 docs/use/examples/global-web-fabric/console-map.png
645 586 3d65a9979cdb87c58d5b8b504506425587685784 docs/guide/yaml/web-console-yaml.png
529 487 ad531d202995fb583d04a37de2322bb4e228786d examples/simple-messaging-pubsub/resources/lib/qpid-client-0.14.jar
479 429 60a07b99af9d7d5ce029878556ab411b8d99eee0 docs/website/learnmore/features/ops-console.png
418 398 47988cd9148671441d18eada811f4bf8ce4be72d docs/start/walkthrough/walkthrough-webconsole-scaling.png
388 363 c7cf2645df219a926fc253a7d94a2661eb4e3e56 docs/start/walkthrough/walkthrough-webapp.png
379 359 45e45b5c1d3053af4bf17fa0c19b082a71c0729e gemfire/lib/antlr.jar
377 89 a189b2a33744dab7c9bf6d7766db5dbc4fa5aa02 web-console/web-app/js/jquery/jquery.jqGrid-4.1.1/js/jquery.jqGrid.src.js
368 107 1d8a220ba8077aa314a28b90331c7cba9b4811c8 usage/jsgui/src/main/dev/js/libs/jquery.dataTables.js
368 84 1d8a220ba8077aa314a28b90331c7cba9b4811c8 usage/jsgui/src/main/dev/js/libs/jquery.dataTables.js
366 363 3303667efd4288d25d0e4da05aaeac0c017e235a docs/use/examples/global-web-fabric/console-map-w700.png
366 87 96b2ea624a1ce4abaaa6ff3ae2c48e354c7199ac usage/web-console/web-app/js/jquery/ui/jquery-ui-1.8.14.js
362 105 70165d34d4f3a45d0dc3c9a5dd931b467a0f015d usage/jsgui/src/main/webapp/assets/swagger-ui/lib/swagger-ui.min.js
362 332 59543774f218e4fd2a899ac75f118066c9395cab usage/web-console/src/test/resources/ldap/lib/mail.jar
358 325 625130719013f195869881a36dcb8d2b14d64d1e examples/simple-messaging-pubsub/resources/lib/log4j-1.2.14.jar
327 304 e17a052dd123bbd10439f236a59cdca6f97f11f0 docs/start/walkthrough/walkthrough-webconsole-details.png
325 102 bcb0295349021c79bbcdebf7a1cb120f2cf60305 sandbox/mobile-app/src/main/webapp/assets/mobile/libs/angular-1.2.19/angular-scenario.js
324 317 970805f0218c6b5751db7a28d4055ca2a6a7bd1d docs/guide/java/wt-starting.png
323 317 cd0f8117dda7fe4ae6c4adfcfe9d4dd169871d5e docs/_extra/big_examples/global-web-fabric/console-map.png
316 293 9ee257fa8cb734a458f51540097452c8ff6743e7 docs/use/examples/portable-cloudfoundry/webapp.png
297 275 25ebba474973a93955de943b4ba6c7230a80e051 docs/use/examples/global-web-fabric/console-geoscaling-details.png
296 296 c87a53913efee0b0f448615caeddbf146b0a8d80 docs/guide/java/wt-starting-700.png
283 30 471a2ff2405409951193f24dce5c4fd4b76fe7bb usage/web-console/src/test/resources/ldap/config/upgrade/schema.ldif.7743
280 84 d907b25ae60ec7e3d32e4027aa6e6b7595de97af docs/style/deps/font-awesome-4.2.0/fonts/fontawesome-webfont.svg
> On 20.11.2015 г., at 18:02, Hadrian Zbarcea <hz...@gmail.com> wrote:
>
> Probably a bad subject in the context of other things going on :).
>
> Apache Brooklyn is faced with the tasks of migrating it's repo(s) post graduation and there are some very large *pre-incubation* artifacts in the git repo that we would like removed.
>
> The question was asked on general@ [1] many moons ago, but received no answer (the original thread [1] indicates the offenders). We'd like to use this occasion to split the git repo into multiple smaller once (more naturally tailored to the project), so one idea would be, I think, to leave incubator-brooklyn.git as is and just extract what we need (everything except the large binaries) in new repos. Note: afaiui, those artifacts we're never part of an ASF release.
>
> I am not sure what would be acceptable per ASF (intensely debated) policies.
>
> Thoughts?
> Hadrain
>
>
> [1] https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201506.mbox/%3C556F0973.7030504@CloudsoftCorp.com%3E
Re: [QUESTION] Rewriting history
Posted by Sam Corbett <sa...@cloudsoftcorp.com>.
Hi,
To give some context on the objects in question..
There are 14 files in Brooklyn's history larger than 1Mb. Four of these are
larger than 20Mb. The largest is 57Mb(!). These files make for a
significant penalty when cloning the repository.
Of the fourteen large files, five were present in the Brooklyn repo when
the project joined the incubator (1 May 2015). All of them were deleted
before its first incubator release (0.7.0-M2 (incubating)) on 23 December
2014. The files are also not to be found in Brooklyn's last pre-ASF release
(they are all either examples or in a 'sandbox' module).
The other nine files were all deleted before Brooklyn even had its first
public GA release (0.4.0) on January 16 2013. The worst offending file is
part of this group.
Regards,
Sam
On 20 November 2015 at 16:42, Ted Dunning <te...@gmail.com> wrote:
> On Sat, Nov 21, 2015 at 12:02 AM, Hadrian Zbarcea <hz...@gmail.com>
> wrote:
>
> > The question was asked on general@ [1] many moons ago, but received no
> > answer (the original thread [1] indicates the offenders). We'd like to
> use
> > this occasion to split the git repo into multiple smaller once (more
> > naturally tailored to the project), so one idea would be, I think, to
> leave
> > incubator-brooklyn.git as is and just extract what we need (everything
> > except the large binaries) in new repos. Note: afaiui, those artifacts
> > we're never part of an ASF release.
> >
> > I am not sure what would be acceptable per ASF (intensely debated)
> > policies.
> >
>
> Surely copying and leaving some stuff behind is a fine thing to do.
>
Re: [QUESTION] Rewriting history
Posted by Sam Corbett <sa...@cloudsoftcorp.com>.
Hi,
To give some context on the objects in question..
There are 14 files in Brooklyn's history larger than 1Mb. Four of these are
larger than 20Mb. The largest is 57Mb(!). These files make for a
significant penalty when cloning the repository.
Of the fourteen large files, five were present in the Brooklyn repo when
the project joined the incubator (1 May 2015). All of them were deleted
before its first incubator release (0.7.0-M2 (incubating)) on 23 December
2014. The files are also not to be found in Brooklyn's last pre-ASF release
(they are all either examples or in a 'sandbox' module).
The other nine files were all deleted before Brooklyn even had its first
public GA release (0.4.0) on January 16 2013. The worst offending file is
part of this group.
Regards,
Sam
On 20 November 2015 at 16:42, Ted Dunning <te...@gmail.com> wrote:
> On Sat, Nov 21, 2015 at 12:02 AM, Hadrian Zbarcea <hz...@gmail.com>
> wrote:
>
> > The question was asked on general@ [1] many moons ago, but received no
> > answer (the original thread [1] indicates the offenders). We'd like to
> use
> > this occasion to split the git repo into multiple smaller once (more
> > naturally tailored to the project), so one idea would be, I think, to
> leave
> > incubator-brooklyn.git as is and just extract what we need (everything
> > except the large binaries) in new repos. Note: afaiui, those artifacts
> > we're never part of an ASF release.
> >
> > I am not sure what would be acceptable per ASF (intensely debated)
> > policies.
> >
>
> Surely copying and leaving some stuff behind is a fine thing to do.
>
Re: [QUESTION] Rewriting history
Posted by Ted Dunning <te...@gmail.com>.
On Sat, Nov 21, 2015 at 12:02 AM, Hadrian Zbarcea <hz...@gmail.com>
wrote:
> The question was asked on general@ [1] many moons ago, but received no
> answer (the original thread [1] indicates the offenders). We'd like to use
> this occasion to split the git repo into multiple smaller once (more
> naturally tailored to the project), so one idea would be, I think, to leave
> incubator-brooklyn.git as is and just extract what we need (everything
> except the large binaries) in new repos. Note: afaiui, those artifacts
> we're never part of an ASF release.
>
> I am not sure what would be acceptable per ASF (intensely debated)
> policies.
>
Surely copying and leaving some stuff behind is a fine thing to do.
Re: [QUESTION] Rewriting history
Posted by Ted Dunning <te...@gmail.com>.
On Sat, Nov 21, 2015 at 12:02 AM, Hadrian Zbarcea <hz...@gmail.com>
wrote:
> The question was asked on general@ [1] many moons ago, but received no
> answer (the original thread [1] indicates the offenders). We'd like to use
> this occasion to split the git repo into multiple smaller once (more
> naturally tailored to the project), so one idea would be, I think, to leave
> incubator-brooklyn.git as is and just extract what we need (everything
> except the large binaries) in new repos. Note: afaiui, those artifacts
> we're never part of an ASF release.
>
> I am not sure what would be acceptable per ASF (intensely debated)
> policies.
>
Surely copying and leaving some stuff behind is a fine thing to do.
Re: [QUESTION] Rewriting history
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
To me, binaries not released by the ASF should not be necessary to keep
in multiple repos so this is a project PMC decision.
On 11/20/2015 11:02 AM, Hadrian Zbarcea wrote:
> Probably a bad subject in the context of other things going on :).
>
> Apache Brooklyn is faced with the tasks of migrating it's repo(s) post
> graduation and there are some very large *pre-incubation* artifacts in
> the git repo that we would like removed.
>
> The question was asked on general@ [1] many moons ago, but received no
> answer (the original thread [1] indicates the offenders). We'd like to
> use this occasion to split the git repo into multiple smaller once
> (more naturally tailored to the project), so one idea would be, I
> think, to leave incubator-brooklyn.git as is and just extract what we
> need (everything except the large binaries) in new repos. Note:
> afaiui, those artifacts we're never part of an ASF release.
>
> I am not sure what would be acceptable per ASF (intensely debated)
> policies.
>
> Thoughts?
> Hadrain
>
>
> [1]
> https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201506.mbox/%3C556F0973.7030504@CloudsoftCorp.com%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org