# Prepare pijul-0.7.0

**URL:** <https://discourse.pijul.org/t/prepare-pijul-0-7-0/37>\
**Category:** Development\
**Created:** [June 5, 2017, 12:04pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37 "2017-06-05T12:04:30Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![lthms](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/lthms/32/124_2.png) [@lthms](https://discourse.pijul.org/u/lthms)\
**Post date:** [June 5, 2017, 12:04pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/1 "2017-06-05T12:04:30Z")

</div>

I think now is a good time to consider a new release for pijul.

## ChangeLog

> If you find something is missing, please feel free to tell. The goal is to have an as useful as possible ChangeLog _for end-users_.

### Features

- `pijul status`: print the list of staging changes
- `.ignore` and `.pijul/local/ignore` files can be used to filter the `pijul status` output.

### Enhancement

- Improve test coverage

### Bug Fixes

- Fixing a stack overflow in `pijul apply`

### Dependencies

- bitflags: 0.8 → 0.9
- hyper-rustly: 0.5 → 0.6

## Pending Features

> If a pending feature is missing here, feel free to tell.

- `show-dependencies` command: do we want it in this release or in the next? (@lthms)
- the global configuration should use the app\_dirs crate so that it goes in a good, platform-appropriate place (@joeneeman)

## Blocking Issue

I’ve reported two issues which should be taken care of before releasing, IMO.

- ~~[pijul unrecord panicks](https://nest.pijul.com/pijul_org/pijul/issues/114): I can reproduce this issue, but am I the only one in such case?~~
- ~~[pijul pull has created a diff in a clean repo](https://nest.pijul.com/pijul_org/pijul/issues/113): I know at least @laumann has seen the same issue  
~~
- ~~Fixing pending conflict thanks to @laumann [PR](https://nest.pijul.com/pijul_org/pijul/pullrequests/115)~~

Any feedback on that matter?

---

<div class="post-metadata">

**Author:** ![joeneeman](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/joeneeman/32/77_2.png) [@joeneeman](https://discourse.pijul.org/u/joeneeman)\
**Post date:** [June 5, 2017, 12:11pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/2 "2017-06-05T12:11:34Z")

</div>

> [@lthms](#):
>
> Interpret pull’s remote relative from the working directory

Are you talking about my patch here? Because that wasn’t an enhancement relative to the last release: I was just undoing a (presumably unintended) change.

Also, there’s one change I’d like to make before the next release, but haven’t had time: the global configuration should use the `app_dirs` crate so that it goes in a good, platform-appropriate place.

---

<div class="post-metadata">

**Author:** ![lthms](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/lthms/32/124_2.png) [@lthms](https://discourse.pijul.org/u/lthms)\
**Post date:** [June 5, 2017, 12:16pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/3 "2017-06-05T12:16:55Z")

</div>

I’ve edited the first post in consequence, thanks for your feedback!

> [@joeneeman](#):
>
> Because that wasn’t an enhancement relative to the last release: I was just undoing a (presumably unintended) change.

Should I consider it a bug fix? Or has it been introduced after the `0.6.0` release and therefore shouldn’t appear in the ChangeLog?

---

<div class="post-metadata">

**Author:** ![joeneeman](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/joeneeman/32/77_2.png) [@joeneeman](https://discourse.pijul.org/u/joeneeman)\
**Post date:** [June 5, 2017, 1:27pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/4 "2017-06-05T13:27:31Z")

</div>

I think it appeared after 0.6.0.

---

<div class="post-metadata">

**Author:** ![lthms](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/lthms/32/124_2.png) [@lthms](https://discourse.pijul.org/u/lthms)\
**Post date:** [June 5, 2017, 2:30pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/5 "2017-06-05T14:30:04Z")

</div>

One blocking issue has been fixed by @pmeunier. Thanks a lot!

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [June 5, 2017, 4:43pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/6 "2017-06-05T16:43:38Z")

</div>

Just fixed the other one 😤

---

<div class="post-metadata">

**Author:** ![lthms](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/lthms/32/124_2.png) [@lthms](https://discourse.pijul.org/u/lthms)\
**Post date:** [June 5, 2017, 5:15pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/7 "2017-06-05T17:15:36Z")

</div>

There are still several conflicts @laumann [has fixed](https://nest.pijul.com/pijul_org/pijul/pullrequests/115).

---

<div class="post-metadata">

**Author:** ![lthms](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/lthms/32/124_2.png) [@lthms](https://discourse.pijul.org/u/lthms)\
**Post date:** [June 6, 2017, 4:32pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/8 "2017-06-06T16:32:21Z")

</div>

As for as I know, all pending issues have been fixed. I will push one last time a patch to add my `show-dependencies` command and we will wait for @joeneeman to finish its own item and I think we will be good. Once done, we will just have to update the ChangeLog before releasing.

Do not hesitate to test the latest pijul as much as possible, @all!

---

<div class="post-metadata">

**Author:** ![joeneeman](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/joeneeman/32/77_2.png) [@joeneeman](https://discourse.pijul.org/u/joeneeman)\
**Post date:** [June 6, 2017, 7:35pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/9 "2017-06-06T19:35:49Z")

</div>

I just pushed my patch. I’m going to modify the changelog next.

---

<div class="post-metadata">

**Author:** ![lthms](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/lthms/32/124_2.png) [@lthms](https://discourse.pijul.org/u/lthms)\
**Post date:** [June 8, 2017, 7:29am UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/10 "2017-06-08T07:29:26Z")

</div>

Thanks a lot, @joeneeman! I think we will be ready for releasing this weekend if that suits the pijul team. I will try to push my own patch so that either @pmeunier or @flobec can merge them along with yours.

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [June 14, 2017, 8:29pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/11 "2017-06-14T20:29:13Z")

</div>

Hi guys! I’m sorry, but I had to make lots of changes in the Nest recently, mostly for stability problems. I’ve not been able to do it all as fast as I first imagined.

Summary of the changes to the Nest in the last week:

- no more pending patches, these were really fat on disk. They might come back in the future.
- massive refactoring: several modules were getting fat (\> 3000 lines). The situation is now back under control, but I had to re-debug a number of things (such as oauth).
- repositories got an “admin” page. You can give extra permissions to other users. The UI is not great. Also, remember that all repos on the Nest are public anyway, and there’s no way yet to create a private repository.
- after a testing period, webhooks are now available for all repositories.
- the Pijul IRC bot is now public.

Now that the Nest is back on its feet, I’d like to ask you guys to check if you want any other patch in. Else, I’ll upload 0.7 to [crates.io](http://crates.io), and build a windows version, by tomorrow (Thursday) night.

---

<div class="post-metadata">

**Author:** ![lthms](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/lthms/32/124_2.png) [@lthms](https://discourse.pijul.org/u/lthms)\
**Post date:** [June 23, 2017, 5:33pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/12 "2017-06-23T17:33:12Z")

</div>

IMO, before releasing, we need to:

1. add `pijul show-dependencies`
2. add `app-dir`’s patch crate by @joeneeman
3. add `Cargo.lock` to the `include` directive of `Cargo.toml` (to be sure `cargo install pijul` **is** reproductible)

---

<div class="post-metadata">

**Author:** ![flobec](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/flobec/32/23_2.png) [@flobec](https://discourse.pijul.org/u/flobec)\
**Post date:** [July 14, 2017, 1:23pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/14 "2017-07-14T13:23:46Z")

</div>

I think we should release the current state of master as 0.7.0 (modulo writing a changelog / announcement)

---

<div class="post-metadata">

**Author:** ![lthms](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/lthms/32/124_2.png) [@lthms](https://discourse.pijul.org/u/lthms)\
**Post date:** [July 14, 2017, 2:01pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/15 "2017-07-14T14:01:03Z")

</div>

I can help for that. The only thing I could add is you have introduced the wrong version of my show-dependencies command. It is not a big deal however: I will try to submit the diff as an additional patch for the next release.

---

<div class="post-metadata">

**Author:** ![flobec](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/flobec/32/23_2.png) [@flobec](https://discourse.pijul.org/u/flobec)\
**Post date:** [July 14, 2017, 2:41pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/16 "2017-07-14T14:41:15Z")

</div>

sorry about that and thanks for fixing it.

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [July 14, 2017, 3:13pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/17 "2017-07-14T15:13:18Z")

</div>

So, should I release?

---

<div class="post-metadata">

**Author:** ![flobec](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/flobec/32/23_2.png) [@flobec](https://discourse.pijul.org/u/flobec)\
**Post date:** [July 14, 2017, 3:19pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/18 "2017-07-14T15:19:35Z")

</div>

I’d say yes, unless lthms wants to wait for something (the version needs to be bumped, of course)

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [July 14, 2017, 4:50pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/19 "2017-07-14T16:50:59Z")

</div>

Maybe this would be a good time to add documentation. I’ll try to do it and release later today.

---

<div class="post-metadata">

**Author:** ![lthms](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/lthms/32/124_2.png) [@lthms](https://discourse.pijul.org/u/lthms)\
**Post date:** [July 14, 2017, 4:51pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/20 "2017-07-14T16:51:05Z")

</div>

I think we are good to go. Can you create a branch when it is done, so we can backport potential fixes?

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [July 14, 2017, 7:36pm UTC](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37/21 "2017-07-14T19:36:41Z")

</div>

Alright, some work was needed, I took the opportunity to document libpijul better, and to do a general cleanup.

I also switched to error-chain for error handling, instead of doing the same thing manually.

[Next page](https://discourse.pijul.org/t/prepare-pijul-0-7-0/37.md?page=2)