Looking around for some other matters, I notice there is no 4.1.1 branch in the 
SVN.  Is this intentional?

 - Dennis

-----Original Message-----
From: Andrea Pescetti [mailto:[email protected]] 
Sent: Saturday, December 13, 2014 12:45
To: [email protected]
Subject: Re: Budapest and thereafter.

On 08/12/2014 jan i wrote:
> So may I politely ask, what have changed, that we now believe this will all
> go away, and we can have it all solved in a short time ?

Not much has changed indeed. I pushed to have buildbots running before 
the release, but indeed if buildbots are problematic and the same 
volunteers who built the previous releases can still commit to doing so 
for the next one, it is no major problem.

Very honestly, I would like that we don't depend on individuals for 
project resources, but maybe it is easier for a developer to share an 
existing virtual machine (and possibly get it running at Apache) than to 
prepare a buildbot environment.

> do we really want to wait until this magically happens ?

No, since it won't magically happen. So, what is the minimum we can do 
for a 4.1.2 release? I would set it at:
- New/updated translations
- New/updated dictionaries
- Bugfixes (to be discussed)
- Signed Windows binaries
- Binaries for all other systems as usual

I can volunteer for the first two items (coordinating translations and 
adding/updating dictionaries).

But I'm actually missing some information maybe. Out of the following 
releases, which ones were built on individuals' machines for 4.1.1? All? 
Some? And are these built in a VM that we could consider moving to 
Apache hardware or not?
1) Windows
2) Linux 64 bit (RPM+DEB)
3) Linux 32 bit (RPM+DEB)
4) Mac

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to