RE: JIRA - PLEASE READ

All This thread seems to have turned into 2 quite different discussions: 1. The use (or not) of Jira - which was the original discussion 2. Ways/means of encouraging (and paying for more structured contributors) I know that it could be argued that these are related. Could I suggest opening up

[DISCUSS] - Releases, Project Management & Funding Thereof

As per Giles's comment to the previous thread, I thought I would start a discussion on the subject to canvas peoples thoughts, opinions and fears. My question for discussion, is there is any mileage in someone creating a "CloudStack Foundation" as a non-profit entity, funded largely by key

RE: JIRA - PLEASE READ

Hello, I've created a DISCUSS thread to... discuss this subject separately from the original Jira issue. Sorry Paul for hijacking your Jira rant. Alexander Hitchins E: a...@alexhitchins.com W: alexhitchins.com M: 07788 423 969 T: 01892 523 587 -Original

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

I personally think it is important to have a person working consistently on the ACS releases. It is a ton of work and with the job rotating right now, it makes it harder for everyone. That said, no organization can afford to hire a dedicated RM for year(s) at a time. I have considered it, but

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

Yes, Schuberg Philis, a very active community member forked Cosmic off of CloudStack and has been developing their fork for their needs. I do think we need to have a more consistent front on this matter. I think it would make a big difference on the quality, release cadence and perception of the

Current Developer Setup Guide

All, Is the following link the best guide to assist me in getting CloudStack ready for development on my machine? https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+a+CloudSta ck+dev+environment+on+Windows I note the last modified date is Jan 2015. And yes - I

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

I am in complete agreement with you. Also on your other reply regards to a FT release manager. If 'we' don't go down this line, more and more people will follow the Cosmic/Schuberg Philis path or even use Cosmic instead. I'm encouraged by your response. Sounds like a few others hold the same

RE: JIRA - PLEASE READ

Back to jira. I personally have never searched jira for an issue. I search github prs for issues often though to see what code is actually pending for different issues. I dont think i am alone in that. My stance is that unless we have a solid reason for using jira which we can not solve with

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

https://www.apache.org/foundation/contributing.html says: "If you have a specific target or project that you wish to directly support, pleasecontact us and we will do our best to satisfy your wishes." 1) Is Apache willing to

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

Apache has been historically against the idea of a cloudstack foundation and there is a bit of a pandoras box there which we will want to be careful about opening. Apache added direct contribution, but it was unusable for us historically because it required a minimum contribution of 50k, which

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

I'll read those links, thank you for providing them. Do you think this is a move in the wrong direction or just an unnecessary move to begin with? Alexander Hitchins E: a...@alexhitchins.com W: alexhitchins.com M: 07788 423 969 T: 01892 523 587 -Original

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

Thanks Will, I understand it's something that comes with a big bag of troublesome worries. If this topic comes up again in any discussions, I'd be interested to hear their thoughts on what I see as the alternative; without a dedicated RM/PM/Captain, people will fork off CS so they can achieve

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

How many companies are funding staff now to work on Cloudstack? How much time? How many FTEs does that come to if one adds it all up? It is harder to get people who are working on their own time to do administrative tasks on a tight schedule. If someone is working for a company that is

RE: JIRA - PLEASE READ

From reading back through the thread, I think pauls initial point was around the fact that currently (and I don’t know whether this is hardcoded in our guidelines,etc) there is an assumption that the workflow for an issue will be Jira issue>fix>PR>> - and that is followed erratically The Jira

Re: JIRA - PLEASE READ

Yes, we would be adopting github issues for that then. If you want to handle those in jira we could, but i personally dont see any value in a jira ticket for an actual PR. On Jun 30, 2017 10:26 AM, "Ron Wheeler" wrote: > Going back to my previous point. >

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

We could probably split this topic down also I think I may have mentioned previously  my view on how we have somewhat shot ourselves in the foot with the release process this time around. I think that for the most part, people have been well intentioned, and have been trying to 'make

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

I am not doing much right now because our company has many other things on the go. For about the first 6 months of 2016 CloudOps donated my time full time to act as the release manager of 4.9. That is not something we or I can sustain. Which is part of the problem. On Jun 30, 2017 1:28 PM, "Ron

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

1) Are there any good models in the Apache community of projects that maintain a quality release process without full-time staff? 2) Are there things that cause most of the grief around releases? Anything on the Release Manager's list of aggravations that could be eliminated? Is there a good

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

I know of four who have at least one full time resource dedicated, some with considerably more. These people are working on features and support as this is where the income is. I feel if the cost of a full time RM was split across n sponsors, it would be a massive ROI. > On 30 Jun 2017, at

RE: JIRA - PLEASE READ

Whether we use 'GitHub Issues' or 'Jira Issues' doesn't change the basic point, which is bug fixes and indeed features need to be tracked. If someone wants to know what versions a feature is in, or what version a bug was fixed, or if anyone has experienced/reported/fix a bug that they are

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

Perhaps a Release Tsar would be a better solution. The RM needs to have absolute control over what is in or out. Reasonable discussion allowed and then a decision once the RM feels that the case has been fully explored and that a positive vote is expected. The importance on meeting deadlines

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

> Op 30 juni 2017 om 18:09 schreef Paul Angus : > > > We could probably split this topic down also > > I think I may have mentioned previously  my view on how we have somewhat > shot ourselves in the foot with the release process this time around. I > think

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

Have not looked at Release Tsar, but worth checking out. In general, the biggest problem we have with releasing on a schedule is the lack of a CI setup which covers the entire software. Or at least a 'supported' set of features. This means that the release is always bound to a bunch of volunteers

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

Thanks Wido. Sounds like a warm reception from yourself. I will do more work on costs etc. Be a fun exercise even if likely proves academic. > On 30 Jun 2017, at 18:13, Wido den Hollander wrote: > > >> Op 30 juni 2017 om 18:09 schreef Paul Angus :

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

Releasing against a defined reference rig would be a very good idea, especially if we could replicate several. It concerns me slightly that we are building a platform we want to promote people to deploy in enterprise environments with the caveat 'run at your own risk'. We need to up our game.

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

Consultation with users is something that should definite be done. Canvas as many as possible. I agree that most people will be running test environments before full rollout of any technology, I guess see it a little from a CTO eyes - why shortlist a technology that doesn't even endorse its

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

How much time is there between a feature freeze and the RC being cut.? Do people know far enough in advance that their feature is in or out and if in must be ready to go to a RC release by such and such a date? Is the use case testing well defined - hardware, configurations, etc. Can you put

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

Taken from a talk on CloudStack testing [1]... There are Many, many, MANY permutations of a CloudStack deployment…. • Basic / Advanced • Local / shared / mixed storage • More than 8 common hypervisor types/versions • 4 or 5 Management server OS possibilities • That’s 144 combinations only

RE: [DISCUSS] - Releases, Project Management & Funding Thereof

We can't validate all scenarios no, hence suggesting several common setups as a reasonable baseline. I like the idea of users posting their hardware and versions as a community endeavour. I strongly feel there should be an established, physical setup that the release team have access to in

Re: ***UNCHECKED*** Re: [DISCUSS] - Releases, Project Management & Funding Thereof

Rewritten to have sentences that parse into some understandable English. If the plan is to do several releases each year, something has to change in the process. Any idea about what tasks took up most of the time? Were there any specific issues that ate up more time than you expected.

Re: [VOTE] Apache CloudStack 4.10.0.0 RC6

Hi Rajani, Just checking: Was it your intention to create a new RC on Monday? Thanks! Mike On 6/28/17, 3:28 AM, "Rajani Karuturi" wrote: Thanks for confirming. I will keep this RC open for two more days for others to test before next RC. Agree on merging

RE: ***UNCHECKED*** Re: [DISCUSS] - Releases, Project Management & Funding Thereof

"" Would breaking Cloudstack into separately modules that are separately released by different teams make things more manageable?"" Please don’t do this. This is basically OpenStack at that point. I would write more on this but ZI am on a phone call.. :) I just wanted say I don’t think that

Re: ***UNCHECKED*** Re: [DISCUSS] - Releases, Project Management & Funding Thereof

If the plan is to do several releases each year, something has to change in the process. Any idea about what tasks took up most of the time? Were there any specific issues that ate up more time than you expected. Would breaking Cloudstack into separately modules that are separately released

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

On 30/06/2017 2:19 PM, Alex Hitchins wrote: Releasing against a defined reference rig would be a very good idea, especially if we could replicate several. It concerns me slightly that we are building a platform we want to promote people to deploy in enterprise environments with the caveat

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

On 30/06/2017 3:28 PM, Alex Hitchins wrote: We can't validate all scenarios no, hence suggesting several common setups as a reasonable baseline. I like the idea of users posting their hardware and versions as a community endeavour. I strongly feel there should be an established, physical

Re: [DISCUSS] - Releases, Project Management & Funding Thereof

This makes me think of the OpenSSL (I think) that have some 'foundation' where there is a paid engineer and donated servers, switches etc to maintain builds and tests. In my opinion, we need the same. Who out there in a position to comment thinks they would be able to commit some budget

Re: JIRA - PLEASE READ

Going back to my previous point. Whatever makes the preparation of Release Notes easier should drive the policy. It sounds like Will is favouring a complete abandonment of the JIRA. Does this change the end-user's process for reporting bugs or requesting new features? Ron On 30/06/2017