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

Bring packages to monorepo #51

Open
parzhitsky opened this issue May 11, 2020 · 1 comment
Open

Bring packages to monorepo #51

parzhitsky opened this issue May 11, 2020 · 1 comment
Labels
Change: patch [Issue / PR] describes a small non-breaking change, such as bugfix or an optimization Domain: meta [Issue / PR] describes change in the development process, documentation, maintenance etc. Pending: unclear [Issue] not yet fully defined Priority: low [Issue / PR] could be addressed at any convenient time Type: improvement [Issue / PR] addresses lack of a functionality or an open possibility of enhancement

Comments

@parzhitsky
Copy link
Member

The code for all the packages (see #24) should eventually be stored inside the same (mono-) repo

@parzhitsky parzhitsky added Change: patch [Issue / PR] describes a small non-breaking change, such as bugfix or an optimization Domain: meta [Issue / PR] describes change in the development process, documentation, maintenance etc. Priority: low [Issue / PR] could be addressed at any convenient time Type: improvement [Issue / PR] addresses lack of a functionality or an open possibility of enhancement labels May 11, 2020
@parzhitsky parzhitsky added this to To be considered in xrange@2.0 via automation May 11, 2020
@parzhitsky parzhitsky added this to To be considered in xrange@2.1 via automation May 11, 2020
@parzhitsky parzhitsky added this to To be considered in xrange@2.2 via automation May 11, 2020
@parzhitsky parzhitsky added the Pending: unclear [Issue] not yet fully defined label May 11, 2020
@parzhitsky
Copy link
Member Author

Unclear, untill the list of extraneous packages is defined

@parzhitsky parzhitsky removed this from To be considered in xrange@2.0 May 11, 2020
@parzhitsky parzhitsky moved this from To be considered to Rejected in xrange@2.1 Jan 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Change: patch [Issue / PR] describes a small non-breaking change, such as bugfix or an optimization Domain: meta [Issue / PR] describes change in the development process, documentation, maintenance etc. Pending: unclear [Issue] not yet fully defined Priority: low [Issue / PR] could be addressed at any convenient time Type: improvement [Issue / PR] addresses lack of a functionality or an open possibility of enhancement
Projects
xrange@2.2
  
To be considered
xrange@2.1
  
Rejected
Development

No branches or pull requests

1 participant