This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 10560 - Provide option of incremental download
Summary: Provide option of incremental download
Status: RESOLVED WONTFIX
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 3.x
Hardware: Other Other
: P4 blocker (vote)
Assignee: nbbuild-issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-03-22 02:27 UTC by _ gtzabari
Modified: 2005-03-09 04:28 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ gtzabari 2001-03-22 02:27:54 UTC
Right now users with 56k modems must download 14MB every night to be able 
to test the latest nightly build for you.

I suggest you provide a way to download the diff between different builds 
(so they'd download the full version just once and diffs from then on) 
and provide a Java-based diff-processing utility to update their 
installed version to the latest available build. This diff-creation 
should be automaticalled created by the nightly build cron job.
Comment 1 Jan Zajicek 2001-03-22 10:51:33 UTC
changed to enhancement and priority moved to p5

it would be better to propose this enhancement on nbdev mailing list, I think
this is a job for release engineering
Comment 2 Jesse Glick 2001-04-03 12:01:27 UTC
Why is the default owner for www/downloads support@collab.net?? Should be
bugs@www.netbeans.org like everywhere else.
Comment 3 Taska 2001-05-25 21:19:18 UTC
Has this been proposed on nbdev?
Comment 4 Unknown 2001-05-25 21:46:50 UTC
This doesn't need to be taken to nbdev.  The original issue is something that 
the content people need to provide (ie. splitting up the released files into 
smaller *bites* for people to download.
However, the support@collab.net initial owner was set so that support would be 
notified when issues arose and can escalate properly.
I'm going to set every netbeans.org component's initial owner to 
bugs@www.netbeans.org and add support@collab.net to this alias.
Comment 5 Unknown 2001-05-25 22:00:11 UTC
fixed.
bugs@www.netbeans.org is put in for all www components as initial owner.
support@collab.net has been subscribed to that list.
Comment 6 jcatchpoole 2001-05-28 11:56:13 UTC
Why was this marked resolved/fixed ?  Prior to Friday this
issue was an enhancement request for the buildmasters/release
engineering.  Unless I missed something the enhancement has
not been completed or discussed, so I don't see why this was
closed.  

Also "Assigned to" has been set back to taska@collab.net,
whereas it should be bugs@www.netbeans.org - Jesse alread
changed this once.  Collab this is our problem, you don't
need to do anything here.

Reopening.
Comment 7 Taska 2001-06-07 18:24:52 UTC
Note to Collabnet Support folks: This has been determined to be an issue for
Netbeans to resolve.
Comment 8 rbalada 2001-06-07 18:49:40 UTC
Adding me to Cc:, because I'm the person who should probably implement this.
On the other hand I guess that discussion on nbdev should be started.
In case that the result of discussion on nbdev will be request to implement it, 
then assign it to me and I will implement it in cooperation with Jack.
Comment 9 rbalada 2002-02-20 17:32:36 UTC
Accepting for implementation
Comment 10 rbalada 2002-02-21 12:41:08 UTC
Reassigning to me
Comment 11 Marek Grummich 2002-07-22 11:08:54 UTC
Set target milestone to TBD
Comment 12 rbalada 2003-10-09 15:26:08 UTC
Remind later
Comment 13 Jesse Glick 2003-10-09 18:25:18 UTC
Ruda - generally we don't use the REMIND resolution is IZ; no one will
remind you. :-) At least for normal IZ components, such RFEs are set
to milestone Future is there is no current plan to deal with them.

Anyway this might be WONTFIX, since with the dev alpha daily AU you
can (in principle anyway) just keep one dev build and install any
daily updates to particular modules. You won't have precisely the same
bits as in that day's dev build, since most modules would not have
updated their manifest versions, but you would get any updates that
the module owner considered significant enough to mark with a new version.