| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
> Since I'm one of those that would be affected, my preference would be |
| 5 |
> #2 with the addition that the initial release by package masked for X |
| 6 |
> amount of time to give time to work with it and update the utilities |
| 7 |
> at the same time. |
| 8 |
|
| 9 |
This is what I thought as well. |
| 10 |
|
| 11 |
> If I procrastinate, then it is on me once it is unmasked to handle the |
| 12 |
> bugs for the packages I'm responsible for. |
| 13 |
> |
| 14 |
> Additionally, I would like to see lot's of announcements on |
| 15 |
> gentoo-dev. |
| 16 |
|
| 17 |
Yes, this is planned. I wanted to first get a reaction from the folks |
| 18 |
most involved in portage to assess that this would be a good route to |
| 19 |
go. Once that's established, then I'll toss a nice email to -dev |
| 20 |
stating "Here's how things are going to work in the future", so no one |
| 21 |
is caught 100% surprised (though, as with all major things, there will |
| 22 |
be someone that states 'huh, I didn't hear about that). So it mainly |
| 23 |
comes down to: |
| 24 |
|
| 25 |
1) People need to be made aware |
| 26 |
2) Agreement of the portage development team is essential, as #2 means |
| 27 |
declaring a release, and.. well quite frankly it's their package, they |
| 28 |
decide how a release goes. |
| 29 |
|
| 30 |
> Regards, |
| 31 |
> Paul |
| 32 |
|
| 33 |
Chris White |
| 34 |
-----BEGIN PGP SIGNATURE----- |
| 35 |
Version: GnuPG v1.4.2.2 (GNU/Linux) |
| 36 |
|
| 37 |
iD8DBQFEwUh1FdQwWVoAgN4RAvGGAKCP9+y4XsMaNscvhVxiwj+C9BUXUACeJbRA |
| 38 |
tdHQxnrjJsJLE/0inlPBw6U= |
| 39 |
=gwKe |
| 40 |
-----END PGP SIGNATURE----- |
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-portage-dev@g.o mailing list |
Archives