Open Bug 1169140 Opened 9 years ago Updated 8 years ago

Make available existing private WIN32 builds for testing

Categories

(SeaMonkey :: Project Organization, defect)

SeaMonkey 2.35 Branch
Unspecified
Windows
defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: RainerBielefeldNG, Unassigned)

Details

User Story

Callek has made available a FTP site for us to host private Win32 builds for testing. Please see: http://seamonkey.callek.net/contrib/
Some people do their own WIN32 SeaMonkey builds, for example see <https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2015-05-26> " Ratty has offered".
As long as the official build process is broken it would be great to have them available for a limited number of QA volunteers. It should be easy to find some web space where they can be published, for example I can contribute some GB for a small download area.
The meeting notes haven't been updated to reflect the actual discussion. There were some concerns about malware sneaking in, thus there may be a "more official" way to get these builds done.
(In reply to rsx11m from comment #1)
> There were some concerns about malware sneaking in, thus there may be a

Well, to me most things seem to be more easy than the Mozilla way, so I think sourceforge.net might be a solution for a while?
(In reply to rsx11m from comment #1)
> The meeting notes haven't been updated to reflect the actual discussion.
> There were some concerns about malware sneaking in, thus there may be a
> "more official" way to get these builds done.
This was in regards to putting out a SeaMonkey 2.35 release.

I have a sourceforge account which I haven't used in ages. I could upload my builds there if someone reminds me how to do it.
I can make a build if you need it.
(In reply to Philip Chee from comment #3)
> I could upload my builds there if someone reminds me how to do it.

1. In your profile create a new Project "Private Trunk Builds"
2. To new project Upload a readme.md with short project description
3. In new Project create new folder "SM2.35_WIN32_Trunk" or so
4. To new folder upload s readme.md and your builds, each with source.zip
5. think about sourcforge-project infrastructure, do we need tickets, wiki,
   something else?

If you are too busy for that (it's only few work, but of course, it needs a little initial training) I can create a source forge project similar to <https://sourceforge.net/projects/seamonkeyaddons/> and grant developer permissions (do anything except creating / dropping projects) to  you so that you only need to upload the builds.

(In reply to rn10950 from comment #4)
What kind of builds (branch - OS - Language - ...) can you contribute?
re Sourceforge. Change of plans. Sourceforge is wrapping file downloads with their own installers which install adware/malware. Please suggest somewhere else. Bitbucket?
(In reply to Philip Chee from comment #6)
I also in the past observed some unacceptable ideas at sourceforge.net like
adult contents popups and redirections, see <https://www.mywot.com/en/scorecard/sourceforge.net/comment-85012161#comment-85012161> (unfortunately no comment history visible). But my last info was that currently nothing like that happens. 
Can you contribute sources for your concerns like 
<https://sourceforge.net/p/forge/site-support/5006/>
<https://sourceforge.net/p/forge/site-support/7414/>
<http://malwaretips.com/threads/sourceforge-net-adds-adware-installers-provided-by-ask-com.17247/>
<http://blog.gluster.org/2013/08/how-far-the-once-mighty-sourceforge-has-fallen/>
<http://remixedcat.blogspot.de/2015/02/sourceforge-bundles-malware.html>

Indeed, it seems that we should not trust sourceforge.net.
I have no experience at all with other 
<https://en.wikipedia.org/wiki/Comparison_of_source_code_hosting_facilities>
hosting facilities
(In reply to Rainer Bielefeld from comment #5)
> (In reply to Philip Chee from comment #3)
> > I could upload my builds there if someone reminds me how to do it.
> 
> 1. In your profile create a new Project "Private Trunk Builds"
> 2. To new project Upload a readme.md with short project description
> 3. In new Project create new folder "SM2.35_WIN32_Trunk" or so
> 4. To new folder upload s readme.md and your builds, each with source.zip
> 5. think about sourcforge-project infrastructure, do we need tickets, wiki,
>    something else?
> 
> If you are too busy for that (it's only few work, but of course, it needs a
> little initial training) I can create a source forge project similar to
> <https://sourceforge.net/projects/seamonkeyaddons/> and grant developer
> permissions (do anything except creating / dropping projects) to  you so
> that you only need to upload the builds.
> 
> (In reply to rn10950 from comment #4)
> What kind of builds (branch - OS - Language - ...) can you contribute?

I can submit release Win32 en-US.

(In reply to Philip Chee from comment #6)
> re Sourceforge. Change of plans. Sourceforge is wrapping file downloads with
> their own installers which install adware/malware. Please suggest somewhere
> else. Bitbucket?

Maybe we can use a Dropbox account?
Why not some GBs on Google Drive as a small download area.
https://googledrive.com/host/0B12_Pw9ayns6Vm5UVXJwTWFvXzQ/Mozilla%20SeaMonkey/Windows/en-US/
For User Builds we will need some kind of "package leaflet" so that users can estimate for what the different builds with different build settings can be used. Discussion / Suggestion in progress in German Language at <https://etherpad.mozilla.org/OhUGdNHs7j>
User Story: (updated)
As a side note, the version 20150604 posted in Callek's contrib ( http://seamonkey.callek.net/contrib/ ) is not able to save draft messages not to send mails.
Not sure though if there is (are) bug(s) on that.
(In reply to Dominique Fillon from comment #11)
> As a side note, the version 20150604 posted in Callek's contrib (
> http://seamonkey.callek.net/contrib/ ) is not able to save draft messages
> not to send mails.
Ooops! This was caused by typos in a patch I was reviewing.
To avoid misunderstanding: My intention is not (only) to get some webspace at the remotest area of the WWW where some trunk builds can be found, but
a) An inviting environment where trustworthy users can publish their private builds
b) some management granting Aurora, Trunk and 2.35a builds from different
   users every few days, so that we have all required test builds without 
   overcharging the contributors
c) an inviting download area, published anywhere where required so that QA-
   interested users will find builds they need for their tests (what also means
   that we need some short description of the user builds because build preferences
   of the contributors might be different). May be we even can find some 
   additional bug testers ...

Of course we can use <http://seamonkey.callek.net/contrib/>, but we will need a wiki-page with some explications
a) who may contribute
b) where to ask for upload permission?
c) where is download area already published?
d) and so on.

I am willing to do some of that work when required info is available here in the
Bug.
You need to log in before you can comment on or make changes to this bug.