octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Request for write access on OctaveForge server


From: Juan Pablo Carbajal
Subject: Re: Request for write access on OctaveForge server
Date: Sat, 31 Oct 2015 11:29:36 +0100

On Sat, Oct 31, 2015 at 11:09 AM, Julien Bect
<address@hidden> wrote:
> Le 31/10/2015 10:46, Lukas Reichlin a écrit :
>>
>> On Friday morning, I posted control-3.0.0 on the package release tracker,
>> just a few hours after parallel-3.0.3 (by Olaf Till). Additionally, I sent
>> an e-mail to Carnë, asking him that he should upload it to the OctaveForge
>> server as soon as possible.
>>
>> On Friday afternoon, Carnë published parallel-3.0.3 on the OctaveForge
>> server and removed its ticket on the package release tracker, but he failed
>> to do so for control-3.0.0 for no apparent reason. He did not respond to my
>> enquiry on Friday evening, and control-3.0.0 is still waiting for being
>> published on OctaveForge until now.
>>
>> As I have been working very hard on improving the control package during
>> the last few weeks (and as I am on edge), this situation is very frustrating
>> to me (and it is not the first time). Therefore I am asking kindly for write
>> acces on the OctaveForge server so I can publish my future package releases
>> (control and quaternion) on my own.
>
>
> Hello Lukas,
>
> I can't speak for Carnë of course, but I assume that what you call "no
> apparent reason" is simply lack of time to process both release request
> tickets in a row.
>
> You created the ticket on Friday and we are only Saturday: no yet a very
> long wait time, in my opinion (but of course that's subjective, and you
> probably have some very good reasons to be in a hurry for this specific
> release).
>
> It is my understanding that the "release process" (i.e., what Carnë does to
> turn a release request into an actual release) is only semi-automated.
>
> Perhaps the first step towards reducing the release delay (and reducing
> Carnë's workload) would be to fully document those steps (which probably
> include some basic sanity checks, pushing the tarballs to the release file
> system, pushing the documentation to the web site, etc.).
>
> Then we would have two options : either expanding the "release team" (which
> is actually composed of Carnë only) as you suggest, or automating those
> steps (in which case we could have some sort of "release deamon" that does
> what Carnë actually does, but I have no idea if this is realistic).
>
> Just my 2 cents.
>
> @++
> Julien
>
>

Hi Lukas,

Do not feel bad! You have made an excellent work and I am sure Carnë
is just out of time as Julien said. I am sure contorl 3.0.0 will be
out soon.

I coincide 100% with Julien, we need to have a bigger release team and
a description of the release stps so we can automate or at least
follow.

Cheers



reply via email to

[Prev in Thread] Current Thread [Next in Thread]