Re: Addding support for unattended upgrades

Hi Gianluca,

Thanks for implementing this feature.  Regarding submitting the patch,
some developers prefer a diff file and some prefer the updated/added
files.  I would suggest attaching a zip file to the issue.  The zip
file should include the following:

1. The universal diff file.

2. The files that were updated/added.

3. A readme file explaining the files about how to apply the patch.
Also this should identify files to be deleted (if applicable).

On 1/5/07, Gianluca Sforna <giallu@...> wrote:
> Following up to:
> http://www.mantisbt.org/bugs/view.php?id=7663
>
> I implemented a (pretty rough) script to upgrade the db schema from
> the command line.
>
> The script (a simplified version of upgrade.php) uses a new function I
> added to upgrade_inc.php  (run_all_unattended) and was tested here to
> upgrade an old DB coming from some older 0.xx version to the 1.0.6
> schema.
>
> Now I would like to:
> 1. polish to code
> 2. test again with a "live" mantis installation
> 3. submit the patch
>
> what is your preferred way for 3?
>
> cheers
>
> Gianluca
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Mantisbt-dev mailing list
> Mantisbt-dev@...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV