Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 15.3 proposal #1104

Closed
2 of 37 tasks
zabil opened this issue May 6, 2015 · 6 comments
Closed
2 of 37 tasks

Release 15.3 proposal #1104

zabil opened this issue May 6, 2015 · 6 comments
Milestone

Comments

@zabil
Copy link
Contributor

zabil commented May 6, 2015

Open Items

CD features

Installers

UI/UX enhancements

API enhancements

Plugins

Bug fixes

Performance fixes

Technical debt


See also -

@ketan ketan added this to the Release 15.3 milestone Jun 30, 2015
@zabil zabil mentioned this issue Jun 30, 2015
23 tasks
@ketan ketan changed the title Next release (15.2+) Release 15.3 proposal Jun 30, 2015
@tomzo
Copy link
Member

tomzo commented Jul 29, 2015

#1133 shouldn't be under 'Performance fixes' . It does not improve xml performance, it only provides a way to not use xml at all.

It is definitely a feature. It could also be under plugins because it introduces new extension point.

@cholmes1111
Copy link

Feature request: Order tasks in alphabetical order (and ability to remove tasks you don't want)

@cholmes1111
Copy link

Feature request: Assigning pipelines to an environment permissions. Users besides System Administrators, should be able to assign pipelines to an environment.

@cholmes1111
Copy link

Feature request: AD integration and user permissions. With LDAP integration enabled, you should be able to manage user permissions with AD security groups as well as individual users. Unfortunately, currently GO does not recognize security groups.

@arvindsv
Copy link
Member

arvindsv commented Nov 2, 2015

@cholmes1111: Here are some GitHub issues where those features have been brought up before:

#1441 - Roles for assigning pipelines to environments
#134 - AD groups and integration
#1404 and #1496 - Probably the right places for talking about ordering tasks

As I've said before in other tickets, this is an open-source project (yes, some core contributors and infrastructure are supported by an organization, but all development to the core happens out in the open) and contributions are key. Not everything asked by everyone will get done, unfortunately. But, as a project, pull requests are always welcome and we help people work on anything they're interested in (by pairing with them, by explaining how they can start and helping them with setup if needed).

Currently, for 15.3, this is the work in progress and that is a lot of work. Hope that makes sense. Thanks!

@arvindsv
Copy link
Member

arvindsv commented Nov 2, 2015

Not to say your requests and ideas are not valuable, of course. :) I think what you say about ordering makes complete sense. My response was more about slotting that work in, and deciding what to work on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants